Hide Forgot
Description of problem: ----------------------- The BTRFS "subvolume" usage is not as easy and intuitive as with ZFS or LVM. With zfs or lvm, an admin sys is used to create a "volume" and to "mount" it. With ZFS, the subvolume creation, the filesystem creation and the "mount" operation are done at the same time. An admin sys can check it with the command "mount" or "df". With BTRFS, at the subvolume creation, the "mount" operation is not obvious and can't be checked whereas the subvolume does exist and the directory is browsable, readable, writable.... Version-Release number of selected component (if applicable): ------------------------------------------------------------- mount from util-linux 2.19.1 (with libblkid and selinux support) Btrfs Btrfs v0.19 (0.19-16.fc15) How reproducible: ------------------ Btrfs normal usage Steps to Reproduce: 1. Create a subvolume 2. type "mount" 3. Use the subvolume Actual results: ---------------- [ root@Jumper ] /home/xakraz └─> # btrfs subvolume create @test Create subvolume './@test' ┌[ root@Jumper ] /home/xakraz └─> # ls Documents Images Public @test ┌[ root@Jumper ] /home/xakraz └─> # mount | grep btrfs /dev/sda3 on / type btrfs (rw,noatime,seclabel,ssd,space_cache,clear_cache) /dev/sda3 on /home type btrfs (rw,relatime,seclabel,ssd,space_cache,clear_cache) /dev/sda3 on /tmp type btrfs (rw,noatime,seclabel,ssd,space_cache,clear_cache) /dev/sda3 on /var/tmp type btrfs (rw,noatime,seclabel,ssd,space_cache,clear_cache) /dev/sda3 on /home type btrfs (rw,relatime,seclabel,ssd,space_cache,clear_cache) [ root@Jumper ] /home/xakraz └─> # btrfs subvolume list / ID 256 top level 5 path @ ID 257 top level 5 path @home ID 265 top level 5 path @apt-snapshot-2011-08-07_21:11:31 ID 266 top level 5 path @apt-snapshot-2011-08-07_21:19:30 ID 267 top level 5 path @apt-snapshot-2011-08-07_21:26:36 ID 292 top level 5 path @home/xakraz/@test Expected results: ------------------- * Device handling : ’root@ubuntu1010fs:~# zpool create mypool raidz sdb sdc sdd sde’ ’root@ubuntu1010fs:~# zpool list’ NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT mypool 3,94G 150K 3,94G 0% 1.00x ONLINE - ’root@ubuntu1010fs:/# mount | grep zfs’ mypool on /mypool type zfs (rw) * Filesystem = subvolume handling ’root@ubuntu1010fs:/mypool# zfs create mypool/subVol1’ ’root@ubuntu1010fs:~# df -hT | grep zfs’ mypool zfs 2,7G 101M 2,6G 4% /mypool mypool/subVol1 zfs 2,7G 91M 2,6G 4% /mypool/subVol1 Additional info: ----------------- A tool for rollbacking snapshots would be very handful too.
This bugzilla has nothing to do with filesystem package/component. This package creates and owns the set of basic system directories. Reassigning to btrfs-progs, but maybe belongs to kernel.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping