From: Chris Mason <chris.mason@oracle.com>
To: Travis Shivers <ttshivers@gmail.com>
Cc: cwillu <cwillu@cwillu.com>, Gurudas Pai <gurudas.pai@oracle.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Btrfs Storage Array Corrupted
Date: Wed, 29 Feb 2012 18:44:37 -0500 [thread overview]
Message-ID: <20120229234437.GT5054@shiny> (raw)
In-Reply-To: <CAPeorG-rC6_bM+vX0Jyap74TdRr7cgQjBfb_PBvNHDz-yyQkWw@mail.gmail.com>
On Wed, Feb 29, 2012 at 05:11:24PM -0600, Travis Shivers wrote:
> Thank you all for helping. My btrfs array consists of 4 disks: 2 (2
> TB) disks and 2(500 GB) disks. Since I have disks of different sizes,
> I have the array being mirrored so that there are two copies of a file
> on two separate disks. The data and metadata are mirrored.
>
> I originally made the array by using this command:
>
> # mkfs.btrfs -m raid1 -d raid1 /dev/sd[abcd]
> (The drives were originally those letters)
>
>
> All of the disks sit in an external 4 bay ESATA enclosure going into a
> PCI-E RAID card set up as JBOD, so I can use btrfs' software
> mirroring. This is the enclosure that I have:
> http://www.newegg.com/Product/Product.aspx?Item=N82E16816132029
>
> The corruption was unexpected. I am not entirely sure what caused it,
> but a few days before the corruption, there were several power
> outages. I do not think that the problem is with the actual hard drive
> hardware since they are fairly new (6 months old) and they pass all
> SMART tests. After a reboot, the btrfs array refused to mount and
> started giving off errors. I do weekly scrubs, balances, and
> defragmentation.
Ok, all of this should have worked. Which kernel were you running when
you had the power outages?
I'm testing out the patch to skip the extent allocation tree at mount.
That will be the easiest way to get to the data (readonly, but it'll
work).
-chris
next prev parent reply other threads:[~2012-02-29 23:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 0:13 Btrfs Storage Array Corrupted Travis Shivers
2012-02-29 0:34 ` Fajar A. Nugraha
2012-02-29 1:41 ` Gurudas Pai
2012-02-29 2:50 ` Chris Mason
2012-02-29 3:00 ` Travis Shivers
2012-02-29 3:16 ` cwillu
2012-02-29 3:36 ` Travis Shivers
2012-02-29 13:59 ` Chris Mason
2012-02-29 21:57 ` Travis Shivers
2012-02-29 22:14 ` Chris Mason
2012-02-29 23:11 ` Travis Shivers
2012-02-29 23:44 ` Chris Mason [this message]
2012-02-29 23:58 ` Travis Shivers
2012-03-16 17:30 ` Travis Shivers
[not found] ` <CAPeorG-Zrr-fTaYmHHKQ5=0jL9ZqjbTypGzo7je3g=MJDPmXcA@mail.gmail.com>
2012-03-26 23:15 ` Travis Shivers
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=20120229234437.GT5054@shiny \
--to=chris.mason@oracle.com \
--cc=cwillu@cwillu.com \
--cc=gurudas.pai@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=ttshivers@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;
as well as URLs for NNTP newsgroup(s).