I have a 3 disk raid1 filesystem mounted with nodatacow. I have a folder in said filesystem with the 'C' NOCOW & 'Z' Not_Compressed flags set for good measure. I then copy in a large file and proceed to make random modifications. Filefrag shows no additional extents created, good so far. A big thank you to the those devs who got that working. However, after a balance run (which crashed btw), modifications to the file result in increasing extent counts, ie. no longer obeying nodatacow mount option nor the 'C' flag. I realize that a balance will cow the data but it should not disable the ability to make nodatacow inline changes to a file. I'm currently running 3.5.0 mainline Ubuntu kernel with the latest master of btrfs-progs from a ppa. Thank you. Kyle Gates -- 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
