From: Spelic <spelic@shiftmail.org>
To: Alexey A Nikitin <moonwalker@syrius.us>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS fsck tool
Date: Tue, 08 Mar 2011 03:17:48 +0100 [thread overview]
Message-ID: <4D7591CC.6060301@shiftmail.org> (raw)
In-Reply-To: <AANLkTim1+n4OJcm1iYMQKQZyN9jT2uFUYjAM6=x4pY2g@mail.gmail.com>
On 03/05/2011 12:59 AM, Alexey A Nikitin wrote:
> Hi, everybody
>
> I have BTRFS RAID0 setup with two disks. After some incident where I
> had to force shutdown machine this array won't mount anymore
Have you "reset" the machine or cut the power?
I don't really know btrfs, but in btrfs wiki there is written:
"Note that Btrfs does not yet have a fsck tool that can fix errors.
While Btrfs is stable on a stable machine, it is currently possible to
corrupt a filesystem irrecoverably if your machine crashes or loses
power on disks that don't handle flush requests correctly. This will be
fixed when the fsck tool is ready."
is this your scenario? If you leave the power and stop submitting writes
to the disks (like with a reset) the filesystem should be preserved, if
that sentence is true.
Did you cut the power while there was some process writing to it? If the
kernel was panicked it is probably safe to cut the power (because the
last write happened long time ago and disks had time to put that to the
platters)
Also what disks brand/model do you have? The sentence speaks about disks
which don't honour flush+FUA requests, I think. Enterprise disks should
honour that, consumer disks might not.
I am interesed in what happened because I am evaluating using btrfs for
very large backups (still losing those wouldn't be totally nice)
Thank you
next prev parent reply other threads:[~2011-03-08 2:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 23:59 BTRFS fsck tool Alexey A Nikitin
2011-03-05 0:05 ` cwillu
2011-03-05 1:20 ` Alexey A Nikitin
2011-03-05 3:00 ` cwillu
2011-03-05 3:27 ` Alexey A Nikitin
2011-03-05 7:12 ` Helmut Hullen
2011-03-05 10:55 ` Alexey A Nikitin
2011-03-08 2:17 ` Spelic [this message]
2011-03-08 4:52 ` Alexey A Nikitin
2011-03-08 6:52 ` Peter Stuge
2011-03-10 12:21 ` Clemens Eisserer
2011-03-10 13:02 ` Chris Mason
2011-03-10 13:29 ` Peter Stuge
2011-03-10 13:58 ` Chris Mason
2011-03-10 17:30 ` Alexey A Nikitin
2011-03-10 17:41 ` Chris Mason
2011-03-12 22:49 ` Spelic
2011-03-12 23:53 ` Ric Wheeler
2011-03-15 14:18 ` Hubert Kario
2011-03-15 14:22 ` Peter Stuge
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=4D7591CC.6060301@shiftmail.org \
--to=spelic@shiftmail.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=moonwalker@syrius.us \
/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).