https://bugs.kde.org/show_bug.cgi?id=425040
Chris Murphy <bugzi...@colorremedies.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugzi...@colorremedies.com
--- Comment #7 from Chris Murphy <bugzi...@colorremedies.com> ---
Perhaps limit partition manager to subvolumes in a flat layout in the top-level
of the file system, i.e. only list, create, delete, and assign top-level
subvolumes. They could be assigned to arbitrary mountpoints.
And maybe limit the file manager to subvolumes in the nested layout, where it's
a special kind of directory?
https://btrfs.wiki.kernel.org/index.php/SysadminGuide#Layout
Btrfs supports 2^64 subvolumes. It could be that there will be many
client/owners of subvolumes that expect exclusive access, e.g. snapper,
podman/mobi, timeshift, btrbk, etc.
Partition manager may not want to be in a position of having to manage
everything, or in some sense make it easy for users to inadvertently mess up
some other application's realm. Instead it might care more about the multiple
device handling of Btrfs, add/remove/replace devices.
Maybe in the short term we should just ideate, and look at what libbtrfsutil,
libblockdev, and udisks2 need. There is:
http://storaged.org/doc/udisks2-api/latest/gdbus-org.freedesktop.UDisks2.Filesystem.BTRFS.html
Does it make sense to include some kind of list limiting or filtering within
this library? Or expect every client to handle possibly thousands of items in a
GetSubvolumes method?
--
You are receiving this mail because:
You are watching all bug changes.
