On Wed, 2014-02-19 at 17:22 -0300, Ernesto wrote: > El 05/02/2014 19:50, Ben Hutchings escribió: > > On Wed, 2014-02-05 at 17:48 -0300, Ernesto wrote: > >> Ben, > >> > >> El 13/01/2014 01:49, Ben Hutchings escribió: > >> > Control: tag -1 moreinfo > >> > > >> > On Mon, 2014-01-13 at 00:34 -0300, Ernesto wrote: > >> >> Package: src:linux > >> >> Version: 3.2.51-1 > >> >> Severity: important > >> >> > >> >> Hi, > >> >> > >> >> the problem is when I resume from suspend to ram (perhaps from disk > >> >> also) having a disk image mounted through nbd. I lose access to the > >> >> mounted image, and can't umount nor remove the module nbd. > >> >> > >> >> I have to reboot the system in order to gain access to the disk image > >> >> again. This is very annoying since I use it a lot. > >> >> > >> >> I hope you can sort this out. Any additional info, please ask. > >> > > >> > Does this work in Linux 3.12 (available from testing or > >> > wheezy-backports)? > >> > > >> > Ben. > >> > >> I tested the kernel you suggested and it works fine. Thanks. > > > > So does the disk image remain mounted and accessible? > > Or, does it become unmounted but possible to mount again? > > > > I'm trying to work out what might have fixed this, but it's not > > obvious. > > The disk image remains mounted and accessible.
OK, noted. > Sadly, backporting the kernel renders my postgresql server install > useless. Do I have to backport that too? Is this normal? That should not be necessary. Can you open a new bug against the new kernel, explaining how postgresql goes wrong? Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer
signature.asc
Description: This is a digitally signed message part
