I'll preface that I'm running Ubuntu 13.04 with the standard 3.8 series
kernel so please disregard if this has been fixed in higher versions. This
is on a btrfs RAID1 with 3 then 4 disks.
My use case is to set the nocow 'C' flag on a directory and copy in some
files, then make lots of writes (same file sizes) and note that the number
of extents stays the same, good.
Then run a balance (I added a disk) and start making writes again, now the
number of extents starts climbing, boo.
Is this standard behavior? I realize a balance will cow the files. Are they
also being checksummed thereby breaking the nocow flag?
I have made no snapshots and made no writes to said files while the balance
was running.
Thanks,
Kyle
--
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
