Excerpts from Josef Bacik's message of 2011-02-13 11:13:30 -0500: > On Sun, Feb 13, 2011 at 06:07:36PM +0200, Marti Raudsepp wrote: > > On Sun, Feb 13, 2011 at 17:57, Josef Bacik <josef@xxxxxxxxxx> wrote: > > > Does the same problem happen when you use cp --sparse=never? > > > > You are right. cp --sparse=never does not cause data loss. > > > > So fiemap probably isn't doing the right thing when compression is enabled, > which doesn't suprise me since we don't do the right thing with delalloc either. > I will try and get to this soon. Thanks, This might be a bug in the cp code. We're setting the disk extent to zero but setting different flags to say we're inline and compressed. The cp fiemap code might be ignoring the flags? Or, it could just be delalloc ;) -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
