⟦4bfa9a9a7⟧

TextFile

«ff»
*******************************************************

         R E L E A S E   D E S C R I P T I O N

*******************************************************




Module id number: CSS/920
-------------------------

Module name:      FMS
---------------------

Actual release:   06.06            Release date: 850502
-----------------------            --------------------

Previous release: 06.05            Release date: 850401
-----------------------            --------------------


Release descriptions for releases prior to release 0600 can be
found in the release description for release 0602 and earlier.
--------------------------------------------------------------


This version includes the following submodule releases:

  FM :            0608
  DCM :           0606
  CTRL :          0602
  EXCEPTION :     0602
  COMON_IF :      0100
  DIGNOSTIC_VAR : 0101
  DISK_OP_LOG :   0102
  INIT :          0601



New facilities:
---------------


>> Release 0606 <<

1. A new compl. code Different_access_dates_1 has been added.  This means
   that a mount command was requested with a volume use parameter that
   specified that the volumes to be mounted should be dual, whereas the
   specified volumes did not carry the same time-stamps.  Dual disk 0
   did carry the newest time-stamp.

>> Release 0604 <<

None.


>> Release 0603 <<

1. The FMS can now perform logging of disk operations.
   The FMS will, if properly configured, log all necessary
   information concerning the change of the status of devices
   and log all the writing disk operations, that write to both
   disks of a dual disk pair.
   A standard link module is delivered, that presents an interface
   to a very simple physically logging link module, which is
   configuration dependant.
   If this logging facility is not to be used, a dummy link module
   is delivered. This must be included instead of the standard
   logging module.
2. A set of new INIT completion codes were introduced in release 0601.
   Most of these reflect, that a mismatch exists between the
   configuration and the linking of the FMS.

   *) #0334  Nbr_ths <> 0 and FMS not linked with TQM
   *) #0335  Nbr_chs <> 0 and FMS not linked with CRAM
   *) #0336  INIT failed to fetch configuration record from config process
   *) #0337  Timeout on wait for message from config process
      #0338  FM and DCM mismatch with respect to support of dual disks
      #0339  CTRL was not compiled with DMA  support and nbr_dmas <> 0
      #033A  CTRL was not compiled with TQM  support and nbr_ths  <> 0
      #033B  CTRL was not compiled with CRAM support and nbr_chs  <> 0
   *) #033F  Workarea was less than #2000

   Those marked with *) are not implemented yet, but will be in some
   future release.

   The completion code, #0480, which occur sometimes, implies, that the
   disk driver has observed an error on the disk subsystem (drive, cable
   and controller), but was not able to determine a proper completion
   code. The cause for the completion code is often cabling problems or
   alike.


>> Release 0602 <<

1. New functions:
     INCLUDEDEVICEKIND     - to allow new exotic, system specific
                             device kinds to be used.
2. A new volume use - PARTIAL_DUALIZABLE_VOL - introduced.
   If a dual volume is mounted with this volume use, the FMS
   does not check, that all sectors on the volume have been dualized
   when a finish_dualize on the volume is received.
   When a volume is mounted with this volume use, it must meet the
   same criteria as with DUALIZABLE_VOL.


>> Release 0601 <<

1. New functions:
     EXMOUNT
     SETFILESIZE
2. The start-sector for Dualize-sectors may be defaulted.
3. It is possible to perform read_sectors on mounted volumes.
4. CRAM & TQM interface now supported again.
5. Statistics are gathered.


>> Release 0600 <<

1. A set of new functions has been included. These are:
     UNMOUNT
     GET_DEVICE_INFORMATION
     CHANGE_VOLUME_ID
     CHANGE_BOOT_ENTRY
2. The FMS may report device and system errors via the Event Report
module to subscribing processes.
3. The FMS reports the amount of missing workarea at initialisation
if it cannot initialize itself.
4. It is possible to dismount and unmount a volume, where the drive is
not ready.
5. It is possible to use a write-protected drive (even though this may
cause numerous error reports).
6. The sector count for dualize_sectors may be defaulted.



Changes:
--------


>> Release 0606 <<

1. The name of compl. code Different_access_dates has been changed to
   Different_access_dates_0.  The meaning of the new compl. code is
   that a mount command was requested with a volume use parameter that
   specified that the volume to be mounted should be dual, whereas the
   specified volumes did not carry the same access time-stamps.  Dual
   disk 0 did carry the newest access time-stamp.

>> Release 0605 <<

