On Sat, Apr 4, 2015 at 4:33 AM, Filipe David Manana <fdman...@gmail.com> wrote: > On Sat, Apr 4, 2015 at 12:36 AM, Justin Maggard <jmaggar...@gmail.com> wrote: >> Hi, >> >> We're hitting a consistently reproducible ENOSPC condition with a >> simple test case: >> >> # truncate -s 1T btrfs.fs >> # mkfs.btrfs btrfs.fs >> # mount btrfs.fs /mnt/ >> # fallocate -l 1021G /mnt/fallocate >> # btrfs fi sync /mnt/ >> # dd if=/dev/zero of=/mnt/dd bs=1G >> # btrfs fi sync /mnt/ >> # rm /mnt/fallocate >> # btrfs fi sync /mnt/ >> # fallocate -l 20G /mnt/fallocate >> fallocate: /mnt/fallocate: fallocate failed: No space left on device >> >> I continue to get ENOSPC even after unmount / mount. >> >> Here we have 1022GB free as reported by df, yet we can't allocate >> 20GB. I tried the integration-4.1 tree, which had the same results. >> I also added Zhao Lei's ENOSPC most recent patchset from today, but it >> didn't seem to help. > > Have you tried too the following patch (not in any release nor rc)? > > https://patchwork.kernel.org/patch/5800231/ >
No, I hadn't; thanks for the pointer! That patch does indeed make my test case work. -Justin -- 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
