libOSTree makes use of bind mounts during startup to support multiple fs trees on any file system for the purpose of atomic updates and rollback. Example during boot: Jul 17 15:18:42 frawhide.localdomain systemd[779]: var.mount: Executing: /usr/bin/mount /sysroot/ostree/deploy/fedora-workstation/var /var -o bind cat /proc/self/mounts /dev/sda6 /var btrfs rw,relatime,ssd,space_cache,subvolid=5,subvol=/ostree/deploy/fedora-workstation/var 0 0 findmnt shows basically the same ─/var /dev/sda6[/ostree/deploy/fedora-workstation/var] │ btrfs rw,relatime,ssd,space_cache,subvolid=5,subvol=/ostree/deploy/fedora-workstation There is no such subvolume /ostree/deploy/fedora-workstation/var, basically it seems like whatever is producing this mount information (kernel code?) is just assuming a bind mount on Btrfs is a subvolume without checking if that subvolume really exists, and if it's just an ordinary directory being bind mounted, which is what's going on here. I'd say it's confusing. But I don't know if it's a problem otherwise. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
