From: David Sterba <dsterba@suse.cz>
To: Lu Fengqi <lufq.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: Add new option for specify chunk root bytenr
Date: Wed, 9 Mar 2016 14:42:51 +0100 [thread overview]
Message-ID: <20160309134251.GF738@twin.jikos.cz> (raw)
In-Reply-To: <1457326661-9646-2-git-send-email-lufq.fnst@cn.fujitsu.com>
On Mon, Mar 07, 2016 at 12:57:41PM +0800, Lu Fengqi wrote:
> Add new btrfsck option, '--chunk-root', to specify chunk root bytenr.And
> allow open_ctree_fs_info() function accept chunk_root_bytenr to override
> the bytenr in superblock.This will be mainly used when chunk tree
> corruption.
Good idea. I'll remove the short option for now as this does not seem to
be frequently needed, we can reserve -c for something else.
prev parent reply other threads:[~2016-03-09 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 4:57 [PATCH] btrfs-progs: Add new option for specify chunk root bytenr Lu Fengqi
2016-03-07 4:57 ` Lu Fengqi
2016-03-09 13:42 ` David Sterba [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=20160309134251.GF738@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lufq.fnst@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).