From: Ted Ts'o Subject: Re: 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 Message-ID: <20101212023415.GG3059@thunk.org> References: <20101209201359.GG2921@thunk.org> <20101209231616.GA12515@basil.fritz.box> <1291945065-sup-1838@think> <20101210023852.GB3059@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Matt , Chris Mason , Andi Kleen , Mike Snitzer , Milan Broz , linux-btrfs , dm-devel , Linux Kernel , htd , htejun , linux-ext4 To: Jon Nelson Return-path: Received: from thunk.org ([69.25.196.29]:56796 "EHLO thunker.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752071Ab0LLCeb (ORCPT ); Sat, 11 Dec 2010 21:34:31 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-ext4-owner@vger.kernel.org List-ID: 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