Swâmi Petaramesh posted on Fri, 11 Apr 2014 11:21:55 +0200 as excerpted: > It is extremely unclear which BTRFS mount options are "filesystem wide" > and will apply to each and every mountpoint in the BTRFS filesystem, and > which options can be set per subvolume or per mountpoint. > > As far as I can tell, there is no reliable documentation about this, is > there any ? In general, btrfs doesn't _yet_ have the runtime infrastructure to handle per-subvolume mount options. The on-device format and general approach in the kernel was designed to allow it, and it's on the roadmap, it just hasn't been done... yet. So at this time, assume all options apply to the entire filesystem including all subvolumes unless you know and can demonstrate otherwise. If you will take a look back at my posts related to nocow files, while I suggested a separate subvolume for those files in ordered to prevent snapshotting them with the rest of the filesystem, I specifically did *NOT* suggest using the nodatacow mount-option on that subvolume even tho I knew about it, instead suggesting either still using the nocow file attribute, or putting those file on an entirely separate partition, which could then be other than btrfs if desired, precisely because AFAIK the nodatacow option cannot apply to a single subvolume yet, and for the most part, if one's going to use it on the entire filesystem, one might as well use some other filesystem instead of btrfs, since without cow and checksumming and snapshotting, there's little left to recommend btrfs above a more stable filesystem such as ext3/4 or xfs. Once the per- subvolume mount-options work as is planned, simply mounting that dedicated subvolume nodatacow will be what I'll recommend, while keeping standard cow for the main filesystem, but AFAIK that doesn't work yet, so I can't recommend it yet. -- 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