Thread (5 messages) 5 messages, 3 authors, 2014-08-09

Re: journal recovery problems with metadata_csum, *non-64bit*

From: Theodore Ts'o <tytso@mit.edu>
Date: 2014-08-08 21:47:34

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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help