Troubleshooting Managed Volumes
Finding NFS-Only Entries in a Multi-Protocol Volume
8-62
CLI Maintenance Guide
A directory with any FGN-patterned names introduces the opposite problem: a new
NFS-only entry can create a back-end FGN that collides with an existing entry. In this
case, the pre-existing entry with the FGN-patterned name becomes “NFS-only.” For
example, if “MYFILE~1” already exists in a directory and a client creates “myFile?,”
the volume must probe the back-end shares to see if any of them created a
“MYFILE~1” FGN. If the FGN is found, the original “MYFILE~1” entry becomes
“NFS-only.”
Evidence from the field demonstrates that these collision checks are rarely necessary,
though they do affect performance when they occur.
The policy engine is subject to this collision check like any external client.
Identifying All NFS-Only Entries
If CIFS clients complain about access issues or slow performance, you should
identify the NFS-only entries in the volume and work toward changing their names.
This is especially true for directory names, which can obscure multiple files and
directories from CIFS users. Run an nsck-inconsistencies report with the
multi-protocol
flag (recall
“Focusing on Multi-Protocol Issues” on page 5-16
) to reveal
all NFS-only filenames and directory names. Each of them is flagged with an “NF.”
For example, this command sequence generates and shows an inconsistencies report
for the “insur” namespace, which reveals several NFS-only files and directories:
bstnA6k#
nsck insur report inconsistencies multi-protocol outputfile insur_fgns
bstnA6k#
show reports insur_fgns._claims.rpt
bstnA6k# show reports insur_fgns._claims.rpt
**** Inconsistencies Report: Started at Fri May 11 03:53:43 2007 ****
**** Software Version: 2.05.001.10153 (May 9 2007 17:40:54) [nbuilds]
**** Hardware Platform: ARX-6000
**** Namespace: insur
**** Volume: /claims
**** Path: /claims
**** multiprotocol flag specified
Share Physical Filer
-------------------- ----------------------------------------------------------
[shr1-old ] 192.168.25.21 NFS:/vol/vol1/NTFS-QTREE/insurance, CIFS:insurance
[shr1-next ] 192.168.25.51NFS:/root_vdm_4/patient_records, CIFS:patient_records
**** Legend:
Summary of Contents for Adaptive Resource Switch
Page 12: ...2 xii CLI Maintenance Guide...
Page 62: ...Backing Up the Running Configuration Restoring the Configuration 3 24 CLI Maintenance Guide...
Page 128: ...Metadata Utilities nsck and sync Clearing All nsck Jobs 5 48 CLI Maintenance Guide...
Page 206: ...Troubleshooting Network Connections Configuring Port Mirroring 7 32 CLI Maintenance Guide...
Page 306: ...GUI Maintenance Restarting the GUI 10 4 CLI Maintenance Guide...
Page 316: ...Powering Down the ARX Restoring Power 11 10 CLI Maintenance Guide...
Page 318: ...Copyright 2 CLI Maintenance Guide...
Page 324: ...Index 6 CLI Maintenance Guide...