Qu Wenruo posted on Tue, 12 Jan 2016 11:09:23 +0800 as excerpted: > Now we hope to add support to enable/disable dedup per-file. > Much like current NODATACOW/NOCOMPRESS for inode. How is this going to work? NODATACOW/NOCOMPRESS can apply to a single file. But a dup flag, by definition, needs two files, except for the special case of parts of a file duplicating other parts of the same file. Is there going to be some background thread that checks for dups and reflinks duplicated extents if both files have the dup flag set? What if one has it on and one has it off? Presumably, if a file has it on and it is copied (so a new file), the copy would be reflinked. But if the flag is off, does that make the file actually data-copy, by default, even if cp decides to do a reflink copy by default? And does the copy automatically have the dup flag set as well, or does the original instance set dup, while the new copy, reflinked to the old one due to that dup flag, still have the dup flag unset, until the user sets it? OTOH, I can see such an attribute for dirs making more sense, since it could be inherited much like the NOCOW attribute, and new files created there could automatically be checked against the current files to see if parts are dup, and reflink them if so. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
