/var/sadm/pkg is very huge



  • 1. in.mpathd - What is it , removing it OK ? slow boot up in Solaris 10
    XXXX@XXXXX.COM writes: > >come up until 10-15 mins later. Below is the terminal server capture >of the boot up sequence at atlantis. One thing we noticed is that >atlantis has "in.mpathd" process started up automatically during boot >up but the other server doesn't have that process. However, both >servers have the identical /etc/default/mpathd file. Is "in.mpathd" >the culprit for the slow start up at atlantis ? > mpathd is associated with ethernet interface configurations that provide failover to a standby ethernet port when the primary fails (e.g. the cable is unplugged or the etherswitch dies), or provide traffic balancing across two or more ports. So take a look at the /etc/hostname.xxx files (where "xxx" is an ethernet port name like "hme0" or "bge1") to see if a group name has been defined in one or more of them. Will mpathd slow booting down so much? I wouldn't expect it to, but I suppose it could. -Greg -- Do NOT reply via e-mail. Reply in the newsgroup.
  • 2. SMF services stoppping order
    Hi everyone :-) I'm totally confused about order in which SMF service are stopped (or can be stopped). The following is sample relationship between services: - database (no dependencies) - web server (depends on working database) - multi-user-server milestone (depends on web server) From my observations so far follows, that when one invokes "svcadm disable database", there will be be following order of services shutdown: 1 - database 2 - web server 3 - multi-user-server milestone And here a problem arises... When stop method of database service is being executed and database processes are being shut down, some web server process looses its connection with database and goes into maintenance state. I'm astonished, because I thought that SMF is aware about propability of such dependencies between services' processes. Is there any way to configure SMF to offline dependant services in "down-top" way? In the above example I would expect following shutdown order: 1 - multi-user-server milestone 2 - web server 3 - database Is it possible to make such relationship without placing "svcadm disable <dependant>" in stop method of dependency service? Thank you in advance for any hints! Best regards, Marcin

/var/sadm/pkg is very huge

Postby Alexander Skwar » Tue, 21 Aug 2007 22:39:13 GMT


