From: Christoph Hellwig <hch@infradead.org>
To: Miao Xie <miaox@cn.fujitsu.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Linux Btrfs <linux-btrfs@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: use btrfsck to check btrfs filesystems
Date: Wed, 4 Jan 2012 13:42:24 -0500 [thread overview]
Message-ID: <20120104184224.GB8131@infradead.org> (raw)
In-Reply-To: <4EE851B8.8010505@cn.fujitsu.com>
On Wed, Dec 14, 2011 at 03:35:20PM +0800, Miao Xie wrote:
> We failed to get fsck program to check the btrfs file system, it is
> because btrfs uses its independent check tool which is named btrfsck
> to check the file system, so the common checker -- fsck -- could not
> find it, and reported there is no checker.
>
> This patch fix it by using btrfsck directly.
>
> Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
Thanks, applied.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-01-04 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 7:35 [PATCH] xfstests: open btrfsck to check the btrfs filesystem Miao Xie
2012-01-04 18:42 ` Christoph Hellwig [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=20120104184224.GB8131@infradead.org \
--to=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--cc=xfs@oss.sgi.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