User's Manual

202 Troubleshooting
Description If you remove an FSE medium from its FSE media pool without physically removing it from an
FSE library, then add it to whichever FSE media pool, and finally start an FSE administrative job
to format the medium, the job seems to be blocked before formatting actually begins.
Explanation When an FSE administrative job commands the Resource Manager (RM) to allocate a
particular FSE medium, the RM cannot execute the allocation unless it knows the medium’s
physical location in the FSE library.
After an FSE medium is added to an FSE media pool, the FSE library where the medium is
located must be physically rescanned in order to record the medium’s location in the Resource
Management Database (RMDB). The formatting can start after the medium location information
is known.
Workaround Before starting to format the re-added FSE media, run the following command to physically
rescan the FSE library. The command will add location information for the re-added FSE media
into the RMDB:
fselibrary --update-inventory LibraryName --rescan
This also unblocks formatting jobs that have already started from waiting for the missing
location information, enabling them to allocate the re-added FSE media and continue with
execution.
Description LTO and disk FSE media pools can be incorrectly configured as media pools of the WORM type.
Explanation When configuring an LTO or disk FSE media pool (the MediaFamily variable), you can
specify WORM for the media pool type (the PoolType variable). The configuration will
succeed, although the LTO-WORM and disk-WORM media are not supported by the FSE
implementation.
Workaround None
Description Recreating Fast Recovery Information (FRI) on a closed but empty FSE disk medium volume
fails.
Explanation Closed FSE disk medium volumes which are empty are not handled correctly by the Back End
Agent.
Workaround Do not recreate FRI on empty closed FSE disk medium volumes.
Description If reorganization of an FSE medium volume fails for any reason, you cannot re-run the
reorganization job for the volume because the scanned indicator is removed from the
medium volume status.
Explanation n/a
Workaround Solve the problem that caused the FSE reorganization job to fail, and then run the command
fsepartition --reorg-scan to scan the appropriate FSE medium volumes again.