On Thu, Feb 16, 2012 at 06:04:47PM +0100, Timo Nentwig wrote: > > > On Wed, 15 Feb 2012, Chris Mason wrote: > > >Date: Wed, 15 Feb 2012 08:23:22 -0500 > >From: Chris Mason <chris.ma...@oracle.com> > >To: Timo Nentwig <bt...@nentwig.biz> > >Cc: linux-btrfs@vger.kernel.org > >Subject: Re: can't read superblock (but could mount) > > > >On Wed, Feb 15, 2012 at 07:03:49AM +0100, Timo Nentwig wrote: > >>On Tue, 14 Feb 2012, Chris Mason wrote: > >> > >>>Ok, 3.2 shouldn't have done this. Was this an external drive? What > >>>else do you have on the system? > >> > >>Nothing special actually. Standard arch linux with virtualbox kernel > >>modules. > >>It's a SSD if this should matter. Mounted with ssd,compress=lzo,noatime. > > > >Ok, it sounds like we've got some memory corruption problems in here. > >Hopefully not from virtualbox, but I'd start with an memtest. > > Wow, now I'm really impressed! :) You are probably right. I overclocked memory > and ran memtest for like 1-2h without errors and had a rock solid > system for quite a while when I recently started to witness all > kinds of random and reoccuring crashes. Actually blamed the broken > FS rather than to run memtest again. Mea culpa. > > So, I hit 1 error after a while, somewhat lowered clock freq and no > error in 17h straight. I'll recreate the FS on that box.
Grin, never be impressed when kernel guys blame the memory. We might as well be saying its cosmic rays. Really though, for this particular type of corruption it is usually some hardware problem, or a memory corruption bug in the kernel. Thanks for humoring me and running the memtest. -chris -- 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
