Can i delete this files whitout troubles?

[Ignacio Rodríguez Arrós]

I think that this is a very simple question but i want to be completely sure.
I have in my hp-9000 many files in a directory named /discos/vol2/machine/sw/patch/PHSS_nnnnn where nnnnn is a number. I think that these are the patches instaled in the system when the machine was configurated in 1999 so the date shown when i do a ll of the files is 1999.
The answer is Can i remove this directory (../patch) without any problem?
Thanks in advance.

[Stefan Schulz]

There is a tool called cleanup which is designed for removal of outdated Patches. Check if it is allready installed. If not, go to software.hp.com and search for it.

It no such good idea to remove this directory "by hand".

Hope this helps

Regards Stefan

[Magdi KAMAL]

Hi Ignacio,

As said before, it's NOT a good idea to manually delete patches unless you are 100% sure you are no more needing it. This could cause a system panic !

try using the cleanup tool to remove any unneeded patches.

Magdi

[Wodisch]

Hello Ignacio,

check wether there is any "symbolic" or "soft" link to
that directory, from "/var/adm/sw/" or below.
If not, make a backup of it (tar should be ok) and then
remove the files in there - oh and check first, if all
those files only have one name (second column of the
output of "ls -l" - if they have more than just one name
removing them in this directory does not help at all!
Then you will have to find all their names/links (the
command "find /MNTPOINT -inod ### -print" comes
to mind, where "MNTPOINT" is the mount-directory of
the filesystem we are talking about, and "###" would
be the i-node number of the file, as shown by "ls -i").
HTH,
Wodisch

[eran maor]

Hi

first you can check all the patches that are install on your system with the command swlist -l product | grep -i PH

second about the dir that you said , it depent if you have a volume group name discos because the dir is not the dir that the patches are sitting

the patches are sitting in the loc. : /var/adm/sw/products

it is also depents where this dir is sitting in vg00 or in a diff vg( not the root ) if the dir is sitting on non root vg you can delete it .

my advise is : backup this files to a tape
do a make_recovery if the file
are sitting in the vg00

delete the files

if you dont know what to do dont delete it , if you need to have move space you can gain it
from other things

[Alex_17]

Hi, Ignacio,

try cleanup -c 1

Good luck.

Alex.

[Ignacio Rodríguez Arrós]

I have this directory in vg01, and also in /var/adm/sw i have the directory products, and another directory linked to /discos/vol2/machine/sw/path named patch.
I have also instaled the cleanup utility, can I use it whithout any risk?

[Bill Alger]

Hello Ignacio,

The patches are copied files from a pre patched file. Here are your possibilities.
1) You remove them but then can never remove a recalled patch.
2) You run the cleanup function (Highly recommended).
3) Try moving /var/adm/sw/patch to it's own mount point on another drive.

If you use cleanup it will remove all but the current backup. Here is an example:

You load patch PHCO_1111. It backs up /duhh.
You load patch PHCO_2222. It backs up /duhh (with PHCO_1111 fix).
You load patch PHCO_3333. It backs up /duhh (with PHCO_1111 and PHCO_2222 fix).

I recommend running the cleanup with the -i option. This will clean up the IPD at the same time.

DO NOT USE -F!!! This will remove all patches and backups. You will be completely stuck with no backout.

I hope this helps.

[Deshpande Prashant]

HI
Use
#cleanup -p -c 2 to see/preview all the patches that are superseeded at leaset by twice.
then use
#cleanup -c 2 to commit all patches superseeded atleast by twice, this will release space occupied by this patches.

You can also selectively commit the patches using
#swmodify -x patch_commit=true

Thanks.
Prashant Deshpande.

[someone_4]

hello
Can you please tell me what it means when you commit a superseded patch?

Richard

[Deshpande Prashant]

Hi Richard
Here is some extract from man cleanup.

The cleanup -c command can be executed to commit all patches that have been superseded specified number of times. The only benefit from committing patches is that disk space will be recovered in the /var/adm/sw/save directory.
Extreme care should be used when committing patches. Once a patch has been committed, it cannot be removed from the system unless the appropriate files from the /var/adm/sw/save directory are recovered from some source, like a backup. Patches should only be committed when you are satisfied with their behavior. Recovering disk space should not be the only factor considered when committing patches.

Thanks.
Prashant Deshpande.

[someone_4]

Yeah I saw that in the man pages thanks.
So in other words when you commit a patch it is a "commitment" to that patch saying that you are going to stick with it. But what is a superseeded patch and why are some "seeded" more then once?

Richard

[Deshpande Prashant]

Richard
Some patches are replaced/seeded more than once over a period.
eg. PHCO_17792 replaced by 19047 by 21187 by 23876.
So PHCO_17792 is seeded by 3.

Prashant.