[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#8001: btrfs: compression breaks cp and cross-FS mv, FS_IOC_FIEMAP bu
bug#8001: btrfs: compression breaks cp and cross-FS mv, FS_IOC_FIEMAP bug?
Tue, 15 Feb 2011 11:30:38 +0000
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:126.96.36.199) Gecko/20100227 Thunderbird/3.0.3
On 14/02/11 17:58, Marti Raudsepp wrote:
> On Mon, Feb 14, 2011 at 17:01, Chris Mason <address@hidden> wrote:
>> Or, it could just be delalloc ;)
> I suspect delalloc. After creating the file, filefrag reports "1
> extent found", but for some reason it doesn't actually print out
> details of the extent.
That's a bug in `filefrag -v` that I noticed independently yesterday.
Without -v it will correctly report 0 extents.
I've already suggested a patch to fix upstream.
> After a "sync" call, the extent appears and "cp" starts working as expected:
About that sync.
I've noticed on ext4 loop back at least (and I suspect BTRFS is the same)
that specifying FIEMAP_FLAG_SYNC (which cp does) is ineffective.
I worked around this for cp tests by explicitly syncing with:
dd if=/dev/null of=foo conv=notrunc,fdatasync
> % rm -f foo bar
> % echo foo > foo
> % sync
> % filefrag -v foo
> Filesystem type is: 9123683e
> File size of foo is 4 (1 block, blocksize 4096)
> ext logical physical expected length flags
> 0 0 0 4096 not_aligned,inline,eof
> foo: 1 extent found
> % cp foo bar
> % hexdump bar
> 0000000 6f66 0a6f
OK that's fine for normal files.
cp (from coreutils >= 8.10) may still do the wrong thing
as it currently ignores FIEMAP_EXTENT_DATA_ENCRYPTED and FIEMAP_EXTENT_ENCODED
as I've already reported:
I'd appreciate some `filefrag -v` output from a large compressed file.
- bug#8001: btrfs: compression breaks cp and cross-FS mv, FS_IOC_FIEMAP bug?,
Pádraig Brady <=