Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Chester <somethingsome2000@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs unmountable after failed suspend
Date: Thu, 9 Feb 2012 20:32:18 -0500	[thread overview]
Message-ID: <20120210013218.GB8384@shiny> (raw)
In-Reply-To: <CAAE6i0h+E0vQ4D6gr7MQiwS00hnQGk5R7ubkRa00NdkoaNxcNA@mail.gmail.com>

On Thu, Feb 09, 2012 at 06:54:42PM -0600, Chester wrote:
> Output for btrfs-debug-tree for that specific block in dmesg
> 
> And available here ( http://pastebin.com/AgdvS5JM ) in case the lines
> wrap and look ugly

Ok, good news.  This bad block is in the extent allocation tree, which
means it is easy to replace.

Is it possible for you to make a block level backup of this disk?  That
way we can experiment a little and fix it up.

Either way, I'll recreate this corruption here in the morning and patch
fsck to fix it.

-chris

  reply	other threads:[~2012-02-10  1:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 22:58 btrfs unmountable after failed suspend Chester
2012-02-07 23:22 ` Chester
2012-02-08  0:10   ` Chester
2012-02-08 12:55     ` Chris Mason
2012-02-08 19:22       ` Chester
2012-02-08 20:26         ` Chris Mason
2012-02-08 20:46           ` Chester
2012-02-09  0:17             ` Chester
2012-02-10  0:54               ` Chester
2012-02-10  1:32                 ` Chris Mason [this message]
2012-02-10  1:40                   ` Chester
2012-02-10 21:27                 ` Chris Mason
2012-02-11 21:42                   ` Chester
2012-03-31  2:32                     ` Chester

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=20120210013218.GB8384@shiny \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=somethingsome2000@gmail.com \
    /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