Filter
Top Products
Command Reference
2-112 Command Reference 601356 Rev A
If a list of media specified in a vsmount request contains media
of more than one type, the request fails.
When media or drive pairing requires the media be moved
within a single library system (such as cross-aisle) the mount
may take a while to complete. The -i and -u options do NOT
apply to intra-library system movement.
When a vsmount request with groups of media or drives is
submitted, VolServ attempts to select a drive or media pair
where the drive and media are associated with the same library.
If multiple drive or media pair are candidates, VolServ selects a
drive or media pair from the library with an available drive.
If no drive or media pair associated with the same library exists,
VolServ then selects a drive or media pair where the drive and
media are associated with a different library. If multiple drive or
media pair are candidates, VolServ selects a drive or media pair
from the library with the largest number of drives. If all libraries
contain the same number of drives, VolServ then selects a drive
or media pair from the library with the largest number of media.
When specifying a mount by MediaClass group, and the
specified MediaClass group is associated with more than one
library, no inter-library media or drive pairing is permitted. The
media selected from the MediaClass group must be in the same
library as the selected drive; otherwise the Mount request fails.
When media is ejected (as a result of Export, or Checkout, no
check is made to determine if a queued Mount request exists for
the ejected media. As a result, the Mount request remains
queued until a drive is freed. At that time, the Mount request
fails because the media is not available. In other words, the
request queue is not checked for impact on pending requests
each time a resource changes its availability and after media or
drive pair is identified. VolServ does not attempt re-pairing
based on changed availability of resources.