On 10/02/2014 11:11 PM, Marc Dietrich wrote: > Am Donnerstag 02 Oktober 2014, 21:55:55 schrieb Marc Dietrich: >> Will try to restore the file using btrfs restore.... > > ok, restore worked. I did some more tests. This is unrelated to CoW. It seems > that the "fallocate -n" in combination with "dd conv=notrunc" using large > files (>10G) triggers it. Maybe this rings some bells.
Just tried it and I confirm filefrag's call to ioctl FS_IOC_FIEMAP fails with -EEXIST. It's actually a known issue affecting any of the 3.17 RCs (except RC1). The extent map manipulation/merging is broken for some cases. Try with this 2 patches on top of 3.17-rcX: https://patchwork.kernel.org/patch/4929981/ https://patchwork.kernel.org/patch/4945191/ Or, alternatively, reverting this patch: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=51f395ad4058883e4273b02fdebe98072dbdc0d2 Someone else reported on this list a write/pwrite/writev failure with errno EEXIST too (and apparently caused by the same reason). This broken extent map handling is serious IMHO, it can make fsync log bogus extent items for example, amongst other possible bad and weird things. > > Marc > > -- > 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 > -- 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
