public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ted Phelps <phelps@gnusto.com>
To: "Yan\, Zheng " <yanzheng@21cn.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfsck core dump
Date: Tue, 29 Dec 2009 19:17:27 +1000	[thread overview]
Message-ID: <26236.1262078247@laika.gnusto.com> (raw)
In-Reply-To: Your message of Tue, 29 Dec 2009 16:46:09 +0800. <3d0408630912290046i6514f924j7e4ed4fb87ea0463@mail.gmail.com>

Yan, Zheng writes:
> On Tue, Dec 29, 2009 at 12:26 PM, Ted Phelps <phelps@gnusto.com> wrot=
e:
> > My btrfs test partition started failing btrfsck (0.19) today, which=
 may
> > be of interest. =C2=A0What's probably more interesting is that git =
head
> > version of btrfsck reliably crashes when pointed at the filesystem.
> > What's more interesting still is that, after unmounting the filesys=
tem,
> > btrfsck (both 0.19 and git head) finds no errors. =C2=A0I have to a=
dmit that
> > I find this a bit confusing. =C2=A0Is this expected behavior?
>=20
> btrfsck doesn't support checking mounted fs.

Ok, that's reasonable.  I recognize that the tools are very new and tha=
t
there are many things to be done, but it would be nice if this
restriction were mentioned in the btrfsck man page so that the next
person to try this doesn't think that his filesystem is corrupt.

Of course, it would be nicer still if btrfsck refused to operate on a
mounted filesystem, and if it didn't crash when presented with a
"damaged" filesystem, though I can see that such bells and whistles
might not be your top priority at the moment.

Thanks,
-Ted
--
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

      reply	other threads:[~2009-12-29  9:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29  4:26 btrfsck core dump Ted Phelps
2009-12-29  8:46 ` Yan, Zheng 
2009-12-29  9:17   ` Ted Phelps [this message]

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=26236.1262078247@laika.gnusto.com \
    --to=phelps@gnusto.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=yanzheng@21cn.com \
    /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