From: Nicholas D Steeves <sten@debian.org>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>, linux-btrfs@vger.kernel.org
Subject: Re: Odd snapshot subvolume
Date: Mon, 14 Apr 2025 13:14:57 -0400 [thread overview]
Message-ID: <87friais1a.fsf@navis.mail-host-address-is-not-set> (raw)
In-Reply-To: <dea3861ab4b85f2dffc5bbc9864b290f03c430f4.camel@interlinx.bc.ca>
[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]
Hi Brian,
"Brian J. Murrell" <brian@interlinx.bc.ca> writes:
> On my Fedora system I have the following:
>
> $ sudo btrfs subvolume show /
> fedora_root
> Name: fedora_root
> UUID: c08a988c-ddd5-164e-b01e-51ac26bf018b
> Parent UUID: -
> Received UUID: -
> Creation time: 2021-08-10 18:30:03 -0400
> Subvolume ID: 258
> Generation: 5029586
> Gen at creation: 10
> Parent ID: 5
> Top level ID: 5
> Flags: -
> Send transid: 0
> Send time: 2021-08-10 18:30:03 -0400
> Receive transid: 0
> Receive time: -
> Snapshot(s):
> fedora_root/previous-releases/f38_root
> fedora_root/previous-releases/f39_root
> fedora_root/previous-releases/f40_root.old
> fedora_root/previous-releases/f41_root
> previous-releases/f33_root
> Quota group: n/a
[snip]
> How can I access that "previous-releases/f33_root" snapshot or even
> just remove it?
# mkdir -p /btrfs-admin
# mount -o subvolid=5 /dev/disk/by-uuid/c08a988c-ddd5-164e-b01e-51ac26bf018b /btrfs-admin
# cd /btrfs-admin
# mv previous-releases/f33_root fedora_root/previous_releases/f33_root
OR
# btrfs subvolume delete /btrfs-admin/previous-releases/f33_root
To anyone else reading this:
Are there any reasons why distributions shouldn't set this up by
default? What are the arguments against exposing the full structure in
/dev or in /sys (with permissions like 700)?
Regards,
Nicholas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]
next prev parent reply other threads:[~2025-04-14 17:15 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 [this message]
2025-04-14 17:24 ` P.S. " Nicholas D Steeves
2025-04-14 17:54 ` Goffredo Baroncelli
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=87friais1a.fsf@navis.mail-host-address-is-not-set \
--to=sten@debian.org \
--cc=brian@interlinx.bc.ca \
--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