Thomas Kahle wrote:
my 2 cents:
| So if for example I copied everything over to a different hard drive and
| then copied everything back, it would be "defragmented" then?
I think so yes, but still I would not do it as I think you will hardly
notice the difference, but there is a good chance to screw things up.
| I would think of something like this:
| Boot some live CD.
| Mount old and backup drives.
| Copy old drive to a backup drive using cp -av yada yada.
Its very important to do this as root and preserve all the file
permissions and symbolic links exactly as they are on the drive.
In particular the backup file system must support all this.
(You cannot backup to a FAT file system, etc.)
the cp option "-b" could help, but surely you should read
| Make a new file system on the old drive to make sure all is clean.
| Copy everything back over from the backup to the old drive using cp -av
| yada yada.
| I would also take the opportunity to redo a few partitions while I was
| able to.
If you do so don't forget to update /etc/fstab
and the configuration of the bootloader !
| The biggest slow down by the way is when logging into KDE the first
| time. It takes a long while and that drive is just a getting it. The
| light just stays on while loading everything up.
I personally think this is not due to fragmentation.
On loading KDE just preloads some big libraries (it is a big program
and this takes some time.
Furthermore the libraries are loaded with "LD_BIND_NOW=true", which
makes the linker resolve all the symbols when KDE starts. (KDE takes
longer to load, but later the programs are loaded faster).
You can google for that to learn what it means.
Hope it helps a little
I did a little test. Something fishy here. I did a test with the /data
partition. I store pictures and documents there and it was fragmented.
I cp -av to another reiserfs formatted partition then remade the file
system and copied it back using basically the same command just in
reverse. This is what I got now:
root@smoker / # /root/fragck.pl /data/
3.88457269700333% non contiguous files, 1.04344379261138 average fragments.
root@smoker / #
That is not a lot better than it was before. It was 4.6% before. How
is that? I copied it over then ran the command right after without even
touching the files.
Any ideas? Is there a limit to the fragmenting "smallness"?
firstname.lastname@example.org mailing list