From: Ted Ts'o Subject: Re: hunt for 2.6.37 dm-crypt+ext4 corruption? (was: Re: dm-crypt barrier support is effective) Date: Thu, 9 Dec 2010 13:01:11 -0500 Message-ID: <20101209180111.GF2921@thunk.org> References: <4CF6B3E8.2000406@redhat.com> <20101201212310.GA15648@redhat.com> <20101204193828.GB13871@redhat.com> <20101207142145.GA27861@think> <20101207182243.GB21112@redhat.com> <20101207193514.GA2921@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Mike Snitzer , Chris Mason , Matt , Milan Broz , Andi Kleen , linux-btrfs , dm-devel , Linux Kernel , htd , htejun@gmail.com, linux-ext4@vger.kernel.org To: Jon Nelson Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org 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? pgsql_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. 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 it would be going anywhere else. Still trying.... - Ted