From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <dsterba@suse.cz>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/8] Introduce offline fsid/chunk tree uuid change for btrfstune.
Date: Wed, 6 May 2015 08:49:33 +0800 [thread overview]
Message-ID: <5549651D.6020005@cn.fujitsu.com> (raw)
In-Reply-To: <20150505152055.GH5099@twin.jikos.cz>
-------- Original Message --------
Subject: Re: [PATCH 0/8] Introduce offline fsid/chunk tree uuid change
for btrfstune.
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Date: 2015年05月05日 23:20
> On Tue, May 05, 2015 at 02:16:38PM +0800, Qu Wenruo wrote:
>> This patchset will introduce offline fsid/chunk tree uuid change
>> function to btrfstune command, with "-u" and "-U" options respectively.
>>
>> The implement is in-place btrfs_header modification, without transaction
>> protection. So the uuid change can be done on any valid image even it is
>> already full.
>>
>> Since we don't use transaction to protect the convert, it's possible one
>> can stop the running convert progress, causing the fs in a inconsistent
>> status and unable to be mounted.
>> To avoid such problem, we introduce new open ctree flags
>> OPEN_CTREE_IGNORE_FSID, allowing btrfstune to finish the convert.
>
> Code looks good to me. I'm not sure whether it should land in btrfstune
> or in 'btrfs' proper.
>
> * btrfstune should go away at some point, so I'd rather not add new
> features there
>
> * 'btrfs property set -t filesystem uuid' seems best to me at this moment
Good idea.
I'll change it to property in next version.
>
> A minor suggestion: set BTRFS_SUPER_FLAG_ERROR on the filesystem during
> the conversion and drop it after it finishes successfully. It's merely a
> hint that there's something wrong with the filesytem, the mount will
> fail because filesystem uuid would not match the device id.
>
Nice idea too.
But I'd like to use more specific flags like
BTRFS_SUPER_FLAG_UUID_CHANGING to give better info if kernel can't mount it.
Thanks for all these advice!
Qu
next prev parent reply other threads:[~2015-05-06 0:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 6:16 [PATCH 0/8] Introduce offline fsid/chunk tree uuid change for btrfstune Qu Wenruo
2015-05-05 6:16 ` [PATCH 1/8] btrfs-progs: Allow open_ctree to ignore fsid mismatch Qu Wenruo
2015-05-05 6:16 ` [PATCH 2/8] btrfs-progs: Export write_tree_block() Qu Wenruo
2015-05-05 6:16 ` [PATCH 3/8] btrfs-progs: Introduce change_header_uuid() function Qu Wenruo
2015-05-05 6:16 ` [PATCH 4/8] btrfs-progs: Introduce change_extents_uuid() function Qu Wenruo
2015-05-05 6:16 ` [PATCH 5/8] btrfs-progs: Introduce function change_device_uuid() Qu Wenruo
2015-05-05 6:16 ` [PATCH 6/8] btrfs-progs: Introduce change_devices_uuid() function Qu Wenruo
2015-05-05 6:16 ` [PATCH 7/8] btrfs-progs: Introduce change_uuid() function Qu Wenruo
2015-05-05 6:16 ` [PATCH 8/8] btrfs-progs: btrfstune: Introduce new "-u" and "-U" options Qu Wenruo
2015-05-05 15:20 ` [PATCH 0/8] Introduce offline fsid/chunk tree uuid change for btrfstune David Sterba
2015-05-06 0:49 ` Qu Wenruo [this message]
2015-05-06 15:43 ` David Sterba
2015-05-08 8:57 ` Qu Wenruo
2015-05-11 16:24 ` David Sterba
2015-05-12 2:09 ` Qu Wenruo
2015-05-12 4:00 ` Anand Jain
2015-05-13 0:54 ` Qu Wenruo
2015-05-13 13:43 ` David Sterba
2015-05-15 15:42 ` Anand Jain
2015-05-21 16:30 ` David Sterba
2015-05-22 15:20 ` Anand Jain
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=5549651D.6020005@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.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 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).