On Wed, Aug 16, 2017 at 3:27 AM, Piotr Szymaniak <szarpaj@xxxxxxxxxxx> wrote: > On Mon, Aug 14, 2017 at 05:40:30PM -0600, Chris Murphy wrote: >> On Mon, Aug 14, 2017 at 4:57 PM, Piotr Szymaniak <szarpaj@xxxxxxxxxxx> wrote: >> >> > >> > and... some issues: >> > ~ # btrfs fi du -s /mnt/red/\@backup/ >> > Total Exclusive Set shared Filename >> > ERROR: cannot check space of '/mnt/red/@backup/': Inappropriate ioctl for device >> >> >> It's a bug, but I don't know if any devs are working on a fix yet. >> >> The problem is that the subvolume being snapshot, contains subvolumes. >> The resulting snapshot, contains an empty directory in place of the >> nested subvolume(s), and that is the cause for the error. > > Ok, but why, on the same btrfs, it works on some subvols with subvols and does > not work on other subvols with subvols? If it does not work - OK, if it works - > OK, but that seems a bit... random? > > ~ # btrfs fi du -s /mnt/red/\@backup/ /mnt/red/\@backup/.snapshot/monthly_2017-08-01_05\:30\:01/ /mnt/red/\@svn/ /mnt/red/\@svn/.snapshot/weekly_2017-08-05_04\:20\:02/ > Total Exclusive Set shared Filename > ERROR: cannot check space of '/mnt/red/@backup/': Inappropriate ioctl for device > ERROR: cannot check space of '/mnt/red/@backup/.snapshot/monthly_2017-08-01_05:30:01/': Inappropriate ioctl for device > 52.23GiB 10.57MiB 4.13GiB /mnt/red/@svn/ > 4.35GiB 1.03MiB 4.12GiB /mnt/red/@svn/.snapshot/weekly_2017-08-05_04:20:02/ I don't know. It might be that there's something inconsistent about the inode for the missing/ghost subvolume placeholder directory at snapshot creation time? -- 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
