From: Martin <develop@imagmbh.de>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: recover corrupt BTRFS
Date: Mon, 06 Apr 2015 21:08:15 +0200 [thread overview]
Message-ID: <2290805.G7iFbWqiA5@term0> (raw)
In-Reply-To: <CAJCQCtRLN8_Qe+0Hh0o-NCoc7KFWMu_wWbP8fObB3hq_xNgoFw@mail.gmail.com>
Am Montag, 6. April 2015, 09:45:10 schrieb Chris Murphy:
> On Mon, Apr 6, 2015 at 5:40 AM, Martin <develop@imagmbh.de> wrote:
> > Hello!
> >
> > I have to recover a corrupt btrfs. The size is approx 4.5 TB. The fs
> > became
> > corrupt by failure of a hardware-raid.
>
> What raid level? What kind of failure? What is the current raid
> status? What was the mkfs.btrfs command used to create the file system
> OR what is the current profile used for data and metadata?
Hello Chris,
it was a hardware-RAID (3ware-Controller), RAID-5. There was a failure of 2 of
6 disks. Because only one disk was physically damaged, I could "dd" the RAID
to a new big disk with the help of 3Ware/Avago.
The stack was: hardware-raid --- Linux LVM --- btrfs. The metadata-profile was
the default for a single drive, so it should be "dup".
Martin
next prev parent reply other threads:[~2015-04-06 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 11:40 recover corrupt BTRFS Martin
2015-04-06 15:45 ` Chris Murphy
2015-04-06 19:08 ` Martin [this message]
2015-04-06 19:51 ` Chris Murphy
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=2290805.G7iFbWqiA5@term0 \
--to=develop@imagmbh.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 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.