From: Hugo Mills <hugo@carfax.org.uk>
To: Alan Brand <alan@georgiabrands.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Raid0 rescue
Date: Thu, 27 Jul 2017 15:10:38 +0000 [thread overview]
Message-ID: <20170727151038.GT7140@carfax.org.uk> (raw)
In-Reply-To: <CAFcRpx4q7N1zG4gz-g6MgkU6c-F_gQ6+2-4ibgm+nyRCp5pTXQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
On Thu, Jul 27, 2017 at 10:49:37AM -0400, Alan Brand wrote:
> I know I am screwed but hope someone here can point at a possible solution.
>
> I had a pair of btrfs drives in a raid0 configuration. One of the
> drives was pulled by mistake, put in a windows box, and a quick NTFS
> format was done. Then much screaming occurred.
>
> I know the data is still there.
Well, except for all the parts overwritten by a blank NTFS metadata
structure.
> Is there anyway to rebuild the raid
> bringing in the bad disk? I know some info is still good, for example
> metadata0 is corrupt but 1 and 2 are good.
I assume you mean superblock there.
> The trees look bad which is probably the killer.
We really should improve the error messages at some point. Whatever
you're inferring from the kernel logs is probably not quite right. :)
What's the metadata configuration on this FS? Also RAID-0? or RAID-1?
> I can't run a normal recovery as only half of each file is there.
Welcome to RAID-0...
Hugo.
--
Hugo Mills | We don't just borrow words; on occasion, English has
hugo@... carfax.org.uk | pursued other languages down alleyways to beat them
http://carfax.org.uk/ | unconscious and rifle their pockets for new
PGP: E2AB1DE4 | vocabulary. James D. Nicoll
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-07-27 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 14:49 Raid0 rescue Alan Brand
2017-07-27 15:10 ` Hugo Mills [this message]
2017-07-27 19:43 ` Alan Brand
2017-07-27 19:53 ` Hugo Mills
2017-07-27 20:25 ` Duncan
2017-07-27 23:38 ` Adam Borowski
2017-08-17 1:48 ` Chris Murphy
2017-08-17 5:13 ` Chris Murphy
2017-08-01 18:24 ` Chris Murphy
[not found] ` <CAFcRpx5JkNnTOtrVbjTe6e7tde=Sw3_78TAJThEd+cYtx62h4w@mail.gmail.com>
2017-08-01 18:48 ` Chris Murphy
-- strict thread matches above, loose matches on Subject: below --
2017-07-27 20:07 Alan Brand
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=20170727151038.GT7140@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=alan@georgiabrands.com \
--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