Partition size mismatch

[Vern Clark]

I imaged my ubuntu partition using Clonezilla.
Then I increased the size of my partition.
Now there is a size mis-match after restoring image:
I know I read about this topic but found no solution.

The size use to be 3.7 GB. Now it's over 11 GB as you can see from below.

===== related info =====
vmc@vmc-desktop:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 3.7G 2.5G 1.1G 70% /
tmpfs 1006M 0 1006M 0% /lib/init/rw
varrun 1006M 96K 1006M 1% /var/run
varlock 1006M 0 1006M 0% /var/lock
udev 1006M 148K 1006M 1% /dev
tmpfs 1006M 76K 1006M 1% /dev/shm
lrm 1006M 2.4M 1004M 1% /lib/modules/2.6.28-11-generic/volatile
================================================== ====================================
vmc@vmc-desktop:~$ sudo fdisk -l

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xc701877d

Device Boot Start End Blocks Id System
/dev/sda1 * 1 657 5277321 7 HPFS/NTFS
/dev/sda2 2276 30401 225922091+ 7 HPFS/NTFS
/dev/sda3 658 2116 11719417+ 83 Linux
/dev/sda4 2117 2275 1277167+ 5 Extended
/dev/sda5 2117 2275 1277136 82 Linux swap / Solaris
================================================== =====================================
cfdisk (util-linux-ng 2.14.2)

Disk Drive: /dev/sda
Size: 250059350016 bytes, 250.0 GB
Heads: 255 Sectors per Track: 63 Cylinders: 30401

Name Flags Part Type FS Type [Label] Size (MB)
---------------------------------------------------------------------------------------------------
sda1 Boot Primary NTFS 5404.01
sda3 Primary Linux ext3 12000.69
sda5 Logical Linux swap / Solaris 1307.82
Logical Free Space 0.01 *
sda2 Primary NTFS [] 231344.23 *

====================
vmc@vmc-desktop:~$ cat /proc/partitions
major minor #blocks name

8 0 244198584 sda
8 1 5277321 sda1
8 2 225922091 sda2
8 3 11719417 sda3
8 4 1 sda4
8 5 1277136 sda5
=====================
vmc@vmc-desktop:~$ cat /proc/diskstats
1 0 ram0 0 0 0 0 0 0 0 0 0 0 0
1 1 ram1 0 0 0 0 0 0 0 0 0 0 0
1 2 ram2 0 0 0 0 0 0 0 0 0 0 0
1 3 ram3 0 0 0 0 0 0 0 0 0 0 0
1 4 ram4 0 0 0 0 0 0 0 0 0 0 0
1 5 ram5 0 0 0 0 0 0 0 0 0 0 0
1 6 ram6 0 0 0 0 0 0 0 0 0 0 0
1 7 ram7 0 0 0 0 0 0 0 0 0 0 0
1 8 ram8 0 0 0 0 0 0 0 0 0 0 0
1 9 ram9 0 0 0 0 0 0 0 0 0 0 0
1 10 ram10 0 0 0 0 0 0 0 0 0 0 0
1 11 ram11 0 0 0 0 0 0 0 0 0 0 0
1 12 ram12 0 0 0 0 0 0 0 0 0 0 0
1 13 ram13 0 0 0 0 0 0 0 0 0 0 0
1 14 ram14 0 0 0 0 0 0 0 0 0 0 0
1 15 ram15 0 0 0 0 0 0 0 0 0 0 0
11 0 sr0 0 0 0 0 0 0 0 0 0 0 0
8 0 sda 8845 39472 592941 228368 479 969 11672 4252 0 22964 232616
8 1 sda1 41 595 1860 368 0 0 0 0 0 288 368
8 2 sda2 39 1079 1118 568 0 0 0 0 0 436 568
8 3 sda3 8702 37609 587965 226804 422 969 11672 4136 0 22836 230936
8 4 sda4 3 0 6 120 0 0 0 0 0 120 120
8 5 sda5 39 170 1672 356 0 0 0 0 0 336 356
2 0 fd0 0 0 0 0 0 0 0 0 0 0 0

[Vern Clark]

I found the solution:

     resize2fs

[Steven Shiau]

If you turn on "-r" option in the advanced menu, it actually will use resize2fs to do the job for you after the file system is cloned.

Steven.