Re: 2.6.9 VFS Issues

[Jan Blunck <jblunck@gmail.com>]

On 11/1/05, Jeff V. Merkey <jmerkey@utah-nac.org> wrote:
>
> I have noticed one change from 2.4 to 2.6 which although esoteric, is
> bothersome.  Did the dache assign static inode identities to
> the "." and ".." directories for 2.6 differnt than the behavior in 2.4?
> I notice that the root of ext based filesystems is now always "2"
> for the root (although readdir commands pass "0" during passes through
> the readdir function calls into the VFS).  I have noticed that
> the user space libs always fix "2" as the value of the inode for the
> root directory.  I am having trouble getting the . and .. entries to show
> up under 2.6, although, they seem to work just fine when you type cd ..
> and cd ., etc.
>
> Here's what dir.c outputs from user space for ext3 FS's:
>
> . type-4 len-16 ino-00000002 off-0000000C
> .. type-4 len-16 ino-00000002 off-00000018
> lost+found type-4 len-24 ino-0000000B off-0000002C
> grub type-4 len-16 ino-00000FC1 off-00000038
> initrd-2.6.5-1.358.img type-8 len-40 ino-0000001D off-00000058
> bzImage type-8 len-24 ino-00000010 off-00000078
> boot.b type-8 len-24 ino-00000011 off-00000088
> chain.b type-8 len-24 ino-0000000E off-00000098
> os2_d.b type-8 len-24 ino-0000000F off-000000A8
> vmlinuz-2.6.9 type-8 len-32 ino-00000012 off-00000150
> kernel.h type-8 len-24 ino-00000019 off-000001FC
> System.map-2.6.5-1.358 type-8 len-40 ino-0000000C off-0000021C
> config-2.6.5-1.358 type-8 len-32 ino-0000000D off-00000238
> vmlinuz-2.6.5-1.358 type-8 len-32 ino-0000001C off-00000400
>

As defined in include/linux/ext3_fs.h:

/*
 * Special inodes numbers
 */
#define EXT3_ROOT_INO            2      /* Root inode */

Cheers,
Jan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/