From: Kent Overstreet <kent.overstreet@linux.dev>
To: linux-bcachefs@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
lsf-pc@lists.linux-foundation.org
Subject: [LSF TOPIC] statx extensions for subvol/snapshot filesystems & more
Date: Tue, 20 Feb 2024 19:51:05 -0500 [thread overview]
Message-ID: <2uvhm6gweyl7iyyp2xpfryvcu2g3padagaeqcbiavjyiis6prl@yjm725bizncq> (raw)
Recently we had a pretty long discussion on statx extensions, which
eventually got a bit offtopic but nevertheless hashed out all the major
issues.
To summarize:
- guaranteeing inode number uniqueness is becoming increasingly
infeasible, we need a bit to tell userspace "inode number is not
unique, use filehandle instead"
- we need a new field (st_vol, volume ID) for subvolumes - subvolumes
aren't filesystems and st_dev is problematic too
- I'd like a bit for flagging subvolume roots, as well
That's basic stuff. Beyond that, it would be useful to standardize APIs
for
- recursively enumerating subvolumes (without walking full fs
heirarchy), and translating from volume IDs to paths
- exposing snapshot tree structure - which is yet another tree
structure we need to expose, completely unrelated to normal fs path
tree structure
- snapshot recovery - i.e. atomically replacing one subvolume with
another subvolume that was a snapshot
- setting default subvolume root
- exposing disk usage of snapshots
& probably more.
Hoping to get some real participation from the btrfs crew - if they
could talk about what they've done and what else they see a need for,
that would be wonderful. Additionally, we tend to not have a lot of
userspace people at LSF, but standardizing and improving these APIs is
something userspace would _very_ much like us to do, so in addition to
the usual crew I'm hoping to bring Neal Gompa to share that perspective.
Cheers,
Kent
next reply other threads:[~2024-02-21 0:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 0:51 Kent Overstreet [this message]
2024-02-21 15:06 ` [LSF TOPIC] statx extensions for subvol/snapshot filesystems & more Miklos Szeredi
2024-02-21 21:04 ` Kent Overstreet
2024-02-21 21:08 ` Josef Bacik
2024-02-22 9:14 ` Miklos Szeredi
2024-02-22 9:42 ` Kent Overstreet
2024-02-22 10:25 ` Miklos Szeredi
2024-02-22 11:19 ` Kent Overstreet
2024-02-22 11:01 ` [Lsf-pc] " Jan Kara
2024-02-22 11:27 ` Kent Overstreet
2024-02-22 11:44 ` Jan Kara
2024-02-22 11:55 ` Kent Overstreet
2024-02-22 13:10 ` Miklos Szeredi
2024-02-22 12:48 ` Miklos Szeredi
2024-02-22 16:08 ` Jan Kara
2024-02-26 8:27 ` Miklos Szeredi
2024-02-26 16:24 ` Amir Goldstein
2024-02-22 15:48 ` Josef Bacik
2024-02-26 8:14 ` Miklos Szeredi
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=2uvhm6gweyl7iyyp2xpfryvcu2g3padagaeqcbiavjyiis6prl@yjm725bizncq \
--to=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).