Chris Mason wrote: > But, it'll be common to mix database files with files that you do want > checksummed in the same volume. This is an admin level decision, and we > can easily provide knobs to turn it on/off. So, I think the ioctl is > really important and we'll just document it as best we can. I do see now why this ability is desirable, especially if there is a way to see a file's checksum/COW settings (or better still, to query the filesystem for which files have certain settings). My initial concern was that an admin or user may not realize (or forget) a file was left in an "unprotected" state, but yes, I'm sure there are ways to mitigate that possibility. -Joe -- 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
