> > 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
Additionally, if you have have several hardlinked files, their inode numbers are all same. I don't think it is a problem. You might just meet a known problem in aufs1 since your aufs1 version is so old and not maintained now. I'd suggest you to try the last version of aufs1. 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
