Last updated on JANUARY 29, 2015
Applies to:Sun QFS and Storage Archive Manager (SAM) - Version 5.4 and later
Information in this document applies to any platform.
Customer sees a problem problem when using the distributed I/O (distio) and attempting to stop the archiver on the server (MDS).
When the 'samcmd arstop' command is used on the MDS, it attempts to stop the archiver and kills all the current archive processes. However, distio doesn't appear to recognize this and continues processing it's current message. The archiver then tries to unload the tape that distio is using, times out, downs the drive involved and marks the tape being used by the datamover (distio) as 'unavailable'. At the same time distio completes it's current message and then stalls out waiting to send a reply back to the arcopy process, which has already been killed. The sam-datamover never reports in it's trace file that it's 'Closing device' and 'Destroying dm_thread', like it should. See log messages below seen on both the MDS and Shared client.
Log messages on MDS:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms