From: Chester <somethingsome2000@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: The "The status of btrfsck" thread
Date: Thu, 26 Aug 2010 03:43:52 -0500 [thread overview]
Message-ID: <AANLkTikU0YAzvemezrjvhszACPcLUPiiqSO2o=eVP06A@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim3LUO8BqC61LLFh8CuBOVLkEdCU_p=StqBFQpG@mail.gmail.com>
Hi, I'm aware that btrfs doesn't have a functioning fsck tool that
fixes errors.
I was just wondering (I'm sure many are, also) if there is a working
btrfsck somewhere in the pipeline.
If there is some sort of rough estimate to when it'll be available,
please state it here.
If you're not confident about any release date, it's no big deal. I
just want an organized place
to sift through things regarding btrfsck (since it's pretty crucial)
next parent reply other threads:[~2010-08-26 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTim3LUO8BqC61LLFh8CuBOVLkEdCU_p=StqBFQpG@mail.gmail.com>
2010-08-26 8:43 ` Chester [this message]
2010-08-27 0:57 ` The "The status of btrfsck" thread Chris Mason
2010-08-27 3:25 ` Chester
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='AANLkTikU0YAzvemezrjvhszACPcLUPiiqSO2o=eVP06A@mail.gmail.com' \
--to=somethingsome2000@gmail.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).