Acopia Adaptive Resource Switch Cli Maintenance Manual page 245

Table 8-1. Share Status Conditions (Continued)
Status Condition
Error: Metadata filer configuration is
invalid. Data written has been lost,
corrupting the database.
Error: Metadata share unavailable
during import.
Error: Mismatched NFS filename
encoding.
Error: Mount to filer failed.
CLI Maintenance Guide
Description/Action
This is not an import error: it typically occurs while the volume
is providing service. This condition disables the volume.
Some of this share's metadata was lost at the volume's metadata
share. This indicates that the metadata share did not
synchronously write its data; it wrote the data to a cache, told the
ARX that the write succeeded, and then lost the data between the
cache and the disk. This is only possible on an NFS export
where either
• the "async" option was set, or
• "async" is the default for the NFS implementation (as with
some releases of Linux)
CIFS shares do not have this problem.
At the filer, set the "sync" option for the NFS export. We also
recommend that you specify the "no_wdelay" option.
Use
nsck ... rebuild volume
reimport all shares in the volume.
The switch could not contact the metadata share. Use the
command and/or
exports
metadata share's filer. The
that the share is accessible by root (for NFS shares) or the
namespace's
proxy-user (gbl-ns)
(multi-protocol) The NFS character-encoding setting for the
namespace does not match the character encoding supported at
the filer. If this share was imported, lost NFS files could result.
Reset the namespace character encoding (using the
command) and retry the import.
character-encoding
(NFS) The switch was unable to NFS-mount the filer share.
Check the NFS service at the back-end filer.
Troubleshooting Managed Volumes
Correcting Share-Import Errors
to re-initialize the metadata share and
to check the connection to the
ping
command also verifies
show export
(for CIFS shares).
show
8-39