Well, after I pruned down the size a bit on the CRAB server. Here’s a summary of why that had to be done:
BEFORE:
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_cap-lv_root 50G 40G 7.3G 85% /
tmpfs 1.9G 204K 1.9G 1% /dev/shm
/dev/sda1 485M 45M 415M 10% /boot
/dev/mapper/vg_cap-lv_home 129G 67G 56G 55% /home
/dev/sdb1 1.8T 856G 886G 50% /mnt/storage
/dev/sdc1 1.8T 796G 945G 46% /mnt/backup
AFTER:
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_cap-lv_root 50G 21G 27G 45% /
tmpfs 1.9G 352K 1.9G 1% /dev/shm
/dev/sda1 485M 45M 415M 10% /boot
/dev/mapper/vg_cap-lv_home 129G 17G 106G 14% /home
/dev/sdb1 1.8T 924G 818G 54% /mnt/storage
/dev/sdc1 1.8T 924G 818G 54% /mnt/backup
You will see the problem areas highlighted in red, and the end product in green. I can probably still trim the system / partition a bit, but it’s MUCH better, and should pose no problems with the OS upgrading process. The /boot partition will be fine. 😉
The pruning will be fairly ‘transparent’ to users as I used some pretty slick symbolic links to ‘move’ the content to the storage drive.
The dar backup script for the top level of the storage drive has run about three days, as it’s fairly large. I expect it to complete sometime today, or overnight, and expect to start the upgrade with the Fedora 14 dvd. If all goes well, I might just go ahead and push on with Fedora 15. I really don’t foresee any issues through Fedora 16, but not sure with 17, as it moves a few directories like /sbin and /bin, merging their content under /usr/sbin and /usr/bin for compatibility. Time will tell. 😉