Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754204Ab0LEKKP (ORCPT ); Sun, 5 Dec 2010 05:10:15 -0500 Received: from moutng.kundenserver.de ([212.227.17.10]:64736 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752423Ab0LEKKM (ORCPT ); Sun, 5 Dec 2010 05:10:12 -0500 Date: Sun, 5 Dec 2010 11:09:54 +0100 From: Heinz Diehl To: Matt Cc: Mike Snitzer , Milan Broz , Andi Kleen , linux-btrfs , dm-devel , Linux Kernel , htd , Chris Mason , htejun@gmail.com, linux-ext4@vger.kernel.org, Jon Nelson Subject: Re: hunt for 2.6.37 dm-crypt+ext4 corruption? (was: Re: dm-crypt barrier support is effective) Message-ID: <20101205100954.GA6564@fritha.org> References: <20101201165229.GC13415@redhat.com> <4CF692D1.1010906@redhat.com> <4CF6B3E8.2000406@redhat.com> <20101201212310.GA15648@redhat.com> <20101204193828.GB13871@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: private site X-OpenPGP-KeyID: 0xA9353F12 X-OpenPGP-Fingerprint: C67E 9A93 1033 DF8A 9321 9F90 DC39 B8C3 A935 3F12 X-OpenPGP-URL: http://www.fritha.org/htd.asc User-Agent: Mutt/1.5.21+20101028 (GNU/Linux) X-Provags-ID: V02:K0:iNTWa2b5Fxu0MSSJD+wqI5qRTbIDP7vaBeSwbxG6KGV S3lcXdQinmgwh9fUGKjUpdgxhODOmZ4xq96p2BeHdjAgANRf9O PVWDDXucg1HXR9NSgbjXffyFcpBwgT+50pa/qI0vyTRD3sENtt QuuwvMOXuXDkMXQkCCB5DhdGd2bdAO5tEDykGSZsCV9tZkogba zbuXGAB7vPSJnqCuiO8vg== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 880 Lines: 20 On 05.12.2010, Matt wrote: > I should have made it clear that the results I get are observed when > using the kernels/checkouts *with* the dm-crypt multi-cpu patch, > without the patch I didn't see that kind of problems (hardlocks, files > missing, etc.) I have to take back my other two emails, stating that no corruption happened with the dm-crypt multi-cpu patch. Today, I encountered filesystem corruption on one, and a complete hardlock on another machine. No logfile entries, no m-sysrq, a complete deadlock. Filesystem was corrupted here too, had to reboot from CD. The machines with plain 2.6.37-rc4 are up and running... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/