[Top] [All Lists]

Re: [PATCH] Freeze bdevs when freezing processes.

To: Pavel Machek <pavel@xxxxxx>
Subject: Re: [PATCH] Freeze bdevs when freezing processes.
From: David Chinner <dgc@xxxxxxx>
Date: Wed, 25 Oct 2006 18:38:30 +1000
Cc: David Chinner <dgc@xxxxxxx>, "Rafael J. Wysocki" <rjw@xxxxxxx>, Nigel Cunningham <ncunningham@xxxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <20061025081001.GL5851@xxxxxxxxxx>
References: <1161576735.3466.7.camel@xxxxxxxxxxxxxxxxxx> <200610231236.54317.rjw@xxxxxxx> <20061024144446.GD11034@xxxxxxxxxxxxxxxxx> <200610241730.00488.rjw@xxxxxxx> <20061024163345.GG11034@xxxxxxxxxxxxxxxxx> <20061024213737.GD5662@xxxxxxxxxx> <20061025001331.GP8394166@xxxxxxxxxxxxxxxxx> <20061025081001.GL5851@xxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/
On Wed, Oct 25, 2006 at 10:10:01AM +0200, Pavel Machek wrote:
> > Hence the only way to correctly rebuild the XFS state on resume is
> > to quiesce the filesystem on suspend and thaw it on resume so as to
> > trigger log recovery.
> No, during suspend/resume, memory image is saved, and no state is
> lost. We would not even have to do sys_sync(), and suspend/resume
> would still work properly.

It seems to me that you ensure the filesystem is synced to disk and
then at some point later you record the memory state of the
filesystem, but these happen at different times. That leaves a
window for things to get out of sync again, right?



Dave Chinner
Principal Engineer
SGI Australian Software Group

<Prev in Thread] Current Thread [Next in Thread>