Hello.
I have a question about the algorithm of recycling aufs inode number.
1. The outline of the problem:
The following command sequence, (a)..(d) , shows something strange.
(a) cd /some-aufs-directory
(b) ls -id some-directory-which-inode-is-99
==> this shows inode number 99.
(c) rmdir some-directory-which-inode-is-99
(d) ls -id other-directory-which-inode-is-unknown
==> sometimes this shows inode number 99.
But the inode number 99 should NOT exist, since it was 'rmdir'ed at (c).
2. Actual operations to reproduce the problem:
(1) Environment:
(a) Puppy linux 4.20p1(japanese edition) which uses aufs 20080825.
(b) CD boot without hard disk installation.
(c) under VirtualBox 1.66( virtual machine's memory = 256M )
(2) Operations:
cd /
mkdir /tmp-root
mount -t tmpfs none /tmp-root
mkdir /tmp-root/org /tmp-root/ovl /tmp-root/new
mkdir /tmp-root/org/p10
mkdir /tmp-root/org/p10/p2
mkdir /tmp-root/org/p11
mkdir /tmp-root/org/p11/p2
mount -t tmpfs none /tmp-root/ovl
mount -t aufs -o br:/tmp-root/ovl:/tmp-root/org=ro none /tmp-root/new
ls -id /tmp-root/new/p10 ==> this shows inode number 11
ls -id /tmp-root/new/p10/p2 ==> this shows inode number 12
rmdir /tmp-root/new/p10/p2 ==> inode 11 is deleted.
rmdir /tmp-root/new/p10 ==> inode 12 is deleted.
ls -id /tmp-root/new/p11 ==> this shows inode number 11 , but it
should not.
ls -id /tmp-root/new/p11/p2 ==> this shows inode number 12 , also.
Is this spec or a bug ?
Thanks for advance.
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
