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... Anyway, thanks for hint how to reproduce it. Milan -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