I noticed that my /var/sadm/pkg is rather big. It's currently about 1.7g.
Can I deleted no longer required "save" directories from there (like


Alexander Skwar

Re: /var/sadm/pkg is very huge

Postby Richard B. Gilbert » Tue, 21 Aug 2007 23:00:14 GMT

Yes, you can.  CAN!!  I would suggest keeping copies somewhere.  Just 
deleting this stuff, without backup, does not seem wise to me.  OTOH, I 
see no need to clutter up your /var with them.  If you can burn them to 
CD/DVD, that should provide sufficient backup.

Re: /var/sadm/pkg is very huge

Postby Tim Bradshaw » Wed, 22 Aug 2007 01:11:18 GMT

Only if you do not ever want to back out those patches.


Re: /var/sadm/pkg is very huge

Postby Publicus Nomen » Wed, 22 Aug 2007 02:19:40 GMT

In the /var/sadm directory are files called obsolete.Z.  These can be
deleted and return a large amount of space.

# find /var/sadm/pkg -name obsolete.Z -exec rm {} \;

After this you can _still_ backout patches if necessary.

Sun InfoDoc 14295 explains this and a lot more, but it's only available to
contract customers :-(

Geoff Lane, Airstrip One

Today's Excuse:  disks spinning backwards - toggle the hemisphere jumper.

Re: /var/sadm/pkg is very huge

Postby Dave Miner » Wed, 22 Aug 2007 03:23:57 GMT

Also, if you delete the save/pspool files, you'll end up unable to 
create zones.


Re: /var/sadm/pkg is very huge

Postby Huge » Thu, 23 Aug 2007 16:37:35 GMT

I ran amok in /var/sadm/pkg in the past to regain space, and so much stuff
stopped working that I restored it from backup ...

I'd find another way, if I were you.

                 "Religion poisons everything."
            [email me at huge {at} huge (dot) org <dot> uk]

Similar Threads:

1./var/sadm/pkg direcotry Q

Since the pkginfo files in the /var/sadm/pkg/pkg_name is not being touched
if i remove /var/sadm/pkg/pkg_name/save dir, removing the save direcotory is
not going to effect when i run pkgrm or patchrm?  or is the pkginfo files
being called only when i run the command pkginfo, showrev -p and
patchadd -p?

what is the save dir for anyway?

****PLEASE REMOVE "_SPAM_SUCKS" before reply


If /var/sadm/pkg is inadvertently evacuated,

is the machine effectively headed for a reinstall?


3.pkg - recreated /var/sadm/install/contents

For some unknown reason, /var/sadm/install/contents is missing
on a couple of our systems, making pkginfo and friends useless.
A web search has not turned up any method for recreating the

So, is there a magic set of commands that I can run to
repopulate that ugly beast?


For example; if an RPM database gets corrupt on a linux system.

rm -f /var/lib/rpm/__db*
rpm -vv --rebuilddb

4.for huge "recommended" patch, not enough room in /var/sadm/patch

Not enough room in /var/sadm/patch, the install-script

But on other partitions and disks I have *lots* of
space available.  Just not on the root partition,
which contains /var/sadm/patch (among much else,
of course).

Might this work.

Rename /var/sadm/patch to eg /var/sadm/patch2-original,
then create a patch dir in some partition that had
logs of space, and then make /var/sadm/patch
a symlink to there.

Or should I symlink either higher up the var/sadm tree,
or symlink *several* of those directories?

And is there any reason to *copy* those directories
to where I'm going to symlink to, so that if there's
already some contents, they'll still be "there"?

(That install-script doesn't explicitly check for
this trick -- I hope not.)


Or is there maybe some better way to do surmount this not-enough-disk pbm?


Of course I do down to single-user before doing
the   ./install_cluster,

but any reason I can't leave everything else

I mean, in recent years, has anyone *ever* gotten
hurt by doing that?   (If so, please say how, so we
can all get wised-up on this, uh, danger.)



5.Repost: Solaris Live Upgrade: questions about /var/sadm

Sorry for the report, seems like my news reader misbehaved (Ah, MSFT!)

 According to the solaris FAQ:


|3.40) Why does installing patches take so much space in /var/sadm?

    All the files that are replaced by a patch are stored under
    /var/sadm/patch/<patch-id>/save so the patch can be safely
    backed out.  Newer patches will save the old files
    under /var/sadm/pkg/<pkg>/save/<patch-id>/undo.Z, for each package

    You can remove the <patchdir>/save directory provided you also
    remove the <patchdir>/.oldfilessaved file.  Newer patches will not
    install a .oldfilessaved file.

    Alternatively, you can install a patch w/o saving the old
    files by using the "-d" flag to installpatch.

|3.41) Do I need to back out previous versions of a patch?

    No, unless otherwise stated in the patch README.
    If the previous patch installation saved the old
    files, you may want to reclaim that space.

    Patches can be backed out with (Solaris 2.6+):
     patchrm <patch-id>

    or in earlier releases:

     /var/sadm/patch/<patch-id>/backoutpatch <patch-id>

    Backoutpatch can take an awful long time, especially when the
    patch contained a lot of files.  This is fixed in later versions
    of backoutpatch.


Prior to doing the live upgrade, I would like to minimize the size of my
root partition
(containing /var in my case) Can I safely remove all patches (not just the
save directories)
from /var/sadm/patches or will live upgrade do it automatically ?

I presume that after a solaris upgrade, the liste of installed patches on
the system will be NULL ?

Another last point, does "back out patch" mean to go back to the state
BEFORE the patch was applied ?
I don't understand the 3.41 paragraph. What does it mean ? It seems to mean
that whenever you apply a new
patch, you should go back to the previous version before installing ?

Ex: Original package = blabla-01

Apply patch blabla-02  (BlaBla-01 saved)

You now want to apply patch blabla-03.

Does question 3.41 ask: "if you need to install patch blabla-03 you should
first back ou to blabla-01 ?"

If so, what do you do if the README tells you that you have to, but you
REMOVED the save directory ?

Thanks !

6. Solaris Live upgrade: questions about /var/sadm/patch

7. Cleaning Up /var/sadm

8. frequency alphabet for files in /var/sadm/install/contents

Return to unix


Who is online

Users browsing this forum: No registered users and 75 guest