Suggestion for INSTALL PURGE and SHUTDOWN.COM

When shutting down a system, proper dismounting of disks is always
important, especially when you have shadowsets involved since it makes
the rebooting process and subsequent remounting of drives much faster
(no volume rebuidling needed and in case of shadowsets, a much fater
re-integration of a disk into the shadow set).

The standard shutdown procedure does the INSTALL PURGE after having
called the site SYSHUTDWN.COM procedure. But SYSHUTDWN is the one where
the system manager is responsible for properly dismounting all
non-system disks. Unfortunatily, proper dismounting of disks is
impossible if there are still installed or opened files.

As a result, I have two suggestions:

1- INSTALL PURGE/DEVICE=disk:

This would limit the de-installation of files to those on a specific
drive. This would enable a procedure to deinstall all files on a
specific disk prior to dismounting it.


2- add a SYSHUTDWN_DISKS.COM procedure to be called by SHUTDOWN.COM
after all processes have been stopped, files deinstalled etc, at which
point the user would have a far better chance of properly dismounting
the disks.


Currently, SYSHUTDWN.COM is called before logicals such as OPC$REBOOT
have been set. So that procedure isn't aware if a reboot will be made
quickly or not.

In the case of disks mounter clusterwide, if you're going to reboot
within a minute, then you may not need to dismount/CLUSTER a local drive
since the other nodes will regain access to it within mount-verification
deadline. But if not doing a reboot, you may wish to really dismount the
drive clusterwide because that drive is really becoming unavailable.
(and INSTALL PURGE/DEVICE becomes useful in a SYSMAN operation to zap
installed files on that disk on all nodes).
.

Relevant Pages

  • Re: P4P800-VM - contant reboots when SATA disks attached
    ... drive attached (two "known good" drives - one a WD another a Seagate) ... If I reset the CMOS setting and leave the SATA drives unattached, ... The moment I attach the SATA disks, ... the system goes into infinite reboot. ...
    (alt.comp.periphs.mainboard.asus)
  • Some Test with DVD-RAM
    ... I have done some quality assessment of two DVD-RAM capable ... DVD-burners with four different DVD-RAM brands. ... both drives ... These disks are incredibly bad. ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: Reward offered: Macintosh software for Corvus Omninet
    ... Constellation III set since it was released, ... moved to the Mac and uploaded, emailed, whatever. ... The original disks are generic, they don't say anything on the ... I refurbished a couple 800K drives and a couple 1.44MB drives so that ...
    (comp.sys.apple2)
  • RE: bad blocks... random death
    ... > the disks with bad blocks work actually fine elswhere (in ... The drives are fine. ... including your drive cables, ... grounded to the chassis and through the chassis to the ...
    (RedHat)
  • Re: Need Recovery Disk?
    ... It is, and this is, of course, the fatal flaw in the recovery partition ... to immediately create restore disks.. ... reproduced the drives in the first place. ... support for a laptop owned by a client, a US citizen who purchased the unit ...
    (microsoft.public.windowsxp.help_and_support)