Administrator Guide

• Powering down the NAS controllers
The le system might take a long time to clean the cache to storage either due to lot of data, or due to an
intermittent connection to the storage. During the powering down stage, the issue could be due to the OS
kernel hanging on the NAS controller or failing to sync its state to the local drive.
Workaround
• If the le system has stopped and if one of the NAS controllers is still up, you can physically power down
the NAS controller using the power button.
• If the le system has not stopped, you must let it continue stopping. The le system reaches a 10 minute
timeout, ushes its cache to local storage, and continues the shutdown process.
NAS Volume Security Violation
Description NAS volume security violation.
Cause Selecting a security style for a NAS volume dictates the dominant protocol to be used to set permissions on
les in the NAS volume: NFS for UNIX security style NAS volumes and SMB for NTFS security style NAS
volumes.
Consequently, this makes some operations invalid:
• Setting UNIX permissions for a le in an NTFS security style NAS volume.
• Setting UID/GID ownership for a le in an NTFS security style NAS volume.
• Setting an ACL for a le in a UNIX security style NAS volume.
• Changing the read-only ag for a le in a UNIX security style NAS volume.
• Setting SID/GSID ownership for a le in a UNIX security style NAS volume.
The NAS volume security style must reect the main protocol used to access its les.
Workaround If a user frequently needs to perform a cross-protocol security related activity, split the data into separate NAS
volumes based on the main access protocol.
Attach Operation Fails
Description
The operation to attach the NAS controller to the FluidFS cluster fails.
Workaround
• Connect a keyboard and monitor to the NAS controller that failed the attach operation, and view the error
message to determine why the attach operation failed.
• Verify that while the NAS controller was detached, the IP assigned to it on the client network was not
allocated to another host. While the NAS controller is detached, it loses its identity, including IP addresses.
When it is attached, its identity is applied back to the NAS controller, including the IP addresses.
• Verify that the default gateway is in the Primary subnet. If the default gateway is not in the Primary
subnet, change the default gateway. For attach to succeed, the default gateway must be able to be
pinged.
• After an attach operation fails, the NAS controller must manually be reset to standby mode.
Controller Taking Long Time to Boot Up After Service Pack Upgrade
Description
The NAS controller takes a long time to boot up after upgrading the service pack of the NAS controller
rmware.
Cause The upgrade process can take up to 60 minutes to complete.
Workaround
• Connect a keyboard and monitor to the NAS controller that is taking a long time to boot up.
• If the system is booting, and is at the boot phase, let the upgrades nish. This can take up to 60 minutes
to complete.
510 FluidFS Administration