From: Chris Mason <chris.mason@oracle.com>
To: Timo Nentwig <btrfs@nentwig.biz>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: can't read superblock (but could mount)
Date: Thu, 16 Feb 2012 13:14:07 -0500 [thread overview]
Message-ID: <20120216181407.GR21896@shiny> (raw)
In-Reply-To: <alpine.LNX.2.00.1202161856220.1579@localhost>
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.mason@oracle.com>
> >To: Timo Nentwig <btrfs@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
next prev parent reply other threads:[~2012-02-16 18:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 19:30 can't read superblock (but could mount) btrfs
2012-02-10 22:18 ` Chris Mason
2012-02-10 23:39 ` Chris Mason
2012-02-11 6:27 ` btrfs
2012-02-13 13:09 ` Chris Mason
2012-02-14 17:37 ` Timo Nentwig
2012-02-14 18:41 ` Chris Mason
2012-02-14 18:54 ` Timo Nentwig
2012-02-14 21:14 ` Chris Mason
2012-02-15 6:03 ` Timo Nentwig
2012-02-15 13:23 ` Chris Mason
2012-02-16 17:04 ` Timo Nentwig
2012-02-16 18:14 ` Chris Mason [this message]
2012-02-17 3:35 ` Timo Nentwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120216181407.GR21896@shiny \
--to=chris.mason@oracle.com \
--cc=btrfs@nentwig.biz \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).