From: "George Spelvin" <linux@horizon.com>
To: gnehzuil.liu@gmail.com, linux@horizon.com
Cc: linux-ext4@vger.kernel.org
Subject: Re: metadata_csum + e4defrag seems to cause problems
Date: 29 Apr 2013 11:57:15 -0400 [thread overview]
Message-ID: <20130429155715.23219.qmail@science.horizon.com> (raw)
In-Reply-To: <20130426025753.GA21659@gmail.com>
> Yes, metatdata_csum + e4defrag could corrupt ext4 file system. We have
> found this bug and it has been fixed by this commit (2656497b, it is in
> dev branch of ext4 tree). I am not sure whether you use dev branch.
> Could you please tell me your kernel version? If you don't use dev
> branch, could you please try dev branch of ext4 tree? Here is the git
> link:
> https://git.kernel.org/cgit/linux/kernel/git/tytso/ext4.git/log/?h=dev
I was running 3.8-rc7 at the time of the corruption; I rebooted to -rc8
as part of the recovery.
Yes, I already have the ext4 repository cloned, but that was just
for pulling a particular fix Ted recommended a while ago. I've been
reluctant to use a branch labelled "dev" more routinely without more
reassurance that it's believed to be "brave" rather than "stupid" to
use in something other than a dedicated test environment.
I'll try v3.9 + ext4/dev. Thank you!
(Current head is 0d606e2c9fcc:
"ext4: fix type-widening bug in inode table readahead code")
prev parent reply other threads:[~2013-04-29 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 17:48 metadata_csum + e4defrag seems to cause problems George Spelvin
2013-04-26 2:57 ` Zheng Liu
2013-04-29 15:57 ` George Spelvin [this message]
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=20130429155715.23219.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=gnehzuil.liu@gmail.com \
--cc=linux-ext4@vger.kernel.org \
/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.