From: Theodore Ts'o Subject: Re: journal recovery problems with metadata_csum, *non-64bit* Date: Sat, 9 Aug 2014 00:07:36 -0400 Message-ID: <20140809040736.GB23604@thunk.org> References: <20140808214732.GN25145@thunk.org> <20140809002131.GR25145@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-ext4@vger.kernel.org To: TR Reardon Return-path: Received: from imap.thunk.org ([74.207.234.97]:51954 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750801AbaHIEHj (ORCPT ); Sat, 9 Aug 2014 00:07:39 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-ext4-owner@vger.kernel.org List-ID: 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