From: Amir Goldstein Subject: Bug#615998: linux-image-2.6.32-5-xen-amd64: Repeatable "kernel BUG at fs/jbd2/commit.c:534" from Postfix on ext4 Date: Mon, 27 Jun 2011 14:57:05 +0300 Message-ID: References: <15E8241A-37A0-4438-849E-A157A376C7F1@boeing.com> <8658F8EE-A52D-4405-A1F3-C0247AB3EA6D@boeing.com> <26AE8923-4DEA-43FF-8F79-1D5AA665A344@boeing.com> <20110405230538.GH2832@thunk.org> <404FD5CC-8F27-4336-B7D4-10675C53A588@boeing.com> <20110624134659.GB26380@quack.suse.cz> <2F80BF45-28FA-46D3-9A28-CA9416DC5813@boeing.com> <20110624200231.GA32176@quack.suse.cz> Reply-To: Amir Goldstein , 615998@bugs.debian.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Jan Kara , "Moffett, Kyle D" , Sean Ryle , "Ted Ts'o" , "615998@bugs.debian.org" <615998@bugs.debian.org>, "linux-ext4@vger.kernel.org" , Sachin Sant , "Aneesh Kumar K.V" To: Lukas Czerner Return-path: Resent-Message-ID: In-Reply-To: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Id: linux-ext4.vger.kernel.org On Mon, Jun 27, 2011 at 2:16 PM, Lukas Czerner wrote: > On Fri, 24 Jun 2011, Jan Kara wrote: > >> On Fri 24-06-11 11:03:52, Moffett, Kyle D wrote: >> > On Jun 24, 2011, at 09:46, Jan Kara wrote: >> > > On Thu 23-06-11 16:19:08, Moffett, Kyle D wrote: >> > >> Besides which, line 534 in the Debian 2.6.32 kernel I am using is t= his >> > >> one: >> > >> >> > >> =A0J_ASSERT(commit_transaction->t_nr_buffers <=3D >> > >> =A0 =A0 =A0 =A0 =A0 commit_transaction->t_outstanding_credits); >> > > >> > > =A0Hmm, OK, so we've used more metadata buffers than we told JBD2 to >> > > reserve. I suppose you are not using data=3Djournal mode and the fil= esystem >> > > was created as ext4 (i.e. not converted from ext3), right? Are you u= sing >> > > quotas? >> > >> > The filesystem *is* using data=3Djournal mode. =A0If I switch to data= =3Dordered >> > or data=3Dwriteback, the problem goes away. >> =A0 Ah, OK. Then bug https://bugzilla.kernel.org/show_bug.cgi?id=3D34642= is >> probably ext3 incarnation of the same problem and it seems it's still >> present even in the current kernel - that ext3 assertion triggered even >> with 2.6.39 kernel. Frankly data=3Djournal mode is far less tested than = the >> other two modes especially with ext4, so I'm not sure how good idea is t= o >> use it in production. > > Hi Jan, > > if it is so (and it probably is, since I am not testing this mode as > well:), it would be interesting to find out whether there are many users > of this and if there are not, which is probably the case, deprecate it no= w, > so we can remove it later. If we are openly suggesting not to use this, > then there is probably no point in having this option in the first > place. > > I vaguely remember that Ted said something about removing data=3Djournal > mode, but I do not remember details. Ted ? > I think Ted was plotting about removing data=3Dordered... Amir.