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 <chris.ma...@oracle.com> 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, Josef -- 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
