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: Sat, 9 Aug 2014 00:07:36 -0400 [thread overview]
Message-ID: <20140809040736.GB23604@thunk.org> (raw)
In-Reply-To: <BLU436-SMTP1726DA8B9CB511781B73155FDEF0@phx.gbl>
On Fri, Aug 08, 2014 at 11:29:11PM -0400, TR Reardon wrote:
>
> I meant only: that commit is in master _and_ maint branches, so to get a
> version roughly = 1.42.11 + metadata_csum, I pulled up to that commit.
Right but you gave me the git commit id for 1.42.11, which is not
particularly useful; I know the commit id for v1.42.11 already. :-)
What I needed to know was the git commit of "master" that you had
grabbed, since the "master" and "next" branches are fairly active
these days. (The master branch langs the next branch, so depending on
how exciting a life you want to live, you can try the next branch
instead of the master branch.)
> Regardless, the problem exists in kernel too, judging by the JBD2 errors.
Yes, we'll need to look into that. Definitely worth knowing; thanks
for that.
Cheers,
- Ted
next prev parent reply other threads:[~2014-08-09 4:07 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
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 [this message]
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=20140809040736.GB23604@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).