On Sat, Aug 07, 2021 at 02:05:15PM +0300, Amir Goldstein wrote: > On Sat, Aug 7, 2021 at 1:17 PM Zhihao Cheng <chengzhihao1@xxxxxxxxxx> wrote: > > > > Hi, all. > > > > As title said. I wonder to know the reason for overlayfs mount failure > > with '-o nfs_export=on,metacopy=on'. > > > > I modified kernel to enable these two options 'on', it looks like that > > overlayfs can still work fine under nfs_v4. > > > > Besides, I can get no more information about the reason from source > > code, maybe I missed something. > > > > It's because ovl_obtain_alias() (decoding a disconnected non-dir file handle) > does not know how to construct a metacopy overlayfs inode. > > Maybe Vivek will be able to point you to the discussion that lead to making > the features mutually exclusive. I think I had not implemented metacopy with nfs export because it seemed non-trivial and I did not need nfs export feature support with metacopy. So I decided to narrow down the problem space and not support nfs export and metacopy together. It will be good if somebody can dive deeper and make it work (if it is possible to make it work). Vivek > > I don't remember any other reason. > > Thanks, > Amir. >
