[Top] [All Lists]

Re: [PATCH] Freeze bdevs when freezing processes.

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>, "Rafael J. Wysocki" <rjw@xxxxxxx>, David Chinner <dgc@xxxxxxx>, Nigel Cunningham <ncunningham@xxxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
Subject: Re: [PATCH] Freeze bdevs when freezing processes.
From: Pavel Machek <pavel@xxxxxx>
Date: Tue, 24 Oct 2006 23:26:48 +0200
In-reply-to: <20061024170633.GA17956@xxxxxxxxxxxxx>
References: <1161576735.3466.7.camel@xxxxxxxxxxxxxxxxxx> <200610231236.54317.rjw@xxxxxxx> <20061024144446.GD11034@xxxxxxxxxxxxxxxxx> <200610241730.00488.rjw@xxxxxxx> <20061024170633.GA17956@xxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.11+cvs20060126

On Tue 2006-10-24 18:06:33, Christoph Hellwig wrote:
> On Tue, Oct 24, 2006 at 05:29:59PM +0200, Rafael J. Wysocki wrote:
> > Do you mean calling sys_sync() after the userspace has been frozen
> > may not be sufficient?
> No, that's definitly not enough.  You need to freeze_bdev to make sure
> data is on disk in the place it's expected by the filesystem without
> starting a log recovery.

I believe log recovery is okay in this case.

It can only happen when kernel dies during suspend or during
resume... And log recovery seems okay in that case. We even guarantee
that user did not loose any data -- by using sys_sync() after userland
is stopped -- but let's not overdo over protections.

(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) 

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