From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nigel Cunningham Subject: Re: Freeze the FUSE on Wubi Date: Sat, 17 Oct 2009 21:08:20 +1100 Message-ID: <4AD99794.2090507@crca.org.au> References: <814979.58291.qm@web112806.mail.gq1.yahoo.com> <20091016115854.1e476da8@strolchi.home.s3e.de> <4AD85889.9010206@crca.org.au> <493410.12916.qm@web112815.mail.gq1.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <493410.12916.qm@web112815.mail.gq1.yahoo.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: Nick Davies Cc: linux-pm@lists.linux-foundation.org, Stefan Seyfried List-Id: linux-pm@vger.kernel.org Hi. Nick Davies wrote: >> Hi. >> >> Stefan Seyfried wrote: >>> On Fri, 16 Oct 2009 01:54:10 -0700 (PDT) >>> Nick Davies wrote: >>> >>>> Dear all, >>>> >>>> I am trying to debug the suspend/hibernate on Wubi(The Ubuntu >>>> installer for Windows) these day. Since Ubuntu sits on top of NTFS >>>> partition with the help of ntfs-3g via FUSE, I think it should not >>>> pass the file system freezing stage, but in fact, the suspend works >>>> well on my machine. So I am curious that how can they achieve that? >>>> Just keep the FUSE alive to the end of the suspend? Any ideas are >>>> welcome. >>> (Disclaimer: all below is AFAIK and it might be slightly wrong) >>> On swapon(), a block map of the file / partition is made by the kernel >>> and later I/O to the swap area are not going through the filesystem >>> layer. So FUSE is not involved in the suspend process at the stage of >>> image writing. >> It's exactly right. > Hi, > > Thanks for all your quick response. That is to say, the suspend itself has no conflict with the FUSE when do the freezing? > > To Nigel, > I've tried the TuxOnIce project, unfortunately I can't do suspend now. According to the dmesg log, it hangs at the freezing file system. > I check some codes of your patch. You've patched freeze_filesystems() to the fs/buffer.c file, so I guess there may be something wrong with the freeze order in that subroutine with my situation(OS sits on top of NTFS using ntfs-3g via FUSE). How your opinions? Hmm. That's interesting - I'd expect things to be the other way around. Can you provide the dmesg? Regards, Nigel