Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Cc: clm@fb.com, josef@toxicpanda.com, dsterba@suse.com,
	linux-fsdevel@vger.kernel.org, kernel@gpiccoli.net,
	kernel-dev@igalia.com, anand.jain@oracle.com,
	david@fromorbit.com, kreijack@libero.it, johns@valvesoftware.com,
	ludovico.denittis@collabora.com, wqu@suse.com,
	vivek@collabora.com
Subject: Re: [PATCH 2/3] btrfs: Introduce the single-dev feature
Date: Fri, 4 Aug 2023 08:38:23 -0300	[thread overview]
Message-ID: <b7f6a100-a802-67a9-589b-1457dee6d32a@igalia.com> (raw)
In-Reply-To: <58a425ca-f7e8-b7e2-eb04-d83bb952b382@gmx.com>

On 04/08/2023 05:27, Qu Wenruo wrote:
> [...] 
> My concern is still about the "virtual" fsid part.
> 
> If we go virtual fsid, there can be some unexpected problems.
> 
> E.g. the /sys/fs/btrfs/<uuid>/ entry would be the new virtual one.
> 
> And there may be some other problems like user space UUID detection of
> mounted fs, thus I'm not 100% sure if this is a good idea.
> 
> However I don't have any better solution either, so this may be the
> least worst solution for now.
> 
> Thanks,
> Qu

Hi Qu, thanks for your analysis!

I think the virtual/spoofed fsid part is not without problems but I
consider it to be less prone to unexpected issues than not.

It's based on the metadata_uuid code, which is stable and present in
btrfs for like 5 years. Also, we don't need to "corner-case" a lot of
stuff to use that, which would be needed if we went to the pure dup fsid
route. I tried that and it breaks in a lot of places, to which we
require a lot of if conditionals (I even discussed that briefly in the
last thread with you, about sysfs, remember?).

So, despite not perfect, I agree with you that seems to be the least
worse solution :)

Cheers,


Guilherme

  reply	other threads:[~2023-08-04 11:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 15:43 [PATCH V2 0/3] Supporting same fsid mounting through a compat_ro feature Guilherme G. Piccoli
2023-08-03 15:43 ` [PATCH 1/3] btrfs-progs: Add the single-dev feature (to both mkfs/tune) Guilherme G. Piccoli
2023-08-17 15:46   ` Josef Bacik
2023-08-17 16:16     ` Guilherme G. Piccoli
2023-08-03 15:43 ` [PATCH 2/3] btrfs: Introduce the single-dev feature Guilherme G. Piccoli
2023-08-04  8:27   ` Qu Wenruo
2023-08-04 11:38     ` Guilherme G. Piccoli [this message]
2023-08-17 15:41   ` Josef Bacik
2023-08-17 16:20     ` Guilherme G. Piccoli
2023-08-17 16:58       ` Josef Bacik
2023-08-17 17:09         ` Guilherme G. Piccoli
2023-08-23 16:31   ` Anand Jain
2023-08-24 20:55     ` Guilherme G. Piccoli
2023-08-29 20:28   ` Guilherme G. Piccoli
2023-08-30  7:11     ` Anand Jain
2023-08-30 12:00       ` Guilherme G. Piccoli
2023-08-03 15:43 ` [PATCH 3/3] btrfs: Add parameter to force devices behave as single-dev ones Guilherme G. Piccoli
2023-08-17 15:44   ` Josef Bacik
2023-08-20 18:16     ` Guilherme G. Piccoli
2023-08-17 13:56 ` [PATCH V2 0/3] Supporting same fsid mounting through a compat_ro feature Guilherme G. Piccoli
2023-08-17 14:19 ` Josef Bacik
2023-08-17 14:23   ` Guilherme G. Piccoli

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=b7f6a100-a802-67a9-589b-1457dee6d32a@igalia.com \
    --to=gpiccoli@igalia.com \
    --cc=anand.jain@oracle.com \
    --cc=clm@fb.com \
    --cc=david@fromorbit.com \
    --cc=dsterba@suse.com \
    --cc=johns@valvesoftware.com \
    --cc=josef@toxicpanda.com \
    --cc=kernel-dev@igalia.com \
    --cc=kernel@gpiccoli.net \
    --cc=kreijack@libero.it \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=ludovico.denittis@collabora.com \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=vivek@collabora.com \
    --cc=wqu@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