linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Florian Gamböck" <mail@floga.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: superblock checksum mismatch after crash, cannot mount
Date: Sat, 23 Aug 2014 10:38:47 +0200	[thread overview]
Message-ID: <53F85317.8060900@floga.de> (raw)
In-Reply-To: <pan$a4556$243aa48a$bd2898a8$c2006893@cox.net>

Hi Duncan,

thank you for your detailed explanations!

Am 23.08.2014 07:27, schrieb Duncan:
> btrfs-show-super is your tool for inspecting the superblocks.  See the
> manpage for the details.
>
> Then use btrfs rescue super-recover to overwrite the bad superblock with
> one that checks out as good (csum match).  See the btrfs-rescue manpage
> for the details there.

Yes, show-super told me, that the first super block did "NOT MATCH", but 
the second one seemed to be in order ("MATCHED"). The SD card is 16 GiB 
big, so there was no third super block.

Rescue also listed the first one as bad and the second one as good and 
it seemed to run successfully, no errors whatsoever.

However, after "recovering", every single partition on the card broke. 
There were three partitions: 1 = fat32 ("/boot"), 2 = swap, 3 = btrfs 
("/"). Naturally I ran the rescue command on partition 3, I hope that 
was not a mistake. Afterwards, as I said, none of the partitions were 
recognized anymore. Not even btrfs recognized the third partition.

Since I've thought I messed up entirely, I just gave up, re-formatted 
the card and let my backups do the job.

It's quite annoying though, how often I get those problems. May it be 
that the Raspberry Pi is too slow to let btrfs do its background magic, 
may it be that btrfs is not that suitable for SD cards (in my case it's 
a class 10 microSDHC, 16GiB), or may it be that btrfs is still not that 
reliable when it comes to "unclean" shutdowns.

Nevertheless, I will keep your explanations around for future reference, 
they were really helpful! Thanks again!

--
Best wishes
FloGa

  reply	other threads:[~2014-08-23  8:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 22:00 superblock checksum mismatch after crash, cannot mount Florian Gamböck
2014-08-22 22:17 ` Florian Gamböck
2014-08-23  5:27 ` Duncan
2014-08-23  8:38   ` Florian Gamböck [this message]
2014-08-23  9:34     ` Duncan
2014-08-23 14:14       ` Florian Gamböck
2014-08-24 20:29         ` Chris Murphy
2014-08-23 16:38       ` Zygo Blaxell
2014-08-24  0:56         ` Duncan
2014-08-24  2:57           ` Chris Murphy
2014-08-24 11:08           ` Leen Besselink
2014-08-24 12:49             ` Chris Samuel
2014-08-24 12:59             ` Duncan
2014-08-24 14:09             ` Florian Gamböck
  -- strict thread matches above, loose matches on Subject: below --
2014-08-24 16:59 Flash ROM
2014-08-24 18:41 ` Florian Gamböck
2014-08-24 19:48 ` Chris Murphy
2014-08-25 11:42   ` Austin S Hemmelgarn

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=53F85317.8060900@floga.de \
    --to=mail@floga.de \
    --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).