On 2018/10/30 5:32, Amir Goldstein Wrote: > [adding back CC list, which I accidentally dropped a few emails back..] > [..] > > Adding another terrible idea to add to the pile of non perfect solutions. > I never liked the 'feature=[on|off]' standard, which is different from the more > common standard of '[feature|nofeature]' mount options. > > What if we interpreted mount options 'feature=[on|off]' as advisory and > mount options '[feature|nofeature]' as mandatory? > > The mandatory semantics could mark the start of the mkfs.overlay era > (a.k.a overlayfs on-disk format v2). > Meaning that you can only mount with mandatory 'metacopy' if either: > - upperdir AND workdir are empty > OR > - layers where created with mkfs.overlay with mandatory 'metacopy' > OR > - overlay was always mounted in the past with mandatory 'metacopy' > OR > - fsck.overlay is used to check layers and add mandatory 'metacopy' > > Zhangyi, > > Do you have plans to post another version of overlayfs feature set > patches for kernel/overlayfs-progs anytime soon? > Hi Amir, Yes, I've done about 70% of the work for kernel, but I haven't started yet for overlayfs-progs. I've been quite busy lately, and have to postpone this work. Anyway, I will try to post the next version as soon as posible. Thanks, Yi.
