----- Original Message ----- From: Orvar Korvar <[EMAIL PROTECTED]> Date: Tuesday, August 19, 2008 9:22 am Subject: [osol-discuss] What happened to blastwave.org? To: [email protected]
> Hey! What happened to the life saver blastwave.org? Us solaris newbies > loves that site! Give me my blastwave back. Something that should have taken four hours in the middle of the night resulted in a set of patches for a primary Solaris 10 ( Update 5 ) server actually using all 16GB of the /var filesystem. In fact, almost everything is ZFS here but the root filesystem is just a big fat UFS filesystem on that server. 16GB should be enough for root I would think. Not when you have a pile of zones and then need to patch. Patch 138864-01 has been successfully installed. See /var/sadm/patch/138864-01/log for details Patch packages installed: SUNWperl584core SUNWpl5u Checking installed patches... Executing prepatch script... Verifying sufficient filesystem capacity (dry run method)... Insufficient space in /var/sadm/pkg to save old files. Space required in kilobytes: 41594 Space available in kilobytes: 41328 WARNING: Skipping patch 138899-01 /usr/bin/nawk: can't open file /tmp/patchadd-1819112778/138899-01.12778/dryrun.fs.asc source line number 1 bah ... # df -F ufs -k Filesystem 1024-blocks Used Available Capacity Mounted on /dev/md/dsk/d0 16525754 16318971 41526 100% / # du -sk /var 1676699 /var I swear I can not catch a break this week. Everything else is up .. but thisprimary server is down while I re-jigger disk space. One moment please ... Dennis ps: who would have figured that patches and 12 zones = massive disk space used up? _______________________________________________ opensolaris-discuss mailing list [email protected]
