I don't know whether this demand, which specified some subvolumes or directories to be compressed, conflict with the design of btrfs's compression feature, may be they want to do this thing well, and everyone will enable the compression feature, rather than throw the decision to user to determine which should compress. But now, if we can mount a subvolume and specify some mount options, we should make these options work, rather than ignore. 2010/7/30 Chris Ball <cjb@xxxxxxxxxx>: > Hi, > > > So, is there such a method: in a specified directory, the > > compression feature is enabled, and the file in this directory > > will be compressed automatically, while the others don't enable > > compression. > > I don't think so, but it wouldn't be difficult -- you'd just set a > per-inode flag on whether to compress, and if it's set on a directory > then it's inherited by the files in that directory. > > I think the hold up has been that we've waited for a *generic* > cross-filesystem flag to appear, and it hasn't (or it has and I didn't > notice). Does anyone have suggestions on how to break the deadlock > there? > > - Chris. > -- > Chris Ball <cjb@xxxxxxxxxx> > One Laptop Per Child > -- Wang Shaoyan -- 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
