From: cwillu <cwillu@cwillu.com>
To: Alexey A Nikitin <moonwalker@syrius.us>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS fsck tool
Date: Fri, 4 Mar 2011 18:05:35 -0600 [thread overview]
Message-ID: <AANLkTin=2=bhmdzUHV-poMwEx9et6y2m3OSba-1Rc9=v@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim1+n4OJcm1iYMQKQZyN9jT2uFUYjAM6=x4pY2g@mail.gmail.com>
On Fri, Mar 4, 2011 at 5:59 PM, Alexey A Nikitin <moonwalker@syrius.us> wrote:
> I have BTRFS RAID0 setup with two disks. After some incident where I
> had to force shutdown machine this array won't mount anymore, even
> after "btrfs device scan". Unfortunately, I don't have backups since I
> can't afford another 4TB of storage. I've read that fsck tool for
> BTRFS that is expected to be released soon should allow recovery from
> this situation, but I can't find info as to where I may find the
> up-to-date release announcements so that I can download it when it's
> out. Can somebody tell me how I can keep track of fsck development
> status?
I'd expect an announcement on this mailing list.
Depending on why it doesn't mount, there's a btrfs-select-super
command in btrfs-progs which may get you up and running again.
next prev parent reply other threads:[~2011-03-05 0:05 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 [this message]
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
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='AANLkTin=2=bhmdzUHV-poMwEx9et6y2m3OSba-1Rc9=v@mail.gmail.com' \
--to=cwillu@cwillu.com \
--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).