Installation manual

Policy for Balancing Capacity
Draining One or More Shares
CLI Storage-Management Guide 12-45
Verifying That All Files Are Removed
You can use a metadata-only report to verify that the share is empty. Use the nsck ...
metadata-only
command to generate a report about the share (as described in
“Focusing on One Share” on page 5-10 of the CLI Maintenance Guide), and then use
show reports to view the report. For example, the following command sequence
generates a report on the “it5” share, proving that it has no files:
bstnA6k(gbl)# nsck wwmed report metadata-only share it5
Scheduling report: metadata_only.9.rpt on switch bstnA6k
bstnA6k(gbl)# show reports metadata_only.9.rpt
**** Metadata-Only Report: Started at Wed Sep 21 12:10:59 2005 ****
**** Namespace: wwmed
**** Volume: /acct
**** Path: /acct
**** Share: it5
Share Physical Filer
-------------------- ----------------------------------------------------------
[it5 ] 192.168.25.24:/lhome/it5
**** Legend:
**** FL = File: The reported entry is a file.
**** DR = Directory: The reported entry is a directory.
**** LN = Link: The reported entry has a link count greater than one.
**** NL = No Lock: Was unable to lock parent directory during report.
**** CC = NFS case-blind name collision.
**** IC = Name contains invalid CIFS characters.
**** FN = Name appears to be filer-generated.
**** NM = Name contains characters that are not mappable to the NFS encoding.
**** SP = A persistent case collision split is registered in the metadata.
**** SN = A persistent split restricts CIFS access, but no collision exists.
Type Share Path
------------- -------------------- ------------------------------------------
[ DR ] [it5 ] /multiTier
[ DR ] [it5 ] /loadBalance