On Fri, 03 Oct 2014 14:15:11 +0100
Filipe Manana 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 cases. Try with
>
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 "
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.
numbers and see if it
> helps.
ok, need to try if I can ever recover from 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.
> >
> &
ase. I
don't know if filefrag has recently grown some extra knowledge of
compressed 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
> &g
> 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
the FIBMAP ioctl that is not implemented on btrfs, in
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".
Virtualbox returns "AHCI#0P0: Read at offset 606236
