On Tue, Apr 12, 2016 at 5:52 PM, Julian Taylor <jtaylor.deb...@googlemail.com> wrote: > smaller testcase that shows the immediate enospc after fallocate -> rm, > though I don't know if it is really related to the full filesystem > bugging out as the balance does work if you wait a few seconds after the > balance. > But this sequence of commands did work in 4.2. > > $ sudo btrfs fi show /dev/mapper/lvm-testing > Label: none uuid: 25889ba9-a957-415a-83b0-e34a62cb3212 > Total devices 1 FS bytes used 225.18MiB > devid 1 size 5.00GiB used 788.00MiB path /dev/mapper/lvm-testing > > $ fallocate -l 4.4G test.dat > $ rm -f test.dat > $ sudo btrfs fi balance start -dusage=0 . > ERROR: error during balancing '.': No space left on device > There may be more info in syslog - try dmesg | tail
The effect is the same with kernel / progs v4.6.0-rc3 / v4.5.1 It also doesn't matter if fallocate -l 4400M test.dat or dd if=/dev/zero of=test.dat bs=1M count=4400 is used to create test.dat (I was looking at --dig-holes and --punch-hole options earlier and was wondering if the use of fallocate would make a difference). -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
