From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-btrfs@vger.kernel.org
Subject: Odd snapshot subvolume
Date: Mon, 14 Apr 2025 10:34:49 -0400 [thread overview]
Message-ID: <dea3861ab4b85f2dffc5bbc9864b290f03c430f4.camel@interlinx.bc.ca> (raw)
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
All of the fedora_root/previous_releases/* snapshot subvolumes make
sense to me. There are all accessible at:
$ ls -l /previous-releases/
total 0
dr-xr-xr-x. 1 root root 378 May 31 2023 f38_root
drwxr-xr-x. 1 root root 194 May 31 2023 f38_var
dr-xr-xr-x. 1 root root 378 Nov 11 2023 f39_root
drwxr-xr-x. 1 root root 194 Apr 1 2024 f39_var
dr-xr-xr-x. 1 root root 362 Jun 15 2024 f40_root.old
drwxr-xr-x. 1 root root 194 May 15 2024 f40_var.old
dr-xr-xr-x. 1 root root 362 Jun 15 2024 f41_root
drwxr-xr-x. 1 root root 194 May 15 2024 f41_var
But then there is that odd-duck snapshot "previous-releases/f33_root"
not under "fedora_root" and not showing under /previous-releases in the
filesystem's namespace.
How can I access that "previous-releases/f33_root" snapshot or even
just remove it?
Cheers,
b.
next reply other threads:[~2025-04-14 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 14:34 Brian J. Murrell [this message]
2025-04-14 17:04 ` Odd snapshot subvolume 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
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=dea3861ab4b85f2dffc5bbc9864b290f03c430f4.camel@interlinx.bc.ca \
--to=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