From: Theodore Ts'o <tytso@mit.edu>
To: TR Reardon <thomas_reardon@hotmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: journal recovery problems with metadata_csum, *non-64bit*
Date: Fri, 8 Aug 2014 17:47:32 -0400 [thread overview]
Message-ID: <20140808214732.GN25145@thunk.org> (raw)
In-Reply-To: <BLU436-SMTP84585FAA628776E190822AFDEE0@phx.gbl>
On Fri, Aug 08, 2014 at 03:31:12PM -0400, TR Reardon wrote:
> Kernel 3.16, e2fsprogs 1.43-WIP (1.42.11 compiled with metadata_csum
> support), filesystems mounted with journal_async_commit.
>
> This may be an fsck problem, hard to tell. I consistently have
> problems with journal recovery after hard reboot when filesystem has
> metadata_csum. Interestingly, no problems with 64-bit filesystems.
These are test file systems I hope. metadata_csum is something where
we're still working out some of the bugs. (Obviously)
So metadata_csum works fine with 64-bit file systems, but it is
failing with journal recovery if the 64-bit file system feature is not
enabled? Is that a correct summary of what you are seeing?
Also, with e2fsprogs 1.43-WIP releases, it's important that you
specify the git commit id you are using, since the next branch in
particular is quite fast moving.
- Ted
next prev parent reply other threads:[~2014-08-08 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 19:31 journal recovery problems with metadata_csum, *non-64bit* TR Reardon
2014-08-08 21:47 ` Theodore Ts'o [this message]
2014-08-08 22:29 ` TR Reardon
2014-08-09 0:21 ` Theodore Ts'o
[not found] ` <BLU436-SMTP1726DA8B9CB511781B73155FDEF0@phx.gbl>
2014-08-09 4:07 ` Theodore Ts'o
2014-08-08 22:15 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2014-08-10 22:35 TR Reardon
[not found] <BLU437-SMTP3407533C3883653626BD3DFDEC0@phx.gbl>
2014-08-11 7:10 ` Darrick J. Wong
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=20140808214732.GN25145@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=thomas_reardon@hotmail.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 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).