Table of Contents
Advertisement
Troubleshooting Managed Volumes
Finding NFS-Only Entries in a Multi-Protocol Volume
Type
-------------------------
...
[
NI NM
8-68
Non-Mappable File Names
For files, the volume uses the NFS-side FGN for the filename. If the FGN contains
any illegal CIFS characters (as they often do), the volume also creates a CIFS-side
AGN from that FGN. For example, consider a site that supports Latin1, a single-byte
character encoding, for its NFS clients. Suppose (before import) a CIFS user creates a
file with the following name:
file012bC
where C is a character that is not supported by the filer's NFS character encoding.
The filer may create an NFS-side FGN with no apparent relationship to the original
filename:
:I1A3410
The volume imports this file and uses the above name for its NFS clients. For its CIFS
clients, it creates the following AGN (since the colon character cannot be used in a
CIFS filename):
(!) 001__I1A3410
An NSCK inconsistencies report for the volume shows these files with an "NM" flag.
For example:
Share
--------------------
]
[shr1-old
The CIFS-side AGN is inaccessible, but an NFS user can change the NFS-side name
(":I1A3410" in the above example) to something that is legal and recognizable in both
protocols (for example, "file012").
Non-Mappable Directory Names
A directory may contain a large tree of subdirectories and files, so the import process
takes greater care in keeping it accessible and easily recognizable from both CIFS and
NFS. If the volume is allowed to modify its imported shares and rename directories in
the particular share, it renames the directory based on its CIFS name. The import for
the share fails if the volume is not allowed to both modify and rename directories; this
is discussed in
"Preventing Directory Renames During Import" on page 9-31
CLI Storage-Management
Path
-------------------------------
]
/images/file012b/ (Characters: U+012b)
Guide.
of the
CLI Maintenance Guide
Advertisement
Table of Contents
Troubleshooting
