[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <486D2BC4.7000603@sandeen.net>
Date: Thu, 03 Jul 2008 14:43:00 -0500
From: Eric Sandeen <sandeen@...deen.net>
To: xfs-masters@....sgi.com
CC: Christoph Hellwig <hch@...radead.org>,
Dave Chinner <david@...morbit.com>,
Elias Oltmanns <eo@...ensachen.de>,
Henrique de Moraes Holschuh <hmh@....eng.br>,
Kyle Moffett <mrmacman_g4@....com>,
Matthew Garrett <mjg59@...f.ucam.org>,
David Chinner <dgc@....com>,
Jeremy Fitzhardinge <jeremy@...p.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jens Axboe <jens.axboe@...cle.com>
Subject: Re: [xfs-masters] Re: freeze vs freezer
Rafael J. Wysocki wrote:
>>> I talked with Jens about it on a very general level, but it seems doable at
>>> first sight.
>> Why would you hack the blok layer when we already have a perfectly fine
>> facility to archive what you want? freeze_bdev is there exactly for the
>> purpose to make the filesystem consistant on disk and then freeze all
>> I/O.
>
> We tried that in the past and it didn't work very well due to some bad
> interactions with the md layer that we wanted to stay functional while we
> were saving the image.
Hm, details or a link?
> Also, do all of the supported filesystems implement this feature?
ext3, ext4, gfs2, jfs, reiserfs, xfs, all provide a write_super_lockfs
op, which is what freeze_bdev uses. I think that the rest is generic,
for simpler filesystems.
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists