Stanislav Brabec wrote:
However both lines mount the same part of btrfs hierarchy, files inside
will have different inode numbers for each.
Fix:
inode number will be the same, independently on subvolume actually used,
and the reported subvolid.
But the mount reference count differs depending on the bind mount source.
In the first case, I can run
umount /.snapshots
in the second, I will get EBUSY.
=> The "mount -a" problem can be reasonably fixed, but depending on the
algorithm, we could encounter unfixable problem during "umount -a".
--
Best Regards / S pozdravem,
Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o. e-mail: sbrabec@xxxxxxxx
Lihovarská 1060/12 tel: +49 911 7405384547
190 00 Praha 9 fax: +420 284 084 001
Czech Republic http://www.suse.cz/
PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
