Hello Okajima,
1. So, aufs spec is:
> Aufs has no its backend block device which means all aufs inode numbers
> are NOT assigned when you mount aufs. When you access a file, aufs finds
> that it exists and assigns an inode number for it.
> Your other-... in aufs didn't have its inode number and gets the number
> when you executes ls -id other-...
and 'other-...'s inode number can be one just deleted.
2. I've concerned this behavior of aufs, because:
Some part of linux assumes that each inode has a uniq inode number
regardless of the node access.
For example,
'rm' command assumes this to detect 'Circular directory structure',
and 'rm -r subdir-in-aufs/*' shows warning message like this:
"rm: WARNING: Circular directory structure.".
( Since 'rm' does circular check lazilly,
it does NOT always shows this messsage, BUT sometimes.
)
In the case of 'rm' command,
since 'rm' does not lock the entire file-system during deleting process,
other process could create a subdirectory while 'rm' is deleting.
So, the 'rm's circular detection method may be inadequate.
but,
i think it's better to declare this aufs behavior as a spec in the document(eg.
readme).
thanks for quick response.
p. yam.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
