On Mar 06, 2006 23:24 -0600, Joseph D. Wagner wrote:
> > The policy seems to distribute dir inodes uniformly on all block
> > groups. Why do we want to do this? Isn't it better to create a dir
> > inode close to its parent dir inode?
>
> Directories can, and frequently are, moved. If you kept the dir inode
> close to its parent dir inode, you'd have to move dir inodes around
> every time you move directories. Less is more.
I'm not sure what it is you are saying. Directories may be renamed, but
the inodes are never moved.
The reason that directory inodes are spread across the disk is that this
allows later balancing of the file inodes that are created within each
directory. If all of the parent directories are kept in the same group,
you would just end up having all inodes at the start of the filesystem
in use, with high fragmentation and no locality between directories and
the files created therein, and similar problems with inode blocks.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
