[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] hunt for 2.6.37 dm-crypt+ext4 corruption? (was: Re: dm-crypt barrier support is effective)
- From: "Ted Ts'o" <tytso mit edu>
- To: Jon Nelson <jnelson jamponi net>
- Cc: htejun <htejun gmail com>, Matt <jackdachef gmail com>, Mike Snitzer <snitzer redhat com>, Linux Kernel <linux-kernel vger kernel org>, dm-devel <dm-devel redhat com>, Andi Kleen <andi firstfloor org>, Chris Mason <chris mason oracle com>, htd <htd fancy-poultry org>, linux-ext4 <linux-ext4 vger kernel org>, linux-btrfs <linux-btrfs vger kernel org>, Milan Broz <mbroz redhat com>
- Subject: Re: [dm-devel] hunt for 2.6.37 dm-crypt+ext4 corruption? (was: Re: dm-crypt barrier support is effective)
- Date: Sat, 11 Dec 2010 21:34:15 -0500
One experiment --- can you try this with the file system mounted with
data=writeback, and see if the problem reproduces in that journalling
mode?
I want to rule out (if possible) journal_submit_inode_data_buffers()
racing with mpage_da_submit_io(). I don't think that's the issue, but
I'd prefer to do the experiment to make sure. So if you can use a
kernel and system configuration which triggers the problem, and then
try changing the mount options to include data=writeback, and then
rerun the test, and let me know if the problem still reproduces, I'd
be really grateful.
Thanks,
- Ted
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]