The Linux Kernel Mailing List
 help / color / mirror / Atom feed
* Re: Bug#645366: [fuse-devel] Hang and suspend failure after FUSE server killed (3.1-rc7)
       [not found]   ` <87ty77lmts.fsf@tucsk.pomaz.szeredi.hu>
@ 2011-10-17 14:31     ` Ben Hutchings
  2011-10-17 14:45       ` Miklos Szeredi
  0 siblings, 1 reply; 2+ messages in thread
From: Ben Hutchings @ 2011-10-17 14:31 UTC (permalink / raw)
  To: Miklos Szeredi, 645366
  Cc: fuse-devel, brian m. carlson, rjw, linux-fsdevel, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]

On Mon, 2011-10-17 at 16:22 +0200, Miklos Szeredi wrote:
> Ben Hutchings <ben@decadent.org.uk> 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 #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Bug#645366: [fuse-devel] Hang and suspend failure after FUSE server killed (3.1-rc7)
  2011-10-17 14:31     ` Bug#645366: [fuse-devel] Hang and suspend failure after FUSE server killed (3.1-rc7) Ben Hutchings
@ 2011-10-17 14:45       ` Miklos Szeredi
  0 siblings, 0 replies; 2+ messages in thread
From: Miklos Szeredi @ 2011-10-17 14:45 UTC (permalink / raw)
  To: Ben Hutchings
  Cc: 645366, fuse-devel, brian m. carlson, rjw, linux-fsdevel,
	linux-kernel

Ben Hutchings <ben@decadent.org.uk> writes:

> On Mon, 2011-10-17 at 16:22 +0200, Miklos Szeredi wrote:
>> Ben Hutchings <ben@decadent.org.uk> 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?

Yes it should.

But my guess is that the server wasn't actually killed, otherwise the
archiver program would have just gotten ENOTCONN errors and exited.  The
fact that "afio" had hung means that sshfs also hung.  We can't prove or
disprove this without a process listing.

The reason for sshfs hanging could be due to one of the bugs that were
fixed in the sshfs-2.3 version.  E.g.:

	* Fix cleanup when ssh connection is terminated.  This prevents
	sshfs hanging when the server is rebooted, for example.

Thanks,
Miklos

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-10-17 14:46 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20111014225213.GA5705@crustytoothpaste.ath.cx>
     [not found] ` <1318824752.3340.7.camel@deadeye>
     [not found]   ` <87ty77lmts.fsf@tucsk.pomaz.szeredi.hu>
2011-10-17 14:31     ` Bug#645366: [fuse-devel] Hang and suspend failure after FUSE server killed (3.1-rc7) Ben Hutchings
2011-10-17 14:45       ` Miklos Szeredi

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox