Hello. 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 /var/sadm/pkg/SUNWzfsu/save)? Thanks, Alexander Skwar
Hello. 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 /var/sadm/pkg/SUNWzfsu/save)? Thanks, Alexander Skwar
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.
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.
Also, if you delete the save/pspool files, you'll end up unable to create zones. Dave
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]
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 database. So, is there a magic set of commands that I can run to repopulate that ugly beast? Linolil 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 says. 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 mounted? 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.) Thanks!!! David
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: --------8<----------------- |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 patches. 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. ---------------->8--------------------------- 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
8. frequency alphabet for files in /var/sadm/install/contents
Users browsing this forum: No registered users and 75 guest