On Wed, Dec 01 2010 at 3:45pm -0500, Milan Broz <mbroz@xxxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
