Sure I should of clarified I am talking about my root partition

root@esx1 root# vdf -h
Filesystem Size Used Avail Use% Mounted on
/dev/cciss/c0d0p2 4.9G 3.9G 685M 86% /
/dev/cciss/c0d0p1 99M 32M 63M 34% /boot
none 391M 0 391M 0% /dev/shm
/dev/cciss/c0d0p6 2.0G 66M 1.8G 4% /var/log
/vmfs/devices 3.4T 0 3.4T 0% /vmfs/devices
/vmfs/volumes/4495f603-a01e71a3-794d-0017a4499244
129G 628M 128G 0% /vmfs/volumes/storage1
/vmfs/volumes/4570a7b5-1c8dc72f-3bac-0017a44950fc
1.6T 949G 657G 59% /vmfs/volumes/Green
/vmfs/volumes/4571b5a6-c5cafec2-0976-0017a4499244
1.6T 857G 749G 53% /vmfs/volumes/Gold

root@esx1 root# fdisk -l

Disk /dev/sda: 1725.7 GB, 1725771546624 bytes
255 heads, 63 sectors/track, 209813 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 209813 1685322858+ fb Unknown

Disk /dev/sdb: 1725.7 GB, 1725771546624 bytes
255 heads, 63 sectors/track, 209813 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 209813 1685322858+ fb Unknown

Disk /dev/cciss/c0d0: 146.7 GB, 146778685440 bytes
255 heads, 63 sectors/track, 17844 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 13 104391 83 Linux
/dev/cciss/c0d0p2 14 650 5116702+ 83 Linux
/dev/cciss/c0d0p3 651 17508 135411885 fb Unknown
/dev/cciss/c0d0p4 17509 17844 2698920 f Win95 Ext'd (LBA)
/dev/cciss/c0d0p5 17509 17577 554211 82 Linux swap
/dev/cciss/c0d0p6 17578 17831 2040223+ 83 Linux
/dev/cciss/c0d0p7 17832 17844 104391 fc Unknown

go easy...

I apologize I currently do run my backups from my IIS server so the patches are never placed in the updates directory. My question is since applying 30+ updates since 3.0.1 to 3.0.2 and so on it has created a large root partition. Is there a way to expand that partition so I can still apply patches (which update files in esx) that expand the esx volumes? These volumes are going to grow over time. I know with 3.5 coming out eventually I will blow away the partitions and start from scratch but in the mean time there were more patches released Jan 2nd and I want to apply them but I get errors because of the root partition being close to full. I hope that makes sense.

go easy...

Well after doing a "find -name '*' -size +1000k" I found a majority of my files that were larger were located in the ./cache/yum/update/packages/ directory. So I ran the "yum clean all" command and my root partition went from 86% to 66%. I never even began to think that the .rpms would still be there after the ftp patching process.

A bit of searching showed that these are files downloaded by yum from the depot, and that the way
to clean them out is by using 'yum clean all' command. It is probably a good idea to include doing this as part of the patching process.

It seems to allow me to get about 20% back of storage space.

Thanks again for the help.

go easy...