[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101209201359.GG2921@thunk.org>
Date: Thu, 9 Dec 2010 15:13:59 -0500
From: Ted Ts'o <tytso@....edu>
To: Jon Nelson <jnelson@...poni.net>
Cc: Mike Snitzer <snitzer@...hat.com>,
Chris Mason <chris.mason@...cle.com>,
Matt <jackdachef@...il.com>, Milan Broz <mbroz@...hat.com>,
Andi Kleen <andi@...stfloor.org>,
linux-btrfs <linux-btrfs@...r.kernel.org>,
dm-devel <dm-devel@...hat.com>,
Linux Kernel <linux-kernel@...r.kernel.org>,
htd <htd@...cy-poultry.org>, htejun@...il.com,
linux-ext4@...r.kernel.org
Subject: Re: hunt for 2.6.37 dm-crypt+ext4 corruption? (was: Re: dm-crypt
barrier support is effective)
On Thu, Dec 09, 2010 at 12:10:58PM -0600, Jon Nelson wrote:
>
> You should be OK, there. Are you using encryption or no?
> I had difficulty replicating the issue without encryption.
Yes, I'm using encryption. LUKS with aes-xts-plain-sha256, and then
LVM on top of LUKS.
> > 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.
>
> 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.
Ah, I'm not using virtualization. I'm running on a X410 laptop, on
raw hardware. Perhaps virtualization slows things down enough that it
triggers? Or maybe you're running with a more constrained memory than
I? How much memory do you have configured in your VM?
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists