public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Goffredo Baroncelli <kreijack@libero.it>
To: Nicholas D Steeves <sten@debian.org>
Cc: "Brian J. Murrell" <brian@interlinx.bc.ca>, linux-btrfs@vger.kernel.org
Subject: Re: P.S. Re: Odd snapshot subvolume
Date: Mon, 14 Apr 2025 19:54:48 +0200	[thread overview]
Message-ID: <72d7150b-4e0b-4e15-bd3f-ab410be4a767@libero.it> (raw)
In-Reply-To: <87cydeirkl.fsf@navis.mail-host-address-is-not-set>

On 14/04/2025 19.24, Nicholas D Steeves wrote:
> P.S.
> 
> Nicholas D Steeves <sten@debian.org> writes:
> 
>>> just remove it?
>>
>>    # mkdir -p /btrfs-admin
>>    # mount -o subvolid=5 /dev/disk/by-uuid/c08a988c-ddd5-164e-b01e-51ac26bf018b /btrfs-admin
> 
> Oops!  This /\ is wrong, because btrfs subvolume show / returns the
> filesystem UUID, and the command above uses the disk UUID.

I have to correct you: "btrfs sub show" shows the *SUBVOLUME* uuid, where
/dev/disk/by-uuid/XXXX refers to the *FILESYSTEM* uuid.
Apart that, it is correct that you can't take the UUID from "btrfs sub show"
to mount a filesystem. You need the UUID from "btrfs fi show"

BR

-- 
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D  17B2 0EDA 9B37 8B82 E0B5

  reply	other threads:[~2025-04-14 17:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14 14:34 Odd snapshot subvolume Brian J. Murrell
2025-04-14 17:04 ` Andrei Borzenkov
2025-04-14 19:11   ` Brian J. Murrell
2025-04-14 17:14 ` Nicholas D Steeves
2025-04-14 17:24   ` P.S. " Nicholas D Steeves
2025-04-14 17:54     ` Goffredo Baroncelli [this message]
2025-04-14 18:32       ` Nicholas D Steeves
2025-04-14 19:06         ` Goffredo Baroncelli
2025-04-17 21:22           ` Nicholas D Steeves
2025-04-18 16:38             ` Goffredo Baroncelli

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=72d7150b-4e0b-4e15-bd3f-ab410be4a767@libero.it \
    --to=kreijack@libero.it \
    --cc=brian@interlinx.bc.ca \
    --cc=kreijack@inwind.it \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sten@debian.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