From: Anand Jain <anand.jain@oracle.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: drop unique uuid test for btrfstune -M
Date: Fri, 6 Sep 2019 17:27:00 +0800 [thread overview]
Message-ID: <232bccd3-3623-8ee9-18db-98edf7cd2e25@oracle.com> (raw)
In-Reply-To: <f3d33e1d-803e-34a5-4dfa-7eeceec6177c@suse.com>
<snip>
> This is intended. Otherwise it's an open avenue for the user to shoot
> themselves in the foot.
I don't understand how?
> If you know what you are doing and are
> absolutely sure the original fs is no longer present
> - then just flush
> libblkid cache and you'll be able to set the FSID back to the original one.
>
<snip>
No no its not about the stale cache holding the original fsid. The use
case is - a golden copy of the bootable OS image is being used and
shares the same fsid on multiple hosts.
Now if you want to mount another copy it for some changes, you need to
btrfstune -m on the copy. And later if you want to boot it
successfully, it needs its original fsid back.
HTH, Anand
next prev parent reply other threads:[~2019-09-06 9:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 0:50 [PATCH] btrfs-progs: drop unique uuid test for btrfstune -M Anand Jain
2019-09-06 7:21 ` Nikolay Borisov
2019-09-06 9:27 ` Anand Jain [this message]
2019-09-09 11:40 ` Nikolay Borisov
2019-09-10 5:12 ` Anand Jain
2019-09-11 17:01 ` David Sterba
2019-09-12 0:45 ` Anand Jain
2019-09-24 11:20 ` Anand Jain
2019-10-01 8:08 ` Anand Jain
2019-10-17 16:32 ` David Sterba
2019-10-18 8:52 ` Anand Jain
2020-05-20 10:44 ` 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=232bccd3-3623-8ee9-18db-98edf7cd2e25@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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