User's Manual

hp StorageWorks File System Extender User Guide 99
The meaning of the columns is the following:
Running the media reorganization job
Using the fsemedium command, you can run the copying step of the reorganization process on all
medium volumes of a specific medium, on a single FSE medium volume, or on a series of specified FSE
medium volumes.
By default, the command reports the progress of the reorganization job to the command shell for
monitoring purposes. You can disable monitoring by specifying the --no-monitor option.
NOTE: To prevent the copying step of the FSE reorganization job from copying the data to the same
medium (that is, to the medium whose medium volumes are being reorganized), set the condition status of
the medium being reorganized to “unreliable” before running the reorganization job. Use the fsemedium
--mark-unreliable command for this purpose.
Note that FSE media with the condition status “unreliable” are not available for migrations. After the
reorganization job has finished, and the reorganized medium volumes have been reinitialized, you must
remove the “unreliable” status of the reorganized medium using the fsemedium --mark-good
command.
The following is the syntax of the fsemedium command when used for media reorganization:
With monitoring enabled, the command generates an output similar to the following:
Med003 5 0 1000 100%
Med004 5 100 1000 90%
VolNum
Number of the FSE medium volumes on the medium.
ValidData
Amount of space on the FSE medium occupied by valid file generations.
If the FSE medium has not yet been scanned for reorganization, it has 0 (zero)
displayed in place of the ValidData amount.
Total
Total amount of space on the FSE medium.
SlackSpace
Percentage of FSE slack space.
FSE slack space is the space on the medium occupied by migrated file generations
that were considered obsolete by the reorganizational scan job.
fsemedium --reorg Barcode [{-V | --volume} VolumeNumber...]
[--no-monitor]
[11:42:09] Started (JobID: 20050121000002).
[11:42:09] Requesting resources...
[11:42:09] Resources allocated.
[11:42:09] Medium 050003 is already present in drive drv1.
[11:42:09] Starting Back End Agent.
[11:42:09] Medium 050003, volume 1: Reading valid files…
[12:20:58] Medium 050003, volume 1: Valid files written to disk buffer.
[12:20:58] Requesting resources...
[12:20:59] Medium 050003, volume 2: Reading valid files…
[12:47:12] Resources allocated.
[12:47:12] Loading medium 050010 to drive drv2.
[12:47:49] Starting Back End Agent.
[12:47:49] Medium 050010, volume 5: Writing…
[12:49:58] Medium 050003, volume 2: Valid files written to disk buffer.