![]() | |||||||||||||
Messages in this thread |
On Tue, Mar 07, 2006 at 09:34:53AM -0600, Joseph D. Wagner wrote: > > I'm not sure what it is you are saying. Directories may be renamed, but > > the inodes are never moved. > > If the "dir inode" were to be moved closer to the "parent dir inode", this would become quite an expensive "move" operation, as it would have to move all of the "dir inodes" of the "i386-redhat-linux" directory and all subdirectories away from the "parent dir inode" of "/usr/local/lib/" and closer to the "parent dir inode" of "/usr/lib/". inodes are allocated once and never moved. We're talking about initial allocation. So even though files have their inodes allocated near their parent directory's inode, their inode is not moved when moved to another directory. The reason, as Andreas said, is that if we did allocate directory inodes near their parent inode, we would end up just filling up from the start of the drive and never spreading out. - 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/ | ||||||||||||
| Last update: 2006-03-07 15:41 [from the cache] ©2003-2008 | |||||||||||||