leftover junk on my system disk. - VMS

This is a discussion on leftover junk on my system disk. - VMS ; While installing OpenVMS-8.3-update-6 on one of my systems today, the task failed due to lack of disk space. Prior to restarting the update I poked around the disk looking for stuff to delete when I discovered 100,000 (allocated) blocks hiding ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: leftover junk on my system disk.

  1. leftover junk on my system disk.

    While installing OpenVMS-8.3-update-6 on one of my systems today, the
    task failed due to lack of disk space. Prior to restarting the update
    I poked around the disk looking for stuff to delete when I discovered
    100,000 (allocated) blocks hiding in a directory called "[PCSI
    $UNDO_001]". The create date of that directory was 21-OCT-2007 and the
    only things I did on that that were:

    1) upgrade from OpenVMS 8.2 to 8.3
    2) apply OpenVMS-8.3-update-4

    ==========

    $set def KAWC15$DKA0:[000000]
    $dir
    Directory KAWC15$DKA0:[000000]

    000000.DIR;1 BACKUP.SYS;1 BADBLK.SYS;1 BADLOG.SYS;
    1
    BITMAP.SYS;1 CONTIN.SYS;1 CORIMG.SYS;1 DECSERVER
    $SRC.DIR;1
    DELIVER.DIR;1 ERRLOG.CVT;1 HSZ22.DIR;1 INDEXF.SYS;
    1
    PCSI$UNDO_001.DIR;1 SECURITY.SYS;1 SYS$REGISTRY.DIR;1
    SYS0.DIR;1 SYSLOST.DIR;1 VMS$COMMON.DIR;1 VOLSET.SYS;
    1

    Grand total of 37 directories, 737 files.

    $dir [PCSI$UNDO_001...]/grand/siz

    Grand total of 37 directories, 737 files, 84175 blocks.

    $
    ==========

    What is worse is that the junk directory was also found on three other
    platforms. I deleted the junk and rebooted without any problems.
    Hopefully this information will be of use to someone else.

    Neil Rieck
    Kitchener/Waterloo/Cambridge,
    Ontario, Canada.
    http://www3.sympatico.ca/n.rieck/

  2. Re: leftover junk on my system disk.

    In article <2cb26bd8-eda6-4f25-af4c-a3366bdf8b59@8g2000hsu.googlegroups.com>, Neil Rieck writes:
    >While installing OpenVMS-8.3-update-6 on one of my systems today, the
    >task failed due to lack of disk space. Prior to restarting the update
    >I poked around the disk looking for stuff to delete when I discovered
    >100,000 (allocated) blocks hiding in a directory called "[PCSI
    >$UNDO_001]". The create date of that directory was 21-OCT-2007 and the
    >only things I did on that that were:


    That is the recovery data from PCSI. In 001 is the latest data and every
    installation with /SAVE_RECOVERY_DATA (implicit or explicit) does a rename
    *UNDO_nnn to *UNDO_nnn+1 and creates a new PCSI$UNDO_001 directory.

    >1) upgrade from OpenVMS 8.2 to 8.3


    A full installation (what a full VMS installation does for the layered
    products like TCPIP, DECNET, ...) deletes all (current and previous)
    recovery data. And you can't avoid this, so I recommend that if you do
    a logfile of the installation (which I always recommend) do the deletion
    of the old recovery data by hand before you start the new kit installation
    (or you end up with umpteen hundreds DELETE-I-DELETED lines in the logfile).

    >2) apply OpenVMS-8.3-update-4


    And an ECO installation save the recovery data then (for PRODUCT UNDO PATCH).

    >What is worse is that the junk directory was also found on three other
    >platforms. I deleted the junk and rebooted without any problems.


    The supported method of getting rid of them is PRODUCT DELETE RECOVERY_DATA
    but as you noted, deleting the whole directories does work as well.
    You see the advantage of the supported command in (not needing to repeat
    the DELETE command more than once until the whole tree is deleted and of
    course in) the qualifiers /BEFORE= and /OLDEST=

    >Hopefully this information will be of use to someone else.


    Only to them who hadn't followed the various PCSI threads here in COV :-)

    My (PCSI) recommendations still hold:

    1) You need at least PCSI V7.3-402 for a successfull PRODUCT UNDO PATCH
    That means you need at least VMS732_PCSI V1.0 on V7.3-2 (and maybe similar
    ECOs for older versions of OpenVMS). V8.2 and up has no problem with UNDO.
    OpenVMS VAX V7.3 unfortunately still has no similar PCSI ECO and so is
    unable to UNDO a patch (but you may remove the whole product including the
    ECOs and reinstall the product without the ECOs again as always/before).

    Do a PRODUCT SHOW UTILITY to find out if your PCSI is new enough.

    2) You need a patch ECO (-4) for saving (and also not deleting of old/saved)
    Recovery Data. Full kits (-1) cannot save recovery data (they also ignore
    the qualifier and/or the corresponding PCSI logical) and do also delete all
    previously saved recovery data.

    Note: TCPIP V5.5/V5.6 ECOs are not ECOs (TCPIP_ECO), but full kits (TCPIP).
    That means you do not need to install V5.6 before the ECO2 (but you do it
    with the VMS V8.3 upgrade/installation of course ;-) but you do loose
    all saved recovery data then by installing this kit.

    3) Do installations with as much logged info as possible

    eg.
    $ DEF/SYS/EXE AXPVMS$PCSI_EXECUTE_VERIFY YES
    $ DEF/SYS/EXE AXPVMS$PCSI_LOG_TRACE BOTH
    $ DEF/SYS/EXE PCSI$$SAVE_RECOVERY_DATA YES
    $ DEF/SYS/EXE PCSI$LOG TRUE
    $ DEF/SYS/EXE PCSI$SOURCE SYS$SYSDEVICE:[INSTALL_KITS]
    $ DEF/SYS/EXE PCSI$TRACE TRUE

    for PCSI (and OPTIONS L for VMSINSTAL)
    and use a logfile (one for each and every installation !)

    eg
    $ SET HOST 0/LOG= !if DECnet is installed/started
    $ SET HOST node/LAT/LOG= !if LAT is started and outgoing conn enabled
    $ TELNET localhost/LOG= !if TCPIP is inst/start and Telnet Svr enabled

    4) If you plan to install some products/ECOs at once, sort them and
    then install only one product at a time (always with its own logfile)

    a) BACKUP (or a shadow member dismount ;-)
    b) PRODUCT DELETE RECOVERY_DATA
    c) VMSINSTAL the - full and ECO - (*.%) kits
    d) PRODUCT INSTALL the (*-1.PCSI*) full kits
    e) PRODUCT INSTALL the (*-4.PCSI*) ECO kits
    f) Reboot (if neccessary) only once

    5) If you UNDO PATCH, keep in mind that you can only UNDO the newest/last ECO.
    If you need to UNDO an older one you need to undo all newer ones as well.

    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

+ Reply to Thread