How to defrag pup001?

[Lobster]

Using the fragmentation viewer in 1.0.7 (early test ISO) I noticed my pup001 was fragmented. This seems to be affecting the size of programs I can download. Even if resizing the file size. Anyway the sure thing would be to defrag this. I looked at fsck, which runs if pup001 is damaged or potentially damaged through premature shutdown. However the options did not have it down as a defragger (as far as I understand) . . .

Not really quite sure what is best to do to defrag pup001? Any ideas?

[GuestToo]

the fragmentation viewer is probably showing you that the pup001 file is fragmented ... not that the Puppy files in the ext2 file system inside the pup001 file are fragmented

if the pup001 file is on a vfat (Windows) partition, it would not be surprising that it's fragmented

to defrag the pup001 file, you would defrag the Windows partition using the Windows defragger

there are tools to defrag linux file systems, but basically, you really don't need to

you can see how fragmented the ext2 file system is inside the pup001 file by typing something like
fsck.ext2 -vfn /mnt/home/pup001

the -n switch tells it to not make any changes to the file system ... do not "fix" any errors it might find, it's mounted and it will damage the file system ... those errors are only there because pup001 is mounted ... do not fsck a mounted file system

the amount of fragmentation will be in a line something like this:
72 non-contiguous inodes (1.2%)

[Lobster]

Code: Select all

# fsck.ext2 -vfn /mnt/home/pup001
e2fsck 1.34 (25-Jul-2003)
Pass 1: Checking inodes, blocks, and sizes
Inode 180270, i_blocks is 4338, should be 4336.  Fix? no

Inode 180271, i_blocks is 4094, should be 4084.  Fix? no

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -40864 -(741734--741738)
Fix? no


/mnt/home/pup001: ********** WARNING: Filesystem still has errors **********


    6087 inodes used (3%)
     444 non-contiguous inodes (7.3%)
         # of inodes with ind/dind/tind blocks: 1403/394/1
  643311 blocks used (81%)
       0 bad blocks
       0 large files

    5036 regular files
     904 directories
       0 character device files
       0 block device files
       0 fifos
       0 links
     137 symbolic links (137 fast symbolic links)
       1 socket
--------
    6078 files
# 

444 non-contiguous inodes (7.3%)

This is on a Ubuntu Linux HD (and pup001)
no other partitions

Is it best to run Ubuntu?
(I would prefer to run something from Puppy)

I am getting to the stage where deleting the pup001
(and starting afresh) is becoming cumbersome
However this would be alleviated if key info was saveable on line

[GuestToo]

in general, you don't need to defrag linux file systems

7% fragmented means the file system is 93% not fragmented ... also, fragmentation on a Linux file system does not cause the performance problems that it does on a dos/vfat file system

if your pup001 file is on the ubantu partition, it probably isn't fragmented much

if there's lot's of free space, copying a file will defragment it ... if there is enough contiguous free space (all in one block), the copy of the file will not be fragmented

if you want to try a defragger, you could try o&o defrag ... it will not work on reiserfs, it will work on ext2 and ext3 ... i have never tried the Linux version

it's always good to have a lot of free space on the drive ... it helps to keep it from getting fragmented

[Lobster]

thanks for the info - most useful and much appreciated