Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758113Ab0LBVaU (ORCPT ); Thu, 2 Dec 2010 16:30:20 -0500 Received: from mail-fx0-f46.google.com ([209.85.161.46]:48908 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752829Ab0LBVaR convert rfc822-to-8bit (ORCPT ); Thu, 2 Dec 2010 16:30:17 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Sdq0dBzXIknIiT/VbB/7w3tf+UihXYS2ga2PZ6F9NMYIHwJuG1EOaztYkoIwCujI++ sBQ3lAP/o4/oX4/E/KzRzJpMFi9Fv24s6TVW4FoL1Prf/MnRdReGdzNnSRXjPjHGV9kN HWA/EstEoIac0Qvpcp8UnG2YjjRyp/zWxrnJY= MIME-Version: 1.0 In-Reply-To: <20101201212310.GA15648@redhat.com> References: <20101114205925.GA20451@redhat.com> <4CE05A9E.9090204@redhat.com> <20101201165229.GC13415@redhat.com> <4CF692D1.1010906@redhat.com> <4CF6B3E8.2000406@redhat.com> <20101201212310.GA15648@redhat.com> Date: Thu, 2 Dec 2010 22:30:16 +0100 Message-ID: Subject: Re: hunt for 2.6.37 dm-crypt+ext4 corruption? (was: Re: dm-crypt barrier support is effective) From: Matt To: Mike Snitzer Cc: Milan Broz , Andi Kleen , linux-btrfs , dm-devel , Linux Kernel , htd , Chris Mason , htejun@gmail.com, linux-ext4@vger.kernel.org, Jon Nelson Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2303 Lines: 63 On Wed, Dec 1, 2010 at 10:23 PM, Mike Snitzer wrote: > On Wed, Dec 01 2010 at ?3:45pm -0500, > Milan Broz wrote: > >> >> On 12/01/2010 08:34 PM, Jon Nelson wrote: >> > Perhaps this is useful: for myself, I found that when I started using >> > 2.6.37rc3 that postgresql starting having a *lot* of problems with >> > corruption. Specifically, I noted zeroed pages, corruption in headers, >> > all sorts of stuff on /newly created/ tables, especially during index >> > creation. I had a fairly high hit rate of failure. I backed off to >> > 2.6.34.7 and have *zero* problems (in fact, prior to 2.6.37rc3, I had >> > never had a corruption issue with postgresql). I ran on 2.6.36 for a >> > few weeks as well, without issue. >> > >> > I am using kcrypt with lvm on top of that, and ext4 on top of that. >> >> With unpatched dmcrypt (IOW with Linus' git)? Then it must be ext4 or >> dm-core problem because there were no patches for dm-crypt... > > Matt and Jon, > > If you'd be up to it: could you try testing your dm-crypt+ext4 > corruption reproducers against the following two 2.6.37-rc commits: > > 1) 1de3e3df917459422cb2aecac440febc8879d410 > then > 2) bd2d0210cf22f2bd0cef72eb97cf94fc7d31d8cc > > Then, depending on results of no corruption for those commits, bonus > points for testing the same commits but with Andi and Milan's latest > dm-crypt cpu scalability patch applied too: > https://patchwork.kernel.org/patch/365542/ > > Thanks! > Mike > Yeah sure, I'll have to set up another testing system (on a separate partition / volume group) for its own so that will take some time, first tests will be run probably in the weekend, thanks for those pointers ! I took a look at git-web - you think 5a87b7a5da250c9be6d757758425dfeaf8ed3179 might be relevant, too ? the others seem rather minor compared to those you posted Afaik last time I run vanilla 2.6.37-rc* (which was probably around rc1) I saw no corruption at all but I'll give it a test-run without the dm-crypt patch anyway Thanks & Regards Matt -- 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/