Confused about the space I'm using on HD...

MooMooMilk · 09-13-2005, 08:21 PM

Okay,
I had a Seagate that was about 20gig's, and then I decided it was time to a larger HD, so I purchased an 80gig Seagate. I deleted all partitions, and then did a fresh install with FC4. I kind of just clicked through the auto-partition thing during the install process, since I wasn't familar with it (I probably should have used the manual-partition option, like I have before).

Anyways, I'm looking the storage in KinfoCenter and it says:

/dev/VolGroup00/LogVol00 ext3 size: N/A MountPoint: /
/dev/fd0 auto size: N/A MountPoint:/media/floppy
/dev/hda1 ? size: 98.7MB /boot
/dev/hdc auto 674.9 /media/cdrecord
/dev/hdd auto N/A /media/cdrom
/dev/mapper/VolGroup00-LogVol00 ? 107.6GB MountPoint: /

So am I using the potencial of my system, or should I reinstall and redo the partition?

Thanks,
moomoomilk

Emmanuel_uk · 09-14-2005, 01:44 AM

in a console try to type
fdisk -l
and
mount

That should be enough info to know if you have fully the 100 Gb

MooMooMilk · 09-14-2005, 06:06 PM

[moomoomilk@localhost sbin]$ ./fdisk -l
[moomoomllk@localhost sbin]$ mount

Quote:

/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
/dev/proc on /proc type proc (rw)
/dev/sys on /sys type sysfs (rw)
/dev/devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hda1 on /boot type ext3 (rw)
/dev/shm on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
automount(pid2038) on /misc type autofs (rw,fd=4,pgrp=2038,minproto=2,maxproto=4)
automount(pid2082) on /net type autofs (rw,fd=4,pgrp=2082,minproto=2,maxproto=4)
/dev/hdc on /media/cdrecorder type iso9660 (ro,nosuid,nodev,_netdev,user=moomoomilk)

uhh... I don't see any space information here. Can someone tell me from the information that I provided? I've afraid to go about compiling new software, since I may have to reinstall FC4. Am I using all of my space to its potencial? Or am I like using only 3 gigs?

When log on as a super user I get this:

Quote:

[root@localhost sbin]# ./fdisk -l

Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 9729 78043770 8e Linux LVM

Disk /dev/hdb: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Thanks,
MooMooMilk

JCipriani · 09-14-2005, 07:18 PM

Try df -h, example output:

Code:

$ df -h
Filesystem                Size   Used  Avail Capacity  Mounted on
/dev/disk0s9               56G    48G   7.5G    86%    /
devfs                      94K    94K     0B   100%    /dev
fdesc                     1.0K   1.0K     0B   100%    /dev
<volfs>                   512K   512K     0B   100%    /.vol
automount -nsl [514]        0B     0B     0B   100%    /Network
automount -fstab [517]      0B     0B     0B   100%    /automount/Servers
automount -static [517]     0B     0B     0B   100%    /automount/static

Dunno what it looks like on a kernel with volume groups though but it seems like it would be similar. See the df man page for more info, but the -h option just makes the output be in useful units instead of block counts.

MooMooMilk · 09-14-2005, 07:50 PM

Thanks! You are the best. The output was:

Quote:

[root@localhost sbin]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
108G 5.0G 98G 5% /
/dev/hda1 99M 14M 80M 15% /boot
/dev/shm 125M 0 125M 0% /dev/shm
/dev/hdc 675M 675M 0 100% /media/cdrecorder

Using the df command is a lot simplier, than using fdisk or another partition tool/command. It makes it a lot easier to terminine the actual available space. Thanks a million for your help.