On Fri, Jul 14, 2017 at 4:37 AM, Oliver O. <oliver.o456i@xxxxxxxxx> wrote:
> Hello,
>
> I think I've found a corner case where the current cross-subvolume inode
> scheme
> does not work as intended:
Yep. So I hit this on all read-only snapshots of my rootfs because
systemd creates a nested /var/lib/machines subvolume, and when I
snapshot root, it contains this odd directory made from
/var/lib/machines subvolume. And it causes 'btrfs subvolume du'
command to not work.
newfstatat(5, "machines", {st_mode=S_IFDIR|0755, st_size=0, ...}, 0) = 0
stat("root00.20170704/var/lib/machines", {st_mode=S_IFDIR|0755,
st_size=0, ...}) = 0
open("root00.20170704/var/lib/machines",
O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 6
fstat(6, {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
ioctl(6, BTRFS_IOC_INO_LOOKUP, {treeid=0, objectid=256 /*
BTRFS_FIRST_FREE_OBJECTID */}) = -1 ENOTTY (Inappropriate ioctl for
device)
close(6)
--
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
