chrismurphy reported a new issue against the project: `atomic-wg` that you are following:
This is an info bug, not an atomic bug, and it's non-fatal. Open question if upstream
should be pushed to fix it or if this is cosmetic.
Background: Btrfs subvolumes can be directly mounted with `mount -o
subvol=nameofsubvolume`. Behind the scenes this is a bind mount. When using the mount
command or looking at `/proc/self/mountinfo` both subvolid and subvol info is shown.
`/dev/sda1 on /srv/scratch type btrfs
subvolid=910 is subvol=scratch, those are synonymous and immutable, at least on disk.
Problem: Ostree installations make prolific use of bind mounts for assembly, and I've
discovered that mount thinks these bind mounts are subvolumes.
/dev/sda7 on /sysroot type btrfs
/dev/sda7 on / type btrfs
/dev/sda7 on /usr type btrfs
/dev/sda7 on /var type btrfs
The first line is correct. subvolid=5 is subvol=root. All the other lines have correct
subvolid's but the subvol listed is a bind mount, there is no such subvolume as those
Clearly the kernel code is correctly looking up subvolume ID, but it's assuming bind
mounts are subvolumes rather than directly looking them up. Upstream report is here:
To reply, visit the link below or just reply to this email