Ext4 has fragmentation - 7.1% is not contiguous,

[urdrwho5]

I booted into recovery and did an Fdick and in the end it said that 7.1% is not contiguous. In windows it is easy, there are a plethora of defrag programs to choose from and it can be done while in windows. Apparently not so with Kubuntu or any other linux distro.

I've read where people say to use Gpart and move partitions around so that ext3 is at the very end, shrink it and then ....well I can't remmeber what was next.

Is there any programs, any way to easily defrag that Ext4.

I think it happened yesterday. Yesterday the computer tried to open a file that was on my external drive, what was in the file, I do not know. I was just snooping about on the external drive and wanted to see that text file. It went into a long, long, long time trying to open that file, I lost control of the mouse, keyboard, etc. Finally I just hit the power off button. I probably caused a bit of fragmentation but now without massive study time, I have no idea how to defrag that partition.

Any ideas??

[vinnywright]

you do not run fsck on a mounted file system ,,,,,this may explain your 7.1% non contiguous ..generally their is no reason to do so,, the system will run it at boot (wile the kernel is runing in ram ) before the file system gets mounted every so often ,,,if you want to force it for the next reboot open a terminal and do

sudo touch /forcefsck

and reboot then check in /var/log/boot.log. to see if it ran .

VINNY

[urdrwho5]

Hm? Well when I boot into recovery you have all those options, resume; clean; dpkg; fsck; grub, etc. Fsck says it is to check all file systems and I would have thought that it was safe to run because it was on the Recovery Menu (filesystem state: read-only).

I guess I was wrong? I'll try your way.

Tried it your way. At reboot it automatically started, at 88% I went to the kitchen to grab a cup of coffee, upon returning I saw that the system has rebooted. Finished the job I guess.

Went to that boot.log and it may be there but I don't see anything that fsck had been run? Could it be that the log is different because it is a dual boot system

 * Stopping Read required files in advance[ OK ]
 * Starting Mount filesystems on boot[ OK ]
 * Stopping Track if upstart is running in a container[ OK ]
 * Starting Initialize or finalize resolvconf[ OK ]
 * Starting set console keymap[ OK ]
 * Starting Signal sysvinit that virtual filesystems are mounted[ OK ]
 * Starting Signal sysvinit that virtual filesystems are mounted[ OK ]
 * Starting Bridge udev events into upstart[ OK ]
 * Starting Signal sysvinit that remote filesystems are mounted[ OK ]
 * Stopping set console keymap[ OK ]
 * Starting device node and kernel event manager[ OK ]
 * Starting load modules from /etc/modules[ OK ]
 * Starting cold plug devices[ OK ]
 * Starting log initial device creation[ OK ]
 * Starting Uncomplicated firewall[ OK ]
 * Stopping load modules from /etc/modules[ OK ]
 * Starting configure network device security[ OK ]
 * Starting configure network device[ OK ]
 * Starting configure network device security[ OK ]
 * Starting Mount network filesystems[ OK ]
 * Stopping Mount network filesystems[ OK ]
 * Starting Bridge socket events into upstart[ OK ]
 * Starting configure network device[ OK ]
 * Starting configure network device security[ OK ]
 * Starting configure network device[ OK ]
 * Stopping cold plug devices[ OK ]
 * Stopping log initial device creation[ OK ]
 * Starting enable remaining boot-time encrypted block devices[ OK ]
 * Starting Signal sysvinit that the rootfs is mounted[ OK ]
 * Starting Clean /tmp directory[ OK ]
 * Stopping Clean /tmp directory[ OK ]
 * Starting SMB/CIFS File Server[ OK ]
 * Starting Signal sysvinit that local filesystems are mounted[ OK ]
 * Starting configure network device security[ OK ]
 * Stopping Mount filesystems on boot[ OK ]
 * Starting flush early job output to logs[ OK ]
 * Stopping Failsafe Boot Delay[ OK ]
 * Starting Enabling additional executable binary formats[ OK ]
 * Starting System V initialisation compatibility[ OK ]
 * Stopping flush early job output to logs[ OK ]
 * Starting configure virtual network devices[ OK ]
 * Starting system logging daemon[ OK ]
 * Starting D-Bus system message bus[ OK ]
 * Starting modem connection manager[ OK ]
 * Starting configure network device security[ OK ]
 * Starting SystemD login management service[ OK ]
 * Starting bluetooth daemon[ OK ]
 * Starting Bridge file events into upstart[ OK ]
Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
 * Starting AppArmor profiles        
[ OK ]
 * Starting mDNS/DNS-SD daemon[ OK ]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[ OK ]
 * Stopping Reload cups, upon starting avahi-daemon to make sure remote queues are populated[ OK ]
 * Stopping System V initialisation compatibility[ OK ]
 * Starting System V runlevel compatibility[ OK ]
 * Starting Restore Sound Card State[ OK ]
 * Starting ACPI daemon[ OK ]
 * Starting anac(h)ronistic cron[ OK ]
 * Starting save kernel messages[ OK ]
 * Stopping Restore Sound Card State[ OK ]
 * Starting regular background program processing daemon[ OK ]
 * Starting deferred execution scheduler[ OK ]
 * Stopping anac(h)ronistic cron[ OK ]
 * Stopping CPU interrupts balancing daemon[ OK ]
 * Starting network connection manager[ OK ]
 * Stopping save kernel messages[ OK ]
 * Starting automatic crash report generation[ OK ]
 * Stopping Restore Sound Card State[ OK ]
 * Starting cups-browsed - Bonjour remote printer browsing daemon[ OK ]
 * Stopping crash report submission daemon[ OK ]

you do not run fsck on a mounted file system ,,,,,this may explain your 7.1% non contiguous ..generally their is no reason to do so,, the system will run it at boot (wile the kernel is runing in ram ) before the file system gets mounted every so often ,,,if you want to force it for the next reboot open a terminal and do

sudo touch /forcefsck

and reboot then check in /var/log/boot.log. to see if it ran .

VINNY