From: Travis Shivers <ttshivers@gmail.com>
To: Chris Mason <chris.mason@oracle.com>,
Travis Shivers <ttshivers@gmail.com>, 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 17:58:47 -0600 [thread overview]
Message-ID: <CAPeorG8xpyeetBRSAt092Ac2qMcvFLLi2utXvfSgYWbzt0M3zw@mail.gmail.com> (raw)
In-Reply-To: <20120229234437.GT5054@shiny>
I was running a fairly old version of the kernel:
Linux server 3.0.0-16-generic #28-Ubuntu SMP Fri Jan 27 17:44:39 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
On Wed, Feb 29, 2012 at 5:44 PM, Chris Mason <chris.mason@oracle.com> w=
rote:
> 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 fi=
le
>> 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=3DN82E16816132029
>>
>> 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 dri=
ve
>> 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. =A0Which kernel were you running =
when
> you had the power outages?
>
> I'm testing out the patch to skip the extent allocation tree at mount=
=2E
> That will be the easiest way to get to the data (readonly, but it'll
> work).
>
> -chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-02-29 23:58 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
2012-02-29 23:58 ` Travis Shivers [this message]
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=CAPeorG8xpyeetBRSAt092Ac2qMcvFLLi2utXvfSgYWbzt0M3zw@mail.gmail.com \
--to=ttshivers@gmail.com \
--cc=chris.mason@oracle.com \
--cc=cwillu@cwillu.com \
--cc=gurudas.pai@oracle.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;
as well as URLs for NNTP newsgroup(s).