Hi,
can anybody explain the following behaviour on RHEL 5.3 in VM-ware?

1. Installed RHEL 5.3 in 20 GB partition
2. Not big enough
3. Created 2nd. 20 GB virtual disk incl. 1 20 GB partition
4. started a resuce CD
5. copied / partition the new partition using "cp -R -preserver /mnt/oldpartition/* /mnt/newpartition/"
6. exchanged this line in /etc/fstab:

LABEL=/ / ext3 defaults 1 1

whith this line:

/dev/sdb1 / ext3 defaults 1 1

(sdb1 is the new 20 GB partition)

7. reboot
8. now see this funny output

[root@localhost ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdb1 3960348 3385476 370448 91% /
/dev/sda5 14270000 5077768 8455656 38% /home
/dev/sda1 46633 10516 33709 24% /boot
tmpfs 517600 0 517600 0% /dev/shm


[root@localhost ~]# fdisk /dev/sdb

The number of cylinders for this disk is set to 2610.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sdb: 21.4 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 2610 20964793+ 83 Linux


How is this possible that a 20 GB partition only shows to have 4 GB in "df"

Any ideas?

Best Regards,

Romeo
__________________
Romeo Kienzler
r o m e o ( a - t ) o r m i u m . d e

And which command did you use to format the new partition ?
Is it ext3 or ext2 ?

A 20GB partition doesn't necessarily imply a 20GB file system. So, it all comes down to how did you format this thing.

Ok, I have the feeling that I maybe have formatted it as 4 GB partition, correct?

I've used the following command:

mkfs.ext3 /dev/sdb1

That should have allocated the whole partition.

But, if for some reason the fs has not grown to fit the partition you can always use the resize2fs tool to grow ext2/3/4 file systems.

Please see the following result:

[root@localhost ~]# tune2fs -l /dev/sdb1
tune2fs 1.39 (29-May-2006)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: e9469849-a623-4388-84fc-aaa67838f7e9
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype sparse_super large_file
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 2621440
Block count: 5241198
Reserved block count: 262059
Free blocks: 4243721
Free inodes: 2504270
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1022
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Filesystem created: Mon Mar 29 01:04:46 2010
Last mount time: Mon Mar 29 01:06:15 2010
Last write time: Mon Mar 29 04:20:31 2010
Mount count: 1
Maximum mount count: 28
Last checked: Mon Mar 29 01:04:46 2010
Check interval: 15552000 (6 months)
Next check after: Sat Sep 25 01:04:46 2010
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: tea
Directory Hash Seed: a1ac4a3b-f15a-40df-8971-5dc58da22541
Journal backup: inode blocks

So block count is 5241198 and block size is 4096 which leads to 20GB.

So I assume the file system is correct?

What else could cause this behavior?

Is it because formerly it was a LVM partition and now I've mounted it directly?

Best Regards,

Romeo

No idea.

Did you try fsck -f on that volume? Maybe it's something weird on the VM itself.

no, fsck completed also without errors :/

Ok, got it working:

1. dd if=/dev/sda2 of=/dev/sdb1
2. resize2fs /dev/sdb1 20G