Hi, Okajima San,
I saw some info about aufs from web, like
: [1]http://gdr.geekhood.net/gdrwpl/aufs-nfs.php, It says:
Also, when exporting via NFS, the AUFS mount should
have xino=/tmp/somefile option attached, with the file different for
different share.
And
in [2]http://aufs.sourceforge.net/aufs5/man.html#Exporting%20Aufs%20via
%20NFS,
Exporting Aufs via NFS
The External Inode Number Bitmap, Translation Table and Generation
Table (xino) is required since NFS file handle is based upon inode
number. The mount option 'xino' is enabled by default.
I thought the xino option is necessary for aufs mount when has
branch of nfs filesystem.
When I reboot the system, the xino option works. Now I add the xino
option to mount again. Now I didn't find that warnning in kernel log.
__________________________________________________________________
Michael Mao
From: [3]J. R. Okajima
Date: 2020-03-22 11:25
To: [4]hom...@163.com
CC: [5]aufs-users
Subject: Re: LXC unpreviliged problem with aufs mounted on nfs
"hom...@163.com":
> About the xino, I gave the xino option first time , but after
some kind of operations, I found aufs can't mount success if I still
give the same xino path, even if I umount the path. So I remove the
xino option to mount the path now.
> I will reboot the system and try again mount with the xino.
Hmm, you might not understand why it failed. The log
> Mar 22 10:22:44 zss-node1 kernel: [62451.849348] aufs
au_xino_create:819:mount[30959]: open /tmp/aaa(-17)
means "17:EEXIST:File exists".
The filepath given to xino must be a new one since aufs will create it.
But why do you want to add xino=? Any particular reason?
J. R. Okajima
References
1. http://gdr.geekhood.net/gdrwpl/aufs-nfs.php
2. http://aufs.sourceforge.net/aufs5/man.html#Exporting%20Aufs%20via%20NFS
3. mailto:hooanon...@gmail.com
4. mailto:hom...@163.com
5. mailto:aufs-users@lists.sourceforge.net
