Hi, Okajima San,
OK, I try to gather them to you.
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.
BTW, I don't know if you will login to my server and debug by
yourself. I think that may be more effective.
And I don't know what online IM tool you are using, such as wechat
in China. Maybe we can add each other to communicate online.
BR.
__________________________________________________________________
Michael Mao
From: [1]J. R. Okajima
Date: 2020-03-22 10:54
To: [2][email protected]
CC: [3]aufs-users
Subject: Re: LXC unpreviliged problem with aufs mounted on nfs
"[email protected]":
> Sorry, please refer to below:
The log is not so informative unfortunately, but I can see this line.
> Mar 22 10:22:44 zss-node1 kernel: [62451.849348] aufs
au_xino_create:819:mount[30959]: open /tmp/aaa(-17)
Did you give xino= option? Are you running aufs with noxino?
Next time when you post, please attach these info.
(from aufs README file)
When you have any problems or strange behaviour in aufs, please let me
know with:
- /proc/mounts (instead of the output of mount(8))
- /sys/module/aufs/*
- /sys/fs/aufs/* (if you have them)
- /debug/aufs/* (if you have them)
- linux kernel version
if your kernel is not plain, for example modified by distributor,
the url where i can download its source is necessary too.
- aufs version which was printed at loading the module or booting the
system, instead of the date you downloaded.
- configuration (define/undefine CONFIG_AUFS_xxx)
- kernel configuration or /proc/config.gz (if you have it)
- LSM (linux security module, if you are using)
- behaviour which you think to be incorrect
J. R. Okajima
References
1. mailto:[email protected]
2. mailto:[email protected]
3. mailto:[email protected]
