Re: 18.104.22.168: hibernation fails with large kernel trace
From: Pavel Machek
Date: Thu May 28 2009 - 16:48:21 EST
On Thu 2009-05-28 17:06:37, Miklos Szeredi wrote:
> On Thu, 28 May 2009, Pavel Machek wrote:
> > In the meantime, people should stop/restart fuse around
> > suspend/hibernation, I guess...
> Which is not possible if the filesystem is busy, and it _will_ be busy
> in all cases where we now see freeze failures.
Well, maybe people will need to kill few processes to get it to
> And just a reminder that this problem is not fuse specific: similar
> freeze failures can also happen for network filesystems routed over a
> tun/tap device (e.g. NFS over OpenVPN).
Agreed, general solution would be nice. In NFS over OpenVPN case,
people will need to unmount NFS :-(, and maybe kill processes to do
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/