From: Marc MERLIN <marc@merlins.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Mitch Harder <mitch.harder@sabayonlinux.org>
Subject: Re: btrfsck failes
Date: Thu, 16 Jan 2014 04:19:06 -0800 [thread overview]
Message-ID: <20140116121906.GP10639@merlins.org> (raw)
In-Reply-To: <5A3CA53B-B359-4DE0-A31B-49F98A1EBF7C@colorremedies.com>
On Wed, Jan 15, 2014 at 10:16:13AM -0700, Chris Murphy wrote:
>
> On Jan 15, 2014, at 9:15 AM, Mitch Harder <mitch.harder@sabayonlinux.org> wrote:
>
> > On Mon, Jan 13, 2014 at 6:37 PM, Chris Murphy <lists@colorremedies.com> wrote:
> >>
> >> On Jan 13, 2014, at 3:58 PM, Holger Brandsmeier <brandsmeier@gmail.com> wrote:
> >>>
> >>> Currently btrfsck failes to repair my partition, I get the output:
> >>>
> >>> [root@ho-think bholger]# btrfsck --repair /dev/sda5
> >>
> >> This is almost the last resort and you probably should be posting to the list before using repair.
> >>
> >>
> >
> > This is like saying:
> >
> > "Yes, btrfs does now have a working btrfsck, but only for the select
> > few who manage to get through on the mailing list for support."
> >
> > I'd like to think that's not the case.
>
> Yet that's exactly what the wiki suggests: "If you have a broken filesystem, it is probably better to use btrfsck with advice from one of the btrfs developers, just in case something goes wrong. (But even if it does go badly wrong, you've still got your backups, right?)"
>
> I think it's understandably annoying that the repair tool could make things worse rather than fail gracefully, because restoring from backups is tedious. But the only way it gets better is if people break both the file system and the repair tools in ways the devs can't possibly predict.
I hate to be a broken record :) but telling people they should read/have
read a wiki when they are in the middle of fixing a filesystem is not
the right way to go.
On my laptop while travelling, it would even be my only way to boot and
maybe I can't get to the internet until my FS is fixed (maybe, maybe
not, but you get the idea).
My main point again (sorry) is still that the man page and usage info of btrfsck
should really warn users "this is likely NOT what you want to run,
please read the manpage, or HOWTO in /usr/share/doc/ with details about
mount recovery and other things to try first".
Think of it as a good thing, it means more btrfs users, and they are
used to working a certain way. It's for btrfs to adapt to how they're
used to working when possible.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2014-01-16 12:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 22:58 btrfsck failes Holger Brandsmeier
2014-01-13 23:15 ` Holger Brandsmeier
2014-01-13 23:53 ` Holger Brandsmeier
2014-01-14 0:37 ` Chris Murphy
2014-01-15 15:08 ` Marc MERLIN
2014-01-15 16:15 ` Mitch Harder
2014-01-15 17:16 ` Chris Murphy
2014-01-16 12:19 ` Marc MERLIN [this message]
2014-01-16 20:30 ` Holger Brandsmeier
[not found] <CAFP7zVtDEfDjKA1GvBq_QMs6gKv9t=K_qNyv6dcxawe5iuj8Kw@mail.gmail.com>
2014-01-15 4:06 ` Chris Murphy
[not found] ` <CAFP7zVuB=A2Lty275-VdixjzG6twXKmJo0qB3gZEH=9noQbpRQ@mail.gmail.com>
2014-01-15 7:53 ` Fwd: " Holger Brandsmeier
2014-01-15 15:15 ` Marc MERLIN
2014-01-15 17:07 ` Chris Murphy
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=20140116121906.GP10639@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=mitch.harder@sabayonlinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.