From: Andreas Dilger <adilger@clusterfs.com>
To: linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Stelian Pop <stelian.pop@fr.alcove.com>,
Sam Vilain <sam@vilain.net>,
dax@gurulabs.com
Subject: Re: [ANNOUNCE] Ext3 vs Reiserfs benchmarks
Date: Tue, 16 Jul 2002 13:49:29 -0600 [thread overview]
Message-ID: <20020716194929.GS442@clusterfs.com> (raw)
In-Reply-To: <20020716193831.GC22053@merlin.emma.line.org>
On Jul 16, 2002 21:38 +0200, Matthias Andree wrote:
> On Tue, 16 Jul 2002, Christoph Hellwig wrote:
> > On Tue, Jul 16, 2002 at 02:53:01PM +0200, Matthias Andree wrote:
> > > Not if some day somebody implements file system level snapshots for
> > > Linux. Until then, better have garbled file contents constrained to a
> > > file than random data as on-disk layout changes with hefty directory
> > > updates.
> >
> > or the blockdevice-level snapshots already implemented in Linux..
>
> That would require three atomic steps:
>
> 1. mount read-only, flushing all pending updates
> 2. take snapshot
> 3. mount read-write
>
> and then backup the snapshot. A snapshots of a live file system won't
> do, it can be as inconsistent as it desires -- if your corrupt target is
> moving or not, dumping it is not of much use.
Luckily, there is already an interface which does this -
sync_supers_lockfs(), which the LVM code will use if it is patched in.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-07-16 19:49 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 16:21 [ANNOUNCE] Ext3 vs Reiserfs benchmarks Dax Kelson
2002-07-12 17:05 ` Andreas Dilger
2002-07-12 17:26 ` kwijibo
2002-07-12 17:36 ` Andreas Dilger
2002-07-12 20:34 ` Chris Mason
2002-07-13 4:44 ` Daniel Phillips
2002-07-14 20:40 ` Dax Kelson
2002-07-15 8:26 ` Sam Vilain
2002-07-15 12:30 ` Alan Cox
2002-07-15 12:02 ` Sam Vilain
2002-07-15 13:23 ` Alan Cox
2002-07-15 13:40 ` Chris Mason
2002-07-15 19:40 ` Andrew Morton
2002-07-15 15:12 ` Andrea Arcangeli
2002-07-15 16:03 ` Andreas Dilger
2002-07-15 16:12 ` Daniel Phillips
2002-07-15 17:48 ` Sam Vilain
2002-07-15 18:47 ` Mathieu Chouquet-Stringer
2002-07-15 19:26 ` Sam Vilain
2002-07-16 8:18 ` Stelian Pop
2002-07-16 12:22 ` Gerhard Mack
2002-07-16 12:49 ` Stelian Pop
2002-07-16 15:11 ` Gerhard Mack
2002-07-16 15:22 ` Andrea Arcangeli
2002-07-16 15:39 ` Stelian Pop
2002-07-16 19:45 ` Matthias Andree
2002-07-16 20:04 ` Shawn
2002-07-16 20:11 ` Mathieu Chouquet-Stringer
2002-07-16 20:22 ` Shawn
2002-07-16 20:27 ` Mathieu Chouquet-Stringer
2002-07-17 11:45 ` Matthias Andree
2002-07-17 19:02 ` Andreas Dilger
2002-07-18 9:29 ` Matthias Andree
2002-07-19 8:29 ` Matthias Andree
2002-07-19 16:39 ` Andreas Dilger
2002-07-19 20:01 ` Shawn
2002-07-19 20:47 ` Andreas Dilger
2002-07-15 21:14 ` Andreas Dilger
2002-07-17 18:41 ` bill davidsen
2002-07-17 19:47 ` [ANNOUNCE] Ext3 vs Reiserfs benchmarks (whither dump?) Lew Wolfgang
2002-07-16 8:15 ` [ANNOUNCE] Ext3 vs Reiserfs benchmarks Stelian Pop
2002-07-16 12:27 ` Matthias Andree
2002-07-16 12:43 ` Stelian Pop
2002-07-16 12:53 ` Matthias Andree
2002-07-16 13:05 ` Christoph Hellwig
2002-07-16 19:38 ` Matthias Andree
2002-07-16 19:49 ` Andreas Dilger [this message]
2002-07-16 20:11 ` Thunder from the hill
2002-07-16 21:06 ` Matthias Andree
2002-07-16 21:23 ` Andreas Dilger
2002-07-16 21:38 ` Thunder from the hill
2002-07-17 11:47 ` Matthias Andree
2002-07-18 14:50 ` Bill Davidsen
2002-07-18 15:09 ` Rik van Riel
2002-07-16 22:19 ` Backups done right (was [ANNOUNCE] Ext3 vs Reiserfs benchmarks) stoffel
2002-07-16 22:33 ` Thunder from the hill
2002-07-18 15:04 ` Bill Davidsen
2002-07-18 15:27 ` Rik van Riel
2002-07-18 15:50 ` stoffel
2002-07-18 16:29 ` Bill Davidsen
2002-07-19 15:28 ` Sam Vilain
2002-07-17 18:51 ` [ANNOUNCE] Ext3 vs Reiserfs benchmarks bill davidsen
2002-07-18 9:32 ` Matthias Andree
2002-07-15 12:09 ` Matti Aarnio
[not found] <20020712162306$aa7d@traf.lcs.mit.edu>
[not found] ` <mit.lcs.mail.linux-kernel/20020712162306$aa7d@traf.lcs.mit.edu>
2002-07-15 15:22 ` Patrick J. LoPresti
2002-07-15 17:31 ` Chris Mason
2002-07-15 18:33 ` Matthias Andree
[not found] ` <20020715173337$acad@traf.lcs.mit.edu>
[not found] ` <mit.lcs.mail.linux-kernel/20020715173337$acad@traf.lcs.mit.edu>
2002-07-15 19:13 ` Patrick J. LoPresti
2002-07-15 20:55 ` Matthias Andree
2002-07-15 21:23 ` Patrick J. LoPresti
2002-07-15 21:38 ` Thunder from the hill
2002-07-16 12:31 ` Matthias Andree
2002-07-16 15:53 ` Thunder from the hill
2002-07-16 19:26 ` Matthias Andree
2002-07-16 19:38 ` Thunder from the hill
2002-07-15 21:59 ` Ketil Froyn
2002-07-15 23:08 ` Matti Aarnio
2002-07-16 12:33 ` Matthias Andree
2002-07-15 22:55 ` Alan Cox
2002-07-15 21:58 ` Matthias Andree
2002-07-15 21:14 ` Chris Mason
2002-07-15 21:31 ` Patrick J. LoPresti
2002-07-15 22:12 ` Richard A Nelson
2002-07-16 1:02 ` Lawrence Greenfield
[not found] ` <mit.lcs.mail.linux-kernel/200207160102.g6G12BiH022986@lin2.andrew.cmu.edu>
2002-07-16 1:43 ` Patrick J. LoPresti
2002-07-16 1:56 ` Thunder from the hill
2002-07-16 12:47 ` Matthias Andree
2002-07-16 21:09 ` James Antill
2002-07-16 12:35 ` Matthias Andree
2002-07-16 7:07 ` Dax Kelson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020716194929.GS442@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=dax@gurulabs.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@vilain.net \
--cc=stelian.pop@fr.alcove.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.