On Wed, 11 Oct 2006 Jakko Pastuchio wrote :
>hi !
>
>On 10/10/06, Avishay Traeger <atraeger@xxxxxxxxxxxxx> wrote:
>>On Tue, 2006-10-10 at 19:15 +0200, Jakko Pastuchio wrote:
>> > I wonder how inodes numbers are allocated/maintainded/recycled.
>>Usually with a bitmap (stored on disk) that says which inode numbers are
>>free and which are used.
>> > does every file on disk have a unique inode number (which is kept
>> > on the disk) and that inode number never changes ?
>>An inode number describes exactly one file on the file system. The
>>inode number should not change.
>>inode numbers are stored in the on-disk inode.
>
>In that case, how do you make sure that there are no inode-number collisions
>between different filesystems mounted ? if every filesystem is responsible to
>allocate and remember its inodes, can't you reach a situation where
>two filesystems you mount gave the same inode number to different
>files ?
Well, as you said there are two different file systems, hence, same inode number on two different file systems will represent two altogether different entities.
>given the inode number in this case, how you can reach the right file ?
the device numbers will be different. So, the (device no + inode number) combination will take you to the right file.
>
>thanks !!!
>jakko
Thanks,
-Rohit
>
>--
>Kernelnewbies: Help each other learn about the Linux kernel.
>Archive: http://mail.nl.linux.org/kernelnewbies/
>FAQ: http://kernelnewbies.org/faq/
>
