Dell PowerVault 725N (Rackmount NAS Appliance) - Manual (Page 69)

Table 8-4. Dell OpenManage Array Manager
Table 8-5. UNIX and Red Hat Linux
Table 8-6. Macintosh and AppleTalk
When I try to take a persistent image, a
critical error message states that the
snapshot could not be taken. ActiveArchive may still be deleting or restoring a volume or taking
another snapshot. Wait a few minutes for the previous
process to complete and then try
again.
In the event log or on the Status page, a
message states: An exception has
occurred. The data contains the
exception record.
This is a known issue. Ignore this message. The NAS system
is functioning normally.
After restoring a volume from a persistent
image, I cannot mount to a share on that
volume from a Linux client. During the restore, the volume is dismounted. From the NAS Manager, restart NFS,
and then remount to a share on the
volume.
The % symbol does not show in the
ActiveArchive event logs. ActiveArchive event log messages that tell you how full the cache file is
and how close the system is to the maximum allowed snapshots are
generated messages. These messages do not include the % symbol. Take no action. The NAS system is
functioning as designed.
Issue Possible cause Resolution
After repairing a volume in the NAS Manager, one or more disks
show as "missing" in Dell OpenManage™ Array Manager. The repair does not actually delete the disks,
although the disks are displayed as missing. Take no action. Your NAS system is
still operating correctly.
Issue Possible cause Resolution
I cannot access the
Terminal Services Advanced
Client through the NAS
Manager from my Red Hat
Linux client system using
the Netscape browser. The Terminal Services Advanced Client is not supported by the Red Hat Linux operating
system and does not work with the NAS Manager. Use a Windows client system to
manage the NAS system through
a Terminal Services Advanced
Client session.
While updating client
access to an NFS share, the
No Access option is
displayed, but the Root
option is not. Only the All Machines category options are displayed during this update. Add the appropriate clients, and
then select OK. After you have
added the client, navigate back
to the NFS tab for this share and
select the correct options for the
individual Client Machines.
Every time I try to obtain a
directory listing from an NFS
client on the root of a
system volume, I get an
error message, such as
Permission Denied
.
The problem you are experiencing involves a System Volume Information directory created
by Microsoft Index Server. The NFS service does not have access to this directory and
returns an error message to the client when trying to list its properties.
This issue only occurs when sharing the root of a drive letter.
Ignore this error. The System
Volume Information directory is
not used by NFS clients or your
system by default.
Sometimes I am unable to
delete folders that have
been used and that are
shared to an NFS client. This is a situation that occurs with NFS discretionary access lists (DACLs) and inheritance.
When the folder to be shared is created, the only access control entry (ACE) created by
default is Everyone with Full Control. When an NFS client creates a directory or a file in this
directory (mounted share), Services for UNIX (SFU) creates a new DACL that replaces the
inherited Everyone with Full Control ACE. This DACL contains an Everyone ACE with the
appropriate UNIX file creation access and may contain two other ACEs for the mapped user
and group. If this happens, the administrator of the Windows client cannot delete the file or
directory unless that administrator takes ownership through the Windows system and
changes the access. As the administrator, use a
Windows client system to take
ownership and change the
access to allow yourself to
delete the share folders.
When you delete the NFS share
folders, ensure that there are no
open file handles for the share.
If you are unsure, delete the
share, and then restart NFS.
When updating client
access to an NFS share, the
All Machines client group is
reset from the No Access
access type to Read-Write
access. The NAS Manager might reset the All Machines client group to Read-Write when there are
no clients that have read-only or read-write access. Add a client that has read-write
or read-only access, and then
set the All Machines client group
to No Access.
My NAS system is
experiencing low NFS
performance. NFS write-back cache is disabled. Enable NFS write-back cache to
improve performance. See
"Advanced Features" for more
information.
The BIG5, EUC-KR, EUC-TW,
GB2312-80, KSC5601, and
Shift-JIS character encoding
schemes for NFS shares
cannot be specified in the
NAS Manager. The NAS Manager user interface supports only EUC-JP and ANSI character encoding for NFS
shares. Access the NAS system's desktop
and modify the NFS share
properties of the folder directly.
The NFS client group All
Machines is reset to No
Access when another client
group is set with the same
access permissions and
root. Setting a client group to use the same permissions as All Machines causes All Machines to
be reset to No Access. Access the NAS system's desktop
and modify the NFS share
properties of the folder directly.
I am getting inconsistent
map definitions when I use
the NAS Manager and the
SFU MMC to create user
name maps. Modifications to user name maps are cached and may not take effect immediately. Use only one tool to administer
user name maps.
Issue Possible cause Resolution
I am getting event errors for Services for
Macintosh. Services for Macintosh are bound to the onboard network
interface controller (NIC) by default. If this NIC has been Bind the AppleTalk protocol to an enabled
NIC. See "AppleTalk Protocol Adapter