Chris Murphy
Chris Murphy
Doesn't happen with an 8T image. It might be a problem related to the size of the target file system or block device.
Posted inquiry to [email protected] https://lists.fedoraproject.org/archives/list/[email protected]/thread/YTGX66CCJLDVMFFOGBV2CUS637NCAQR6/
Perhaps another possibility is backporting new security labels to older release versions of a distribution, so that the receive command can fully succeed.
Contrived reproduce steps pretty much shows `btrfs insp min` isn't working correctly. The resize below its min size succeeds. ``` truncate -s 100g test.raw losetup /dev/loop0 test.raw mkfs.btrfs -msingle -dsingle...
Related https://github.com/storaged-project/libblockdev/issues/548
BTW this inode is a systemd-journald file.
This is arguably a difficult bug to solve, for either the Size value for 'df' or the Free value for 'btrfs fi us' - the volume is 15G but that's...
Andrei argues this may be correct behavior, because this Free space is available for conversion. It's just that there are two kinds of "free" space, in this odd situation. It's...
I'm seeing this with btrfs-progs v5.11.1 and kernel 5.12-rc6 ``` # btrfs fi show Label: 'OWC300G' uuid: ab845dd9-63b5-4459-b98b-06ed92398247 Total devices 1 FS bytes used 160.00KiB devid 1 size 298.09GiB used...
As I fallocate files to fill up the space, it gets even nuttier. And disagrees with GNOME Nautilus and Disks (based on udisks2). ``` # fallocate -l 240g test #...