On Mon, 2011-10-17 at 16:22 +0200, Miklos Szeredi wrote: > Ben Hutchings <ben@xxxxxxxxxxxxxxx> writes: > > > On Fri, 2011-10-14 at 22:52 +0000, brian m. carlson wrote: > >> Package: linux-2.6 > >> Version: 3.1.0~rc7-1~experimental.1 > >> Severity: normal > >> > >> This morning I was backing up my laptop to another computer via sshfs > >> (and fuse). The afio archiver was writing to this sshfs-mounted > >> location. I decided to abort the operation with Ctrl-C, which caused > >> the sshfs mount to become unmounted; however, afio was apparently not > >> affected by the SIGINT (probably because processes in disk IO are > >> unkillable). > >> > >> Several hours later, I attempted to suspend my computer and it failed to > >> do so. The kernel log (attached) indicated that the afio process from > >> hours before was preventing the suspend. Since processes waiting on > >> disk IO are unkillable (IMO a bug) and the underlying device to which > >> afio was writing was long gone, I was forced to reboot the machine in > >> order to get it to suspend. If I had not noticed that the machine had > >> failed to suspend, it could have stayed running in my bag and seriously > >> overheated. > > > > This seems to be a bug in FUSE. Is this known about? If not, could > > someone look into this? > > It's a bug in the fuse-freezer interaction. Yes, it is known. [...] But the FUSE server was already killed; shouldn't that cause outstanding requests to fail immediately? Ben. -- Ben Hutchings No political challenge can be met by shopping. - George Monbiot
Attachment:
signature.asc
Description: This is a digitally signed message part
