From: Jon Nelson Subject: Re: hunt for 2.6.37 dm-crypt+ext4 corruption? (was: Re: dm-crypt barrier support is effective) Date: Thu, 9 Dec 2010 12:10:58 -0600 Message-ID: References: <4CF6B3E8.2000406@redhat.com> <20101201212310.GA15648@redhat.com> <20101204193828.GB13871@redhat.com> <20101207142145.GA27861@think> <20101207182243.GB21112@redhat.com> <20101207193514.GA2921@thunk.org> <20101209180111.GF2921@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE To: "Ted Ts'o" , Jon Nelson , Mike Snitzer , Chris Mason , Matt , Milan Broz Received: from mail-bw0-f45.google.com ([209.85.214.45]:37075 "EHLO mail-bw0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756283Ab0LISLU convert rfc822-to-8bit (ORCPT ); Thu, 9 Dec 2010 13:11:20 -0500 In-Reply-To: <20101209180111.GF2921@thunk.org> Sender: linux-ext4-owner@vger.kernel.org List-ID: On Thu, Dec 9, 2010 at 12:01 PM, Ted Ts'o wrote: > On Tue, Dec 07, 2010 at 09:37:20PM -0600, Jon Nelson wrote: >> One difference is the location of the transaction logs (pg_xlog). In >> my case, /var/lib/pgsql/data *is* mountpoint for the test volume >> (actually, it's a symlink to the mount point). In your case, that is >> not so. Perhaps that makes a difference? =C2=A0pgsql_tmp might also = be on >> two different volumes in your case (I can't be sure). > > I just tried tried to run t.sql five times with /var/lib/postgres as = a > mountpoint for a 5400 rpm disk, and I still haven't been able to > replicate it. You should be OK, there. Are you using encryption or no? I had difficulty replicating the issue without encryption. > If you can point out how to query pgsql_tmp (I'm using a completely > default postgres install), that would be helpful, but I don't think i= t > would be going anywhere else. Normally it's /var/lib/pgsql/data/pgsql_tmp (or /var/lib/postgres/data/pgsql_tmp in your case). By placing /var/lib/{postgresql,pgsql}/data on the LUKS + ext4 volume, on both openSUSE 11.3 and Kubuntu, I was able to replicate the problem easily, in VirtualBox. I can give qemu a try. In both cases I was using a 2.6.37x kernel. --=20 Jon -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html