2009/8/31 Christian Völker <chrisc...@knebb.de>: > Yohoo! >> With backuppc the issue is not so much fragmentation within a file as >> the distance between the directory entry, the inode, and the file >> content. When creating a new file, filesystems generally attempt to >> allocate these close to each other, but when you link an existing file >> into a new directory, that obviously can't be done so you end up with a >> lot of long seeks when you try to traverse directories picking up the >> inode info.
I believe you are mistaken in this. Your confusing directory entries with inode entries. When you hard link a file from one directory to another you have two directory entries pointing to the same inode. You can do a simple test by touching a file and then make a hard link to a new file and list with "ls -li". You will see that both files share the same inode number. -- Jonathan Craig ------------------------------------------------------------------------------ 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 _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
