                                             H                     Spiralog____________________________________________!                     Release Notes                          July 1996                   F                     Software Version:             Spiralog File SystemC                                                   for OpenVMS Alpha =                                                   Version 1.1   G                     Operating System:             OpenVMS Alpha Version 5                                                   7.0                  J           ________________________________________________________________           July 1996   B           Possession, use, or copying of the software described inC           this documentation is authorized only pursuant to a valid D           written license from Digital or an authorized sublicensor.  A           While Digital believes the information included in this E           publication is correct as of the date of publication, it is +           subject to change without notice.   @           Digital Equipment Corporation makes no representationsA           that the use of its products in the manner described in B           this publication will not infringe on existing or futureB           patent rights, nor do the descriptions contained in thisB           publication imply the granting of licenses to make, use,>           or sell equipment or software in accordance with the           description.  /            Digital Equipment Corporation 1996.              All Rights Reserved.  ;           The following are trademarks of Digital Equipment =           Corporation: DEC, Digital, OpenVMS, POLYCENTER, VAX :           DOCUMENT, VMS, VMScluster, and the DIGITAL logo.  3           The following are third party trademarks:   9              POSIX is a registered trademark of the IEEE.   @           All other trademarks and registered trademarks are the/           property of their respective holders.   E           This document was prepared using VAX DOCUMENT, Version 2.1.                                  C   _________________________________________________________________   C                                                            Contents          1  What's New in Version 1.1?   4         1.1   Reported Free Disk Space is CalculatedC               Differently...................................    1-1 9         1.2   Reported Free Disk Space is Up to Date in a C               VMScluster....................................    1-3 C         1.3   New Command to Control the Cleaner............    1-3 C         1.4   New Save Trail Format.........................    1-5 C         1.5   How to Show a Version 1.0 Save Trail..........    1-5 C         1.6   Deleting Files When the Disk is Almost Full...    1-5 C         1.7   Troubleshooting Device Full Errors............    1-6 C         1.8   Other Problems That Have Been Fixed...........    1-9   &   2  Upgrading to Spiralog Version 1.1  C         2.1   Do a Full Save After Upgrading................    2-1 /         2.2   Avoid Mixing Server Versions in a C               VMScluster....................................    2-2      3  Restrictions   C         3.1   Memory Requirements...........................    3-1 C         3.2   Products That are Not Supported...............    3-2      4  Known Problems   7         4.1   Reinstall Spiralog After You Reinstall or C               Upgrade the Operating System..................    4-1 8         4.2   The System Fails If You Restore Files to aC               Disk That is Nearly Full......................    4-2 7         4.3   Insufficient Memory Can Make File Restore C               Sessions Hang.................................    4-2     C                                                                 iii                    8           4.4   Volume Restore Sessions Do Not Check theE                 Target Device.................................    4-3 E           4.5   Page and Swap Files Are Not Supported.........    4-4 7           4.6   Three GETDVI Item Codes Return the Null E                 String........................................    4-4 1           4.7   SYS$SEARCH Routine's RSL Field is E                 Input/Output..................................    4-4                                                                                  iv                         I                                                                         1 I         _________________________________________________________________   I                                                What's New in Version 1.1?       C               o  Reported Free Disk Space is Calculated Differently   G               o  Reported Free Disk Space is Up to Date in a VMScluster   3               o  New Command to Control the Cleaner   &               o  New Save Trail Format  5               o  How to Show a Version 1.0 Save Trail   <               o  Deleting Files When the Disk is Almost Full  3               o  Troubleshooting Device Full Errors   4               o  Other Problems That Have Been Fixed  F                 ________________________ Note ________________________  A                 Versions 1.1 and 1.0-1 of Spiralog are identical.   E                 Spiralog Version 1.0-1 is available as an ECO release *                 through the TIMA database.  F                 ______________________________________________________  >         1.1 Reported Free Disk Space is Calculated Differently  I               The free disk space shown by SHOW DEVICES is now calculated D               differently, to make it more predictable and reliable.  G               The SHOW DEVICES command now gives a pessimistic estimate H               of free disk space. It shows the amount of space in unusedG               (clean) segments minus an estimate for the amount of that B               space that may be needed by cached data that has notF               yet been written to disk. It ignores the space currentlyI               occupied by obsolete data that the cleaner may subsequently                reclaim.  I                                            What's New in Version 1.1? 1-1                 What's New in Version 1.1?:     1.1 Reported Free Disk Space is Calculated Differently    B           The estimate for the amount of space needed by unwritten>           cached data is conservative. When the cached data is@           subsequently written to disk, it usually takes up muchD           less space and you will see the reported free space rising           to reflect this.  C           For example, your Spiralog volume has no unwritten cached @           data, so SHOW DEVICES shows the amount of space in theB           unused segments. You now write some data to a file whoseB           caching attribute is set to write-behind. The free space@           shown by SHOW DEVICES immediately drops by 500 blocks,?           which is the estimate of the amount of space that may @           be needed to write the data to disk. Within 30 secondsC           the data is written to disk. The free space shown by SHOW D           DEVICES rises by 400 blocks because the data only used 100           blocks of disk space.   D           SHOW DEVICES normally gives a very pessimistic estimate of"           free disk space because:  C           o  It overestimates the amount of space that is needed by #              unwritten cached data.   C              In a large VMScluster, when the disk is busy and there E              is a lot of unwritten data in the VMScluster caches, the B              free space shown by SHOW DEVICES can be close to zeroB              even though there is actually plenty of free space on              the disk.  D           o  It does not include any space occupied by obsolete data7              that the cleaner may subsequently reclaim.   C              To get a more accurate estimate of free space, you can B              use the new SPIRALOG SET VOLUME command to change theC              cleaner mode to Nonstop (see Section 1.3). This forces D              the cleaner to proactively reclaim disk space. You willD              notice the reported free space rising rapidly for a fewC              minutes while the cleaner cleans the segments that are               easiest to clean.  ;              Reported free space then rises more slowly and @              performance degrades as the cleaner cleans segments7              that are more and more difficult to clean.     "     1-2 What's New in Version 1.1?           I                                                What's New in Version 1.1? I                1.2 Reported Free Disk Space is Up to Date in a VMScluster     B         1.2 Reported Free Disk Space is Up to Date in a VMScluster  H               In a VMScluster, the free disk space shown by SHOW DEVICESG               is no longer out of date on some computers. All computers C               running Spiralog Version 1.1 now show the same value.   .         1.3 New Command to Control the Cleaner  A               The cleaner can now operate in two modes, Lazy (the #               default) and Nonstop.   H               Normally the cleaner operates in Lazy mode. It waits untilE               a whole segment becomes obsolete (until all the data in F               the segment has been either updated or deleted) and then9               reclaims the space occupied by the segment.   C               However, when the amount of space available in unused @               (clean) segments on the disk gets low, the cleanerD               automatically starts to proactively reclaim disk spaceG               by cleaning segments that contain some live data and some D               obsolete data. The cleaner copies all the non-obsoleteH               data in these segments into a new unused segment, and thenD               reclaims the disk space used by the original segments.  G               When the cleaner is in Lazy mode, it normally proactively G               reclaims disk space only when SHOW DEVICES shows that the E               free space is low. The definition of low depends on how D               much unwritten data is in the VMScluster caches; it isF               150 000 blocks if there is no unwritten cached data, andH               can be about 500 000 blocks for a volume that has a lot of$               unwritten cached data.  G               You can use the SPIRALOG SET VOLUME command to change the 3               cleaner mode to Nonstop. For example:   :               $ SPIRALOG SET VOLUME FSA4: /CLEANER=NONSTOP  G               This forces the cleaner to proactively reclaim disk space I               all the time, even when there are plenty of unused segments                on the disk.  G               Proactively reclaiming space is expensive in terms of CPU H               and I/Os, so by default, the cleaner operates in Lazy mode8               and becomes proactive only when necessary.  D               The cleaner mode is automatically set to Lazy when theC               server for a volume first starts up, and whenever the 4               server fails over to a standby server.  I                                            What's New in Version 1.1? 1-3                 What's New in Version 1.1?*     1.3 New Command to Control the Cleaner    ?           Use Nonstop mode to force the cleaner to reclaim disk            space, for example:   A           o  Use Nonstop mode to improve the accuracy of the free )              space shown by SHOW DEVICES.   @              For example, you want to run a batch job that needsD              2 000 000 blocks, but SHOW DEVICES shows that there are&              only 850 000 free blocks.  D              You cannot run your batch job because it might fill theD              disk. Although the batch job will automatically triggerA              proactive cleaning when the space in unused segments E              gets low, you do not know in advance whether the cleaner 2              will be able to reclaim enough space.  E              So before you run the batch job, you select Nonstop mode C              to force the cleaner to reclaim the disk space used by B              obsolete data. After five minutes, SHOW DEVICES showsA              1 750 000 free blocks; you cannot run your batch job               yet.   B              Five minutes later, SHOW DEVICES shows 2 100 000 freeB              blocks. You can now set the cleaner back to Lazy mode%              then run your batch job.   @           o  Use Nonstop mode to reduce the size of the savesnap$              created by a full save.  E              A full save saves every segment that contains live data. B              It saves the entire contents of each segment-both the<              live data and the obsolete data in the segment.  A              By forcing the cleaner to clean before the save, you C              reduce the amount of obsolete data that is saved. This D              reduces the size of the savesnap and improves the speedB              of subsequent restores. It also improves the speed ofB              the save itself. However the price you pay is reduced4              performance during the forced cleaning.  @           In a VMScluster, you must issue the SET VOLUME commandC           on the server for the volume, otherwise it fails with the "           following error message:  F           %SPIRAL-E-NOTSERVER, this computer is not the server for the           volume  E           To find out the current cleaner mode, use the SPIRALOG SHOW 6           VOLUME command on the server for the volume.  "     1-4 What's New in Version 1.1?           I                                                What's New in Version 1.1? I                                                 1.4 New Save Trail Format     !         1.4 New Save Trail Format   G               The format of save trails has changed to include a number 2               that uniquely identifies the volume.  I               This ensures that you cannot accidentally do an incremental G               save of a volume using the save trail for another volume. C               The incremental save now fails instead of creating an                invalid savesnap.   0         1.5 How to Show a Version 1.0 Save Trail  G               Because the save trail format has changed, you cannot use F               the SPIRALOG SHOW TRAIL command to examine a Version 1.0F               save trail; the command fails with an error message like               this:   G               %SPIRAL-E-STRAILNOACC, unable to access the volume's save -               trail FSA100:[000000]save.trail I               -BCK-E-STRAILBAD, file is either corrupted or is not a save                trail   I               To examine save trails created by Spiralog Version 1.0, use ,               the TYPE command. For example:  >               $ TYPE FSA4:[V10_SAVE_TRAILS.USERS]SAVE.TRAIL;77  7         1.6 Deleting Files When the Disk is Almost Full   I               When the disk gets full, it is now more likely that deleted ?               files and directories will be marked as obsolete.   <               When you delete a file or directory, Spiralog:  F               1. Removes it from the volume's namespace, so that users!                  cannot access it   H                  At this point the DELETE command returns with a successB                  status; subsequent attempts to access the file orD                  directory fail with a file not found error message.  %               2. Marks it as obsolete   G               When the disk is nearly full, Step 1 may succeed but Step G               2 may fail. This means that although the file is deleted, F               it is not marked as obsolete so its disk space cannot beI               reclaimed. Spiralog Version 1.1 reduces the chances of this                happening.  I                                            What's New in Version 1.1? 1-5                 What's New in Version 1.1?3     1.6 Deleting Files When the Disk is Almost Full     A           If the disk is nearly full and Spiralog has problems at >           Step 2, it now issues the following OPCOM message onA           the volume's server within 15 seconds of the successful +           completion of the DELETE command:_  A           Spiralog: starting emergency delete procedure to try to            delete filey  D           Spiralog then does its utmost to carry out Step 2 and markE           the file as obsolete. It outputs one of the following OPCOM E           messages on the server, depending on whether it succeeds or            not:  ?           o  Spiralog: ending emergency delete procedure - filee              delete succeeded   A              This message means that the file or directory is now_               marked as obsolete.  A           o  Spiralog: asynchronous delete failure - disk is full   A              This message means that the disk is so full that youaA              cannot delete any files or directories. Create a neweD              Spiralog volume on a bigger disk, then copy the data to8              the new volume (see Step 9 in Section 1.7).  *     1.7 Troubleshooting Device Full Errors  D           With Spiralog Version 1.1, follow these steps if you get a:           device full error when you try to delete a file:  E           1. If you were not saving the volume with the SPIRALOG SAVE C              command when you got the device full error, go to Step               2.r  E              Otherwise, wait until the save has finished. The cleanerr?              is restricted during a save, but once the save hassB              finished, you should stop getting device full errors.  D              After the save has finished, wait a few minutes for theA              cleaner to resume normal operation. If you still get (              these errors, go to Step 2.  D           2. Tell your users not to access the volume until you have+              fixed the device full problem.a  "     1-6 What's New in Version 1.1?    e      I                                                What's New in Version 1.1? I                                    1.7 Troubleshooting Device Full Errors     H                  In the next few steps, you will attempt to delete filesF                  to try to free up space on the disk. To increase yourD                  chances of success, make sure that no other user isI                  creating, deleting or updating files in the volume while                   you do this.i  H               3. Reset the server state in either of the following ways:  F                  o  Issue the SPIRALOG FAILOVER command on the server.  I                  o  Dismount then remount the volume on the server (using ;                     SPIRALOG DISMOUNT then SPIRALOG MOUNT).   F               4. Enable operator messages of type Disks on the server:  &                  $ REPLY /ENABLE=DISKS  I               5. Try to delete a single file, and look for OPCOM messages.E                  on the server after you issue the DELETE command. If "                  possible, choose:  A                  o  A medium-sized file (about 200 to 500 blocks)g  1                  o  A file that is not fragmentedg  H                     Choose a file that was written in one go by creatingE                     a new version. Do not choose a file that has ever-G                     been updated or extended without its version number.D                     changing, such as a mail folder, database or RMS#                     Journaled file.P  F                  Note that although you are having problems writing toH                  the volume, you can still read it. If you choose a fileF                  that you still need, copy it to another volume before                  you delete it..  F               6. The action you take now depends on whether the DELETE5                  command of Step 5 returned an error:.  C                  o  If the DELETE command failed with a device full (                     error, go to Step 9.  B                  o  If the DELETE command completed with a successE                     status, check whether you get the following OPCOMa*                     message on the server:  H                     Spiralog: starting emergency delete procedure to try"                     to delete file  I                                            What's New in Version 1.1? 1-7                 What's New in Version 1.1?*     1.7 Troubleshooting Device Full Errors    C                 If you do not see this message within 15 seconds of C                 the successful completion of the DELETE command, go 3                 to Step 8. Otherwise, go to Step 7._  E           7. You saw the OPCOM message of Step 6. This means that the D              disk is almost full but Spiralog is doing its utmost to.              mark the file's data as obsolete.  >              Carry on monitoring OPCOM messages on the server:  ;              o  Go to Step 8 if you see this OPCOM message:   B                 Spiralog: ending emergency delete procedure - file                  delete succeeded  ;              o  Go to Step 9 if you see this OPCOM message:m  D                 Spiralog: asynchronous delete failure - disk is full  >           8. Spiralog managed the mark the file you deleted as>              obsolete. Although there is no guarantee that the>              cleaner will be able to reclaim the space used byB              it, the probability of the cleaner failing to reclaim>              the space is very low if you chose a medium sized)              defragmented file in Step 5._  B              Repeat Steps 5 to 7 to delete more files. As the free@              space rises, you can relax the restrictions in StepB              5, and start deleting larger files and using wildcard:              characters to delete several files at a time.  @           9. Your attempt to free up some disk space failed. The@              disk is so full that you cannot delete any files or!              directories from it.t  E              Create a new Spiralog volume on a bigger disk, then copy (              the data to the new volume.  A              For example, you create a new volume and mount it as D              FSA6, then use this command to copy the contents of the2              full volume, FSA3, to the new volume:  J              $ BACKUP FSA3:[000000...]*.*;* FSA6:[*...] /BY_OWNER=ORIGINAL  D              If you were restoring files to the original volume whenD              it became full, the BACKUP command may complain that itC              cannot open files in the BACKUP_PRIVATE directory, fore              example:t  "     1-8 What's New in Version 1.1? a  a      I                                                What's New in Version 1.1? I                                    1.7 Troubleshooting Device Full Errors     0                  %BACKUP-E-OPENIN, error opening>                  FSA3:[BACKUP_PRIVATE]F_RESTORE.DIR;1 as input<                  -SYSTEM-W-BADFILENAME, bad file name syntax  <                  You can safely ignore these error messages.  G               10.The next time you save the new volume that you createda7                  in Step 9, remember to do a full save.   F                  If the next save is an incremental, the SPIRALOG SAVE;                  command will fail with this error message:a  6                  %SPIRAL-E-SAVEFAIL, error during saveG                  -BCK-E-MISMATCH_VOLID, volume and savetrail mismatched   /         1.8 Other Problems That Have Been Fixedi  H               o  The online help no longer contains the errors described?                  in the Release Notes for Spiralog Version 1.0.s  G                  It has also been enhanced to include a new Tasks topichI                  that gives examples of how to set up and manage SpiralogoB                  volumes. For example, to find out how to set up a2                  Spiralog volume use this command:  9                  $ HELP SPIRALOG TASKS SETTING_UP_VOLUMESa  E               o  The SPIRALOG SAVE command no longer makes the systemcF                  crash with an INVEXCEPTN bugcheck code if the disk is                  full.                              I                                            What's New in Version 1.1? 1-9r    a                    I                                                                         2yI         _________________________________________________________________   I                                         Upgrading to Spiralog Version 1.1     F               Read this chapter before you upgrade to Spiralog Version               1.1:  /               o  Do a Full Save After Upgrading   =               o  Avoid Mixing Server Versions in a VMScluster   F                 ________________________ Note ________________________  A                 Versions 1.1 and 1.0-1 of Spiralog are identical.   E                 Spiralog Version 1.0-1 is available as an ECO release *                 through the TIMA database.  F                 ______________________________________________________  *         2.1 Do a Full Save After Upgrading  B               You must restart your backup schedule after you have/               upgraded to Spiralog Version 1.1.   I               For each of your Spiralog volumes, the first scheduled saveN4               after the upgrade must be a full save.  F               copy If the first scheduled save after the upgrade is anH               incremental save, the save will fail with an error message               like this:  G               %SPIRAL-E-STRAILNOACC, unable to access the volume's save -               trail FSA100:[000000]save.trailnI               -BCK-E-STRAILBAD, file is either corrupted or is not a save                traili        I                                     Upgrading to Spiralog Version 1.1 2-1t    t      %     Upgrading to Spiralog Version 1.1b4     2.2 Avoid Mixing Server Versions in a VMScluster    4     2.2 Avoid Mixing Server Versions in a VMScluster  E           To avoid disrupting your backup schedule, we recommend thatlB           you plan your upgrades to make sure that all the serversD           for a given Spiralog volume are upgraded at the same time.  @           For example, if you have a Spiralog volume that can beE           served by two computers, we recommend that you upgrade both            computers together.   D           Spiralog Version 1.1 cannot read Spiralog Version 1.0 saveC           trails, and vice versa. So, if you upgrade one server and B           not the other, a scheduled incremental save will fail if?           the last scheduled save was done by the other server. A           Your backup schedule will be disrupted because you willM>           be forced to do a full save when you wanted to do an           incremental save.                                                         )     2-2 Upgrading to Spiralog Version 1.1n e  s                    I                                                                         3nI         _________________________________________________________________   I                                                              Restrictionsu    G               This chapter describes restrictions that apply to VersionrI               1.1 of Spiralog and that are not mentioned elsewhere in thee               Spiralog docset:  $               o  Memory Requirements  0               o  Products That are Not Supported  D               These restrictions also apply to Spiralog Version 1.0.           3.1 Memory Requirementsa                  We recommend that:  G               o  Each computer on which you mount a Spiralog volume has -                  at least 64 Mbytes of memory   F               o  For each Spiralog volume mounted on the computer, youI                  increase NPAGEVIR by 2,000,000 and NPAGEDYN by 1,000,000l  C                  For example, if you want to mount two volumes on ac.                  computer, follow these steps:  G                  1. Add these two lines to the computer's MODPARAMS.DATn                     file:s  (                     ADD_NPAGEVIR=4000000(                     ADD_NPAGEDYN=2000000  )                  2. Reboot using autogen:.  7                     $ AUTOGEN SAVPARAMS REBOOT FEEDBACKt        I                                                          Restrictions 3-1                 Restrictions'     3.2 Products That are Not Supported     '     3.2 Products That are Not Supportedn  A           When these Release Notes were written, Spiralog did note)           support the following products:              o  POSIX for OpenVMS  ,           o  DEC TCP/IP Services for OpenVMS  7           o  Non-Digital software file caching productsc                                                                           3-2 Restrictions v  e                    I                                                                         4nI         _________________________________________________________________   I                                                            Known Problems     G               This chapter describes known problems with Version 1.1 ofc               Spiralog:a  F               o  Reinstall Spiralog After You Reinstall or Upgrade the!                  Operating Systeme  H               o  The System Fails If You Restore Files to a Disk That is                  Nearly Full  H               o  Insufficient Memory Can Make File Restore Sessions Hang  G               o  Volume Restore Sessions Do Not Check the Target Devicel  6               o  Page and Swap Files Are Not Supported  ?               o  Three GETDVI Item Codes Return the Null String   ?               o  SYS$SEARCH Routine's RSL Field is Input/Output   F               These problems also apply to Spiralog Version 1.0 unless               stated otherwise.   A         4.1 Reinstall Spiralog After You Reinstall or Upgrade the              Operating System  B               The process of reinstalling or upgrading the OpenVMSC               operating system currently removes various files that                Spiralog uses.  @               This means that you must reinstall Spiralog if you9               reinstall or upgrade your operating system.           I                                                        Known Problems 4-1  r  n           Known ProblemsK     4.2 The System Fails If You Restore Files to a Disk That is Nearly Full     ?     4.2 The System Fails If You Restore Files to a Disk That isa         Nearly Fulln  C           Your system may fail if you use a file restore session tor5           restore data to a disk that is nearly full.i  >           If the disk becomes full when a file restore session@           is restoring data to it, your system may fail. If thisD           happens, use the SPIRALOG CANCEL RESTORE command to cancelB           the file restore session as soon as the system restarts.  >           This problem does not apply to Spiralog Version 1.0.  ?     4.3 Insufficient Memory Can Make File Restore Sessions Hang   A           If your computer does not have enough virtual memory, a B           file restore session may hang instead of failing with an,           insufficient memory error message.  E           Set your process PGFLQUOTA quota to at least 500,000 before ?           you start or continue a file restore session with the            following commands:r  #              SPIRALOG RESTORE FILESs&              SPIRALOG CONTINUE RESTORE  C           File restore sessions may require a significant amount ofsD           virtual memory; the more files you are restoring, the more#           memory the session needs.a  A           If your file restore session hangs, follow these steps:t  B           1. Abort the SPIRALOG RESTORE FILES or SPIRALOG CONTINUE7              RESTORE command, for example, with Ctrl/Y.u  B           2. Cancel the session, using the SPIRALOG CANCEL RESTORE              command.   %           3. Do one of the following:s  @              o  Check that your system page file is sufficientlyE                 large, then increase your process PGFLQUOTA quota and                  try again.  ?              o  Split your restore session into several smallerFE                 restore sessions, each of which restores fewer files.sE                 The fewer files you restore in a restore session, the -                 less memory the session uses.f       4-2 Known Problems o  e      I                                                            Known ProblemscI               4.3 Insufficient Memory Can Make File Restore Sessions Hangs    I                     When the first session is finished, start the second.sI                     When the second session is finished, start the third,n                     and so on.  B         4.4 Volume Restore Sessions Do Not Check the Target Device  G               Be very careful to specify the right Files-11 volume whenhG               you continue a volume restore session, or you may corrupt                 the target volume.  D               For volume restore sessions, the following commands doE               not check that the Files-11 volume you specify as theireF               parameter is the volume to which your restore session is               restoring data:   6                  SPIRALOG CANCEL RESTORE target-device8                  SPIRALOG CONTINUE RESTORE target-device4                  SPIRALOG SHOW RESTORE target-device  B               For example, the SPIRALOG SHOW RESTORE command showsD               the volume restore session whose details are stored inG               SYS$LOGIN:V_RESTORE.SESSION, regardless of which Files-112@               volume you supply as the parameter to the command.  A               Be careful to give the right Files-11 volume as thevD               parameter to the SPIRALOG CONTINUE RESTORE command. IfH               you give the wrong Files-11 volume you will corrupt it if:  D               o  The Files-11 volume contains a Spiralog volume, and  F               o  That Spiralog volume is not currently mounted on your                  computer.  F               For example, you start a volume restore session to DUA10C               then accidentally continue it to DUA8, which contains E               a Spiralog volume that is not currently mounted on your                computer:D  @               $ SPIRALOG RESTORE VOLUME MUA1:USERS_WED.SSP DUA10K               %SPIRAL-I-SSPROCESSED, processed savesnap MUA1:USERS_WED.SSP; D               %SPIRAL-S-CONTRESTORE, restore session is not finishedD               -SPIRAL-I-RESTNEXTSS, use SPIRALOG CONTINUE RESTORE to<               process the next savesnap, MUA1:USERS_TUE.SSP;  .               $ SPIRALOG CONTINUE RESTORE DUA8=               %SPIRAL-S-RESTOREDONE, restore session finishedL  I                                                        Known Problems 4-3n h  o           Known Problems>     4.4 Volume Restore Sessions Do Not Check the Target Device    A           Although the SPIRALOG CONTINUE RESTORE command reported:A           that the session is now finished, it copied data to thetC           wrong device. The Spiralog volume on DUA8 is now corrupt.   -     4.5 Page and Swap Files Are Not Supported.  7           Spiralog does not support page or swap files.   A           Your system may hang if you put page or swap files on a            Spiralog volume.  6     4.6 Three GETDVI Item Codes Return the Null String  @           For a Spiralog volume, the following GETDVI item codes!           return the null string:                 LOGVOLNAM              MEDIA_NAMEv              MEDIA_TYPE   @           This affects the F$GETDVI lexical function, LIB$GETDVI9           library routine, and SYS$GETDVI system service.a  C           A corollary of this is that you cannot use the POLYCENTER,C           Software Installation utility to install a product onto aoC           Spiralog volume. This is not a problem for most products,d7           which must be installed onto the system disk.p  6     4.7 SYS$SEARCH Routine's RSL Field is Input/Output  D           When you use the RMS SYS$SEARCH routine to read a SpiralogD           directory, you must not modify the resultant string length           (RSL) field.  A           This field is an input/output field, not an output onlys6           field as described in the RMS documentation.  ;           If you modify this field when you read a SpiraloggC           directory, your program may loop doing a wildcard contextdE           scan. For example, it may repeatedly return the first entryV           in the directory.              4-4 Known Problems