Backup /var/adm/sw/save then remove..

[Joe Hege]

Need some space to accomodate new program that creates a large print file, keeps filling up /var. I believe you can back up /var/adm/sw/save then delete and restore at later date. Is this correct? Just trying to make it until weekend when I can extend /var

Thanks
Joe

[Steven E. Protter]

I would NOT do that.

I would do this:

cleanup -c 1

It will commmit all patches superseded more than once, which will probably save a ton of space if you've been patching.

SEP

[Timoh]

If you are intending to backup /var/adm/sw/save then you should consider backing up only files *.gz, but the rest should be left, otherwise a reboot or a failure when these files are gone will cause you so much of extra work. ;-)

[Tom Geudens]

Hi Joe,
If you're not going to install patches in the mean time ... go ahead. I've done this without problems. An even better solution (if you have the space) is to move /var/adm/sw/save to a different filesystem (lv_var_adm_sw_save created in a volumegroup not on the bootdisk) for the time being. As long as you move it back afterwards ...

Regards,
Tom Geudens

[Massimo Bianchi · Accepted solution]

HI, backup is always a good thing, but for the delete part i suugest ypu to use the "cleanup" command, that is supposed to do that thing in a proper way.


cleanup -p -c 2

will do a preview of how many space you will gain, deleting patches that are superceded two times.

cleanup -p -c 1

... one time


cleanup -c #

will commit and remove those patches.

Chek the size of /var/adm/crash/* files, and of /var/adm/syslog/*.log files

Massimo

[Pete Randall]

Joe,

That's possible but you might want to look at the cleanup command. It removes superceded patches, thus freeing space in /var. Do a man cleanup, then try "cleanup -c 1".


Pete

[Tom Geudens]

Hi again Joe ;-),
While you are reorganising (and if your boot disk is large enough) why not move /var/adm/sw itself to it's own filesystem. When we create a server we do this by default (reserving 1024Mb for /var/adm/sw).

Regards,
Tom Geudens

[RolandH]

Before you do that I recommend you to create new ignite tape, it could be that you must use it anytime.


If it is a 11.00/11i system the patch magmt. has changed.

If you now must deinstall a critical patch for example. The system does not simply remove the patch it will do a rollback to the state before. And that can mean that it installs the patch what was topic before you installed the follower patch. Due to that fact the system needs also the patch before.

But for the moment it has no affect to the system if you backup the directory and remove the files there. But it can be difficult if you must remove patches.


Roland

[Tim Adamson_1]

Hi Joe,

Why not setup a symbolic link for the request directory of the queue that you are printing to so that it points to a filesystem that has more space. It might get you out of trouble.


Cheers!!

[twang]

Yes, you're correct, the save dir only contains superceded patches, to gain space of /var you can use HP-UX patch cleanup utility:
# cleanup -c

And I think you should have /var/adm/sw/save in its own file system. That way if you need more space, you can easily extend it.