From: Kalpak Shah <kalpak@clusterfs.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Andreas Dilger <adilger@clusterfs.com>,
tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 2/4] e2fsprogs: Add undoe2fs
Date: Wed, 01 Aug 2007 12:03:16 +0530 [thread overview]
Message-ID: <1185949996.3870.9.camel@garfield.linsyssoft.com> (raw)
In-Reply-To: <46B02539.5020505@linux.vnet.ibm.com>
On Wed, 2007-08-01 at 11:46 +0530, Aneesh Kumar K.V wrote:
>
> Andreas Dilger wrote:
> > On Aug 01, 2007 07:34 +0530, Aneesh Kumar K.V wrote:
> >> undoe2fs can be used to replay the transaction saved
> >> in the transaction file using undo I/O Manager
> >
> > This should save the mtime of the superblock, and only do the undo
> > step if the filesystem hasn't changed. Otherwise it could seriously
> > corrupt the filesystem.
>
>
> I am not sure i understand this. The Undo I/O manager tracks all the write
> happening to the file system and copy the original content of the blocks to
> the tdb file. Undoe2fs simply copies these blocks back to the file system. So
> That way if you look at undoe2fs it doesn't have any knowledge of the file
> system at all.
>
> Can you let me know a use case where this will fail.
undoe2fs made a copy of all the changes to the filesystem. After that
the filesystem was mounted and used thereby rendering the checkpoint
invalid. If this checkpoint was replayed it could seriously corrupt the
filesystem. Hence as Andreas suggests the mtime of the filesystem should
be checked and only then the transaction should be replayed.
Infact mounting the filesystem when the replay is in progress would also
corrupt the filesystem.
Is should the checkpoint be deleted if e2fsck was aborted?
Thanks,
Kalpak.
next prev parent reply other threads:[~2007-08-01 6:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bee58d48110eee4d5cd133167245b99644148d96.1185933778.git.aneesh.kumar@linux.vnet.ibm.com>
2007-08-01 2:04 ` [PATCH 1/4] e2fsprogs: Add undo I/O manager Aneesh Kumar K.V
[not found] ` <47f96570519d76b8d59f92b729a0a48c4a1b68d8.1185933778.git.aneesh.kumar@linux.vnet.ibm.com>
2007-08-01 2:04 ` [PATCH 2/4] e2fsprogs: Add undoe2fs Aneesh Kumar K.V
2007-08-01 6:02 ` Andreas Dilger
2007-08-01 6:16 ` Aneesh Kumar K.V
2007-08-01 6:33 ` Kalpak Shah [this message]
2007-08-01 7:10 ` Andreas Dilger
2007-08-01 7:52 ` Aneesh Kumar K.V
2007-08-01 8:27 ` Andreas Dilger
[not found] ` <70b3f394cda275d59094d52f60d1ee76492033fc.1185933778.git.aneesh.kumar@linux.vnet.ibm.com>
2007-08-01 2:04 ` [PATCH 3/4] e2fsprogs: Make mke2fs use undo I/O manager Aneesh Kumar K.V
2007-08-01 6:04 ` Andreas Dilger
2007-08-01 6:14 ` Aneesh Kumar K.V
2007-08-01 7:14 ` Andreas Dilger
[not found] ` <83d2fbbea6a099e38b1358e6cbc0f59c4883ddef.1185933778.git.aneesh.kumar@linux.vnet.ibm.com>
2007-08-01 2:04 ` [PATCH 4/4] e2fsprogs: Support for large inode migration Aneesh Kumar K.V
2007-08-01 15:34 e2fsprogs patches Aneesh Kumar K.V
2007-08-01 15:34 ` [PATCH 1/4] e2fsprogs: Add undo I/O manager Aneesh Kumar K.V
[not found] ` <f2c3823cb66c7a30436b1f2163cbe3bba791a115.1185981319.git.aneesh.kumar@linux.vnet.ibm.com>
[not found] ` <53bd7d38bb3251e93fb35f56e38d2d1904951ed0.1185981319.git.aneesh.kumar@linux.vnet.ibm.com>
2007-08-01 15:34 ` [PATCH 2/4] e2fsprogs: Add undoe2fs Aneesh Kumar K.V
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=1185949996.3870.9.camel@garfield.linsyssoft.com \
--to=kalpak@clusterfs.com \
--cc=adilger@clusterfs.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).