Hi,
many undo.Z under /var/sadm/pkg files exist twice:
<pkg>/save/<patch id>/undo.Z and
<pkg>/save/pspool/<pkg>/save/<patch id>/undo.Z
Why are these files not hard linked? Is there a technical reason for that?
It would be nice to save some space in /var/sadm/pkg ...
Thanks.
> Please can you run the following command and return
> the output generated:
>
> # ls -laR /var/sadm/pkg/
The output would be 57084 lines long, little too much.
Let me give an example to precise what i mean:
# cd /var/sadm/pkg/SUNWbind; find . -type f -ls
252962 -rwxr-xr-x1 rootroot 1604 May 24 16:01 ./install/copyright
252971 -rw-r--r--1 rootroot 967 Dec 4 2004 ./install/depend
253022 -rw-r--r--1 rootroot 1582 Jun 23 2004 ./save/pspool/SUNWbind/install/copyright
253031 -rw-r--r--1 rootroot 967 Dec 4 2004 ./save/pspool/SUNWbind/install/depend
253042 -rw-r--r--1 rootroot 1257 Jun 28 07:22 ./save/pspool/SUNWbind/pkginfo
253053 -rw-r--r--1 rootroot 2363 Jun 28 07:22 ./save/pspool/SUNWbind/pkgmap
25308 1624 -rw-r--r--1 rootother1649311 Jun 28 07:22 ./save/pspool/SUNWbind/save/119783-03/undo.Z
25310 1624 -rw-r--r--1 rootother1649311 Jun 28 07:22 ./save/119783-03/undo.Z
253112 -rw-r--r--1 rootroot 1223 Jun 28 07:23 ./pkginfo
both undo.Z have different inode numbers, so double disk space is needed:
# du -sk /var/sadm/pkg/SUNWbind
3270/var/sadm/pkg/SUNWbind
The directory structure under /var/sadm/pkg/<package name>/save/pspool is formatted to allow support for zones on the system. As non global zones do not have access to the global zone filesystem, files such as undo.Z must be copied rather than linked.
If diskspace is an issue, you might find this document useful:
http://sunsolve.sun.com/search/document.do?assetkey=1-9-14295-1
Good to know why undo.Z can't be hard linked. Thank you!
> If diskspace is an issue, you might find this document useful:
>
> http://sunsolve.sun.com/search/document.do?assetkey=1-9-14295-1
Sorry, have no service plan, don't ask why, i'm private.
Yes i have diskspace problems, /var slice was configured too small (1GB).
First i tried moving /var/sadm/pkg to a larger slice, made pkg a symlink.
That does not work, SUM means no patches have been installed.
Second try was to move completly /var/sadm to a larger slice.
This seems to work good with SUM.
But today i was wondering about that someone changed the symlink /var/sadm back
to a new directory and put only 'smc/...' into it.
Now i know who it was: i run 'smosservice add' to prepare a diskless client.
sadm/smc/smcreg was modified on the symlinked tree, after that /var/sadm was
switched back to a new directory. This makes /var/sadm completly useless,
e.g.: 'showrev -p' answers with 'opendir' :-)
Ok, if i changed something i should not think all will work, so i think about a new
installation with much more space for /var.
