linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: dsterba@suse.cz, Qu Wenruo <quwenruo@cn.fujitsu.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: convert: Print different error message if convert partly failed.
Date: Sat, 26 Sep 2015 16:03:46 +0800	[thread overview]
Message-ID: <56065162.2030604@gmx.com> (raw)
In-Reply-To: <20150925175749.GQ11442@twin.jikos.cz>



在 2015年09月26日 01:57, David Sterba 写道:
> On Tue, Jun 09, 2015 at 03:57:40PM +0800, Qu Wenruo wrote:
>> When testing under libguestfs, btrfs-convert will never succeed to fix
>> chunk map, and always fails.
>>
>> But in that case, it's already a mountable btrfs.
>> So better to info user with different error message for that case.
>>
>> The root cause of it is still under investigation.
>>
>> Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
>
> I've adjusted wording of the error message and applied, thanks. What are
> the consequences of the unfinished conversion process when such
> filesystem is mounted?

The whole chunk tree will not be in system chunk but metadata chunk, 
until COW happens.

But the funny thing is, even the system chunk is empty after the 
convert, with empty bg auto remove in recent kernels, it will try to 
remove empty system chunk, and cause COW...
And magically, things will become normal again(If chunk tree only has leaf).

Quite tricky to debug why open_ctree() will fail, as libguestfs is such 
a strange environment, not good method to debug and even no way to use 
gdb...

Thanks,
Qu
> --
> 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:[~2015-09-26  8:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09  7:57 [PATCH] btrfs-progs: convert: Print different error message if convert partly failed Qu Wenruo
2015-09-25 17:57 ` David Sterba
2015-09-26  8:03   ` Qu Wenruo [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=56065162.2030604@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo@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).