| 1 |
Thomas Kahle wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> my 2 cents: |
| 5 |
> |
| 6 |
> | So if for example I copied everything over to a different hard drive and |
| 7 |
> | then copied everything back, it would be "defragmented" then? |
| 8 |
> |
| 9 |
> I think so yes, but still I would not do it as I think you will hardly |
| 10 |
> notice the difference, but there is a good chance to screw things up. |
| 11 |
> |
| 12 |
> | I would think of something like this: |
| 13 |
> | |
| 14 |
> | Boot some live CD. |
| 15 |
> | Mount old and backup drives. |
| 16 |
> | Copy old drive to a backup drive using cp -av yada yada. |
| 17 |
> |
| 18 |
> Its very important to do this as root and preserve all the file |
| 19 |
> permissions and symbolic links exactly as they are on the drive. |
| 20 |
> In particular the backup file system must support all this. |
| 21 |
> (You cannot backup to a FAT file system, etc.) |
| 22 |
> |
| 23 |
> the cp option "-b" could help, but surely you should read |
| 24 |
> man cp |
| 25 |
> and |
| 26 |
> man mount |
| 27 |
> |
| 28 |
> | Make a new file system on the old drive to make sure all is clean. |
| 29 |
> | Copy everything back over from the backup to the old drive using cp -av |
| 30 |
> | yada yada. |
| 31 |
> | |
| 32 |
> | I would also take the opportunity to redo a few partitions while I was |
| 33 |
> | able to. |
| 34 |
> |
| 35 |
> If you do so don't forget to update /etc/fstab |
| 36 |
> and the configuration of the bootloader ! |
| 37 |
> |
| 38 |
> | The biggest slow down by the way is when logging into KDE the first |
| 39 |
> | time. It takes a long while and that drive is just a getting it. The |
| 40 |
> | light just stays on while loading everything up. |
| 41 |
> |
| 42 |
> I personally think this is not due to fragmentation. |
| 43 |
> On loading KDE just preloads some big libraries (it is a big program :) |
| 44 |
> and this takes some time. |
| 45 |
> Furthermore the libraries are loaded with "LD_BIND_NOW=true", which |
| 46 |
> makes the linker resolve all the symbols when KDE starts. (KDE takes |
| 47 |
> longer to load, but later the programs are loaded faster). |
| 48 |
> You can google for that to learn what it means. |
| 49 |
> |
| 50 |
> Hope it helps a little |
| 51 |
> Thomas |
| 52 |
> |
| 53 |
|
| 54 |
I did a little test. Something fishy here. I did a test with the /data |
| 55 |
partition. I store pictures and documents there and it was fragmented. |
| 56 |
I cp -av to another reiserfs formatted partition then remade the file |
| 57 |
system and copied it back using basically the same command just in |
| 58 |
reverse. This is what I got now: |
| 59 |
|
| 60 |
root@smoker / # /root/fragck.pl /data/ |
| 61 |
3.88457269700333% non contiguous files, 1.04344379261138 average fragments. |
| 62 |
root@smoker / # |
| 63 |
|
| 64 |
That is not a lot better than it was before. It was 4.6% before. How |
| 65 |
is that? I copied it over then ran the command right after without even |
| 66 |
touching the files. |
| 67 |
|
| 68 |
Any ideas? Is there a limit to the fragmenting "smallness"? |
| 69 |
|
| 70 |
Dale |
| 71 |
|
| 72 |
:-) :-) |
| 73 |
-- |
| 74 |
gentoo-user@l.g.o mailing list |
Archives