1. DISCARD af a master disk during dualization/redualization is no longer
   allowed (PR 1255).
2. It is check that the disk nbr. of DISCARD don't exceed l.
3. It is now possible to close files, in connection with user_off commands,
   on a volume on which 'disk_change' has been detected (PR 1256).


>> Release 0604 <<

1. The DISK_OP_LOG module now puts a specific pattern into the LOG area
   to facilitate recognition of a closed system versus a crashed system.
   This also implies, that a new version of QUICKDUALIZER must be used.
   The PKK project may use the version found in DISK_OP_LOG.D


>> Release 0603 <<

   None.


>> Release 0602 <<

1. It is now possible to change the boot entry of a mounted device.
2. The number of sector buffers used for dualization limited to 64.
3. It is possible to redualize a volume, on which redualization took
   place when the system crashed.
4. In the DCM, the function FLUSH is moved to the general procedures.
   This means, that the version DCM_CR801 is only needed when using
   TQM. When adding CRAM only, the standard versions of DCM can be used.


>> Release 0601 <<

1. Performance has been improved in the DCM by keeping track of how many
disk_accesses that not yet have been scheduled and only searching the
sector list if there are any.
2. The layout of DEVICE_INFORMATION has been changed.
3. All parts of SFD and BFD entries are initialized when allocated.
4. A reserved volume may be dualized.


>> Release 0600 <<

1. A number of completion codes have been changed, especially the driver
generated (controller) completion codes.
2. The execution level has been changed back from 1 to 2. This is
possible due to the use of the Driver Support Procedures (CSS/357)
for local user communication.
3. A set of checks have been implemented to ensure, that all sectors
of a dual disk pair are dualized.
4. Disk controller device addresses are no longer given as DEVPR, but
as true device addresses.
5. Writing to dual disk pairs are sequentialized - not executed in
parallel.



Errors corrected:
-----------------


>> Release 0605 <<

l. Error in bad sector handling during dualization corrected.
2. Sector access log extended due to the possibility for multiple
   outstanding write requests on one disk.


>> Release 0604 <<

1. The File Manager (FM) can now handle the situation of
   mounting dualizable (or partial dualizable) a dual disk pair
   of which the master disk is not accessible.


>> Release 0603 <<

1. A file handler did not perform proper recovery during dualization
   if one of the disks failed.
2. The DCM did not handle dropout of one of the disks of a dual
   disk pair of it was redualizing.


>> Release 0602 <<

1. The BFD entries and SFD entries are now always zeroed before use.
2. The FM now recovers correctly if it cannot assign driver #2 on a dual
   device
3. The FM now reports disk errors on assigning devices to ERP.
4. The DCM now handles dropout of a disk driver correctly.


>> Release 0601 <<

1. An internal UPDATE command is issued when bad sectors are substituted.
This should keep the homeblock on the disk consistent.
2. Bad marked sectors are removed from the cache when marked.
3. Whenever the homeblock is updated during dulization of a disk pair,
the state of the slave volume is set to dualising_vol.


>> Release 0600 <<

1. When dualising a disk, updates were only done on the master disk.
   - Updates are now done on both disks.
2. Dualisation of a disk now terminates if there is a hard error on
the slave disk.



Reported errors, not corrected:
-------------------------------


>> Release 0604 <<

   As release 0601.


>> Release 0603 <<

   As release 0601.


>> Release 0601 <<

   As release 0601.


>> Release 0601 <<

1. The following CPECR's are not handled by this release :
     870 :  BFD index sector not updated when BFD extended.
     971 :  It should not be possible to remove not-empty directories.


>> Release 0600 <<

1. The following CPECR's are not handled by this release :
     791 :  A bad marked sector remains in the disk cache.
     782 :  The homeblock is not updated after a sector substitute.



CPECRs implemented in current release: 1256
----------------------------------------------------

Comments:
---------


************************************************************************
* Please run the Disk Salvation program on volumes, accessed by FMS,   *
* at regular intervals, eg once a fortnight. If any inconsistency is   *
* reported by either of CHECKFILES or CHECKNAMES , then stop the       *
* salvation and inform Jens Anton Schmidt (CRAS CR80-DD-SED).          *
* Any system errors or inexplicable circumstances, that might have     *
* been caused by the FMS, should be reported IMMEDIATELY.              *
************************************************************************ «a5»
DataMuseum.dk

CR80 Hard and Floppy Disks

⟦4bfa9a9a7⟧ TextFile

Derivation

TextFile
