On Fri, 03 Oct 2014 14:15:11 +0100
Filipe Manana fdman...@suse.com wrote:
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
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
much better results (ok, the file must not be in use).
Somewhere in the 3.17 cycle the resulting image got corrupted using the script
above.
Running filefrag on it returns FIBMAP unsupported.
Virtualbox returns AHCI#0P0: Read at offset 606236672 (49152 bytes left)
returned rc=VERR_DEV_IO_ERROR
got corrupted using the
script
above.
Running filefrag on it returns FIBMAP unsupported.
This message doe not mean it is a corruption, but filefrag tries to use
the FIBMAP ioctl that is not implemented on btrfs, instead FIEMAP is
used.
filefrag on a nocow file works for me here (3.16.x
extents.)
Hugo.
which produces much better results (ok, the file must not be in use).
Somewhere in the 3.17 cycle the resulting image got corrupted using the
script
above.
Running filefrag on it returns FIBMAP unsupported.
This message doe not mean it is a corruption
this error ...
which produces much better results (ok, the file must not be in use).
Somewhere in the 3.17 cycle the resulting image got corrupted using the
script above.
Running filefrag on it returns FIBMAP unsupported.
This message doe not mean it is a corruption, but filefrag tries to use
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
