"Igor Karasynskyi":
> > - after rm, check the whiteout by 'ls -l /rw/tmp/.wh.test'
> yes whiteout created
And what is its user/group/link_count?
> > - check the dir permission by 'ls -ld / /rw /ro /rw/tmp /ro/tmp'
> yes all ok, all branches has 755 and all tmp has 777
Let me make sure about /tmp.
Is its permission 0777 or 1777?
> > - find the systemcall which returned the error by 'strace touch
> > /tmp/test'
> open("/tmp/test", O_WRONLY|O_NONBLOCK|O_CREAT|O_NOCTTY|O_LARGEFILE,
> 0666) = -1 EPERM (Operation not permitted)
So your real error is EPERM, instead of ENOENT.
> I try to repeat this situation in next way:
> 1) Add new branch /my (rw)
> 2) Remount previous cur as RO
> 3) create /tmp/new and chown user:group them
> 4) Add new branch /my1 (rw)
> 5) Remount previous /my as RO
It might be an aufs bug around remount.
After this (or final) remount, please send me your /proc/mounts and
/sys/fs/aufs/*.
> 6) Delete file /tmp/new, whiteout created all ok, ls /tmp/new - No
> such file or directory
Do you mean the whiteout is created as /my1/tmp/.wh.new?
Your rw branch is /my1 and you don't have any other writable
branches. And /my1 appears fist in the br: list in /proc/mounts or
/sys/fs/aufs/*.
Am I right?
Junjiro Okajima
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
