On Tue, Jun 12, 2012 at 04:44:23PM -0400, Chris Mason wrote: > On Tue, Jun 12, 2012 at 01:15:27PM -0600, Ted Ts'o wrote: > > It appears the NOCOW_FL flag is currently a no-op in the 3.2 kernel? > > It's not a noop, but it is only setting the NODATACOW flag. It needs to > set the nodatasum flag as well, just like the mount -o nodatacow mount > option does. > > I'll fix this up on the kernel side, thanks Ted. Last time the nocow question popped up, I sent this workaround, http://article.gmane.org/gmane.comp.file-systems.btrfs/17351 (whole thread http://article.gmane.org/gmane.comp.file-systems.btrfs/17351) which now seems to be the way to go (as removing the checksums from existing file is not that easy). Good to see the NOCOW support going to lsattr/chattr. david -- 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
