All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: Corrupt btrfs filesystem recovery... What best instructions?
Date: Sun, 29 Sep 2013 03:10:37 +0100	[thread overview]
Message-ID: <l2826k$1uc$1@ger.gmane.org> (raw)
In-Reply-To: <l27mn1$squ$1@ger.gmane.org>

On 28/09/13 23:54, Martin wrote:
> On 28/09/13 20:26, Martin wrote:
> 
>> ... btrfsck bombs out with LOTs of errors...
>>
>> How best to recover from this?
>>
>> (This is a 'backup' disk so not 'critical' but it would be nice to avoid
>> rewriting about 1.5TB of data over the network...)
>>
>>
>> Is there an obvious sequence/recipe to follow for recovery?
> 
> 
> I've got the drive reliably working with the sata limited to 3Gbit/s.
> What is the best sequence to try to tidy-up and carry on with the 1.5TB
> or so of data on there, rather than working from scratch?
> 
> 
> So far, I've only run btrfsck since the corruption...

So...

Any options for btrfsck to fix things?

Or is anything/everything that is fixable automatically fixed on the
next mount?

Or should:

btrfs scrub /dev/sdX

be run first?

Or?


What does btrfs do (or can do) for recovery?

Advice welcomed,

Thanks,
Martin





  reply	other threads:[~2013-09-29  2:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-28 19:26 Corrupt btrfs filesystem recovery... (Due to *sata* errors) Martin
2013-09-28 20:51 ` Chris Murphy
2013-09-28 22:51   ` Martin
2013-09-29  2:06     ` Chris Murphy
2013-09-29  2:31       ` Martin
2013-09-28 22:54 ` Martin
2013-09-29  2:10   ` Martin [this message]
2013-09-29  5:11     ` Corrupt btrfs filesystem recovery... What best instructions? Duncan
2013-09-29 21:29       ` Martin
2013-09-29 21:55         ` Martin
2013-09-30  7:51           ` Duncan
2013-10-03  0:49         ` Martin
2013-10-03  1:31           ` Chris Murphy
2013-10-03 16:56           ` Martin
2013-10-04 15:43             ` Martin
2013-10-05 11:32               ` Martin
2013-10-05 13:18                 ` Martin
2013-10-07 14:56                   ` btrfsck --repair --init-extent-tree: segfault error 4 Martin
2013-10-07 19:03                     ` Chris Murphy
2013-10-09 16:03                       ` Martin
2013-10-05 12:05 ` ASM1083 rev01 PCIe to PCI Bridge chip (Was: Corrupt btrfs filesystem recovery... (Due to *sata* errors)) Martin

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='l2826k$1uc$1@ger.gmane.org' \
    --to=m_btrfs@ml1.co.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.