"p. yam": > 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.
Right. > 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. Do you mean ... - you have dir/file and dir/subdir $ ls dir file subdir - create a file under dir during rm -r $ rm -r dir & touch dir/new_file - then, rm -r may warn "Circular directory structure"? If so, the problem can happen on any filesystem. For instance, on ext2, $ > a $ ls -i a 33 a $ rm a $ > b $ ls -i b 33 b It shows that the new inode number can be the number of 'a' anytime after 'a' is deleted. What is the version of your rm (I am not a Puppy user)? And provide me these info. (from the aufs README) 5. Contact ---------------------------------------- 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) - behaviour which you think to be incorrect - actual operation, reproducible one is better - mailto: aufs-users at lists.sourceforge.net Usually, I don't watch the Public Areas(Bugs, Support Requests, Patches, and Feature Requests) on SourceForge. Please join and write to aufs-users ML. ---------------------------------------------------------------------- J. R. Okajima ------------------------------------------------------------------------------ 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
