linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Anand Jain <Anand.Jain@oracle.com>, <dsterba@suse.cz>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/8] Introduce offline fsid/chunk tree uuid change for btrfstune.
Date: Wed, 13 May 2015 08:54:33 +0800	[thread overview]
Message-ID: <5552A0C9.2010108@cn.fujitsu.com> (raw)
In-Reply-To: <55517ADC.6000300@oracle.com>



-------- Original Message  --------
Subject: Re: [PATCH 0/8] Introduce offline fsid/chunk tree uuid change 
for btrfstune.
From: Anand Jain <Anand.Jain@oracle.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>, <dsterba@suse.cz>
Date: 2015年05月12日 12:00

>
>
> On 05/12/2015 10:09 AM, Qu Wenruo wrote:
>>
>>
>> -------- 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月12日 00:24
>>
>>> On Fri, May 08, 2015 at 04:57:14PM +0800, Qu Wenruo wrote:
>>>>> Respecting the current syntax, the way to set the uuid is:
>>>>>
>>>>>    btrfs prop set -t filesytem /dev/sdx uuid ...UUID...
>>>>>
>>>>> In this special case, the property handler should check if the
>>>>> device is
>>>>> unmounted (and is a btrfs filesystem) and then do the rest.
>>>> This is one good idea, but I'm afraid it may still be confusing.
>>>> And things may get even worse when we try to move everything into
>>>> btrfs-prop,
>>>> E.g. if we auto move seeding flag to prop, we must give a quite
>>>> detailed
>>>> explain on which property is offline.
>>>>
>>>> So I prefer to add a new type called offline, and put uuid change with
>>>> other btrfstune function into this type.
>>>> IMHO this should provide a good explain on which is online and which is
>>>> offline.
>>>>
>>>> How do you think about this method?
>>>
>>> I don't think that 'offline' is a good choice. The type should denote
>>> the modified object, ie device, inode, filesystem. What's 'offline' in
>>> this context?
>> Right, 'offline' type here is just a easy trick for me to code, not a
>> meaningful type.
>>>
>>> The property interface can be used to modify other features both for
>>> mounted and unmounted filesystem, I agree that this should be done in a
>>> way that's not confusing. There are operations that are allowed on an
>>> unmounted fs (seeding), mounted + unmounted (extref feature) etc. so I
>>> think we could add options like --check-unmounted that would not allow
>>> to act on a mounted filesystem.
>>
>> Nice idea, but i prefer a option like "--offline" to enable the usage of
>> offline operations.
>> E.g, for normal online operations, nothing is changed.
>>
>> And for "btrfs prop set <DEV> uuid <UUID>", "--offline" must be
>> specified to work.
>> Or a message will be output to info user.
>>
>> What about this one?
>
>
> Qu, Thanks for the feature.
>
> Qu/David,
>
>   I strongly recommend this feature to be part of btrfstune as
>   of now, as originally planned by Qu. When its time to move
>   to btrfs cli we could. If we do it wrongly now it would stay
>   there forever.
>
>   We could take better call, when all the features of progs are
>   in place.
>
> Thanks, Anand
This is much easier for me, no need to consider the format of new 
online-offline mixed parameter for btrfs progs.

But the decision is on David.

Thanks,
Qu
>
>> 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-05-13  0:54 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
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 [this message]
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=5552A0C9.2010108@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=Anand.Jain@oracle.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).