On Wed, Jan 20, 2016 at 2:22 PM, Jerry Steinhauer <jerry.steinhauer@xxxxxxxxxxxxxx> wrote: > % rm a.file > rm: cannot remove 'a.file': No space left on device > % cat /dev/null > a.file > -sh: a.file: No space left on device > % btrfs fi df /data > System, single: total=32.00MiB, used=4.00KiB > Data+Metadata, single: total=506.00MiB, used=500.39MiB > GlobalReserve, single: total=12.00MiB, used=6.45MiB I see somewhere between 6MiB and 12MiB that should be available for file removal. Since delete is cow, the fs still needs free space. But I'd think rm would need very little cow metadata space to work and then free things up. I can't say for sure but sounds like a bug, or at least an unintended behavior. > We encountered this on 3.1, so we upgraded as far as our distro would > take us (yocto) to 4.1. Same issue persists. I suggest two things, neither of which fixes the problem: 1. Remount with -o enospc_debug, and reproduce the problem. 2. See if you can go to 4.1.15. There are quite a few Btrfs backports from the 4.1.8 you're using up until 4.1.15. -- 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
