Phillip Susi
2013-02-03 03:53:46 UTC
I have been testing using e2image vs tar vs dump | restore to clone an
ext{234] partition lately, and found that dump|restore is
significantly slower ( 15m vs 4m on my system ). It seems the
slowness is on the restore side, rather than the dump side. Looking
at the restore code, I think I have found the culprit.
It appears that there is a "directory file" that is a temp file
created during restoration, that contains fixed 1KiB records for every
directory in the dump. It looks like this file mostly duplicates what
the symtable does, only it is initialized first, then the symtable is
built after, first based on this dirfile, then with the regular files
added on top. Am I missing something or could this dirfile not be
removed entirely and just use the symtable instead?
ext{234] partition lately, and found that dump|restore is
significantly slower ( 15m vs 4m on my system ). It seems the
slowness is on the restore side, rather than the dump side. Looking
at the restore code, I think I have found the culprit.
It appears that there is a "directory file" that is a temp file
created during restoration, that contains fixed 1KiB records for every
directory in the dump. It looks like this file mostly duplicates what
the symtable does, only it is initialized first, then the symtable is
built after, first based on this dirfile, then with the regular files
added on top. Am I missing something or could this dirfile not be
removed entirely and just use the symtable instead?