[lkml]   [2011]   [Feb]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: btrfs: compression breaks cp and cross-FS mv, FS_IOC_FIEMAP bug?
    On Tue, Feb 15, 2011 at 11:30:38AM +0000, Pádraig Brady wrote:
    > On 14/02/11 17:58, Marti Raudsepp wrote:
    > > On Mon, Feb 14, 2011 at 17:01, Chris Mason <> 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

    Well thats not good, thats all take care of in the generic code before it gets
    to the fs, I'll take a look at that when I try and fix delalloc fiemap for
    btrfs. Thanks,

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2011-02-15 14:27    [W:0.021 / U:98.808 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site