Administrator Guide

Troubleshoot System Issues
This section contains probable causes of and solutions to common system problems.
NAS System Time Is Wrong
Description Scheduled tasks are running at the wrong times. The date and time of Event Log messages is wrong.
Cause
● The time on the FluidFS cluster is incorrect.
● No NTP server is defined for the FluidFS cluster.
● The NTP server servicing the FluidFS cluster is either down or has stopped providing NTP
services.
● There are network problems communicating with the NTP server.
Workaround 1. If you manually configured the NAS system clock, verify that the time is set correctly in Storage
Manager.
2. Identify the FluidFS cluster NTP server from Storage Manager. Record the host name(s) or IP
address(es) for further reference.
3. If no NTP server is defined, define one. It is recommended synchronizing the NAS system clock
with the NTP server used by the Active Directory domain controller. This avoids time difference
issues and possible authentication problems. In many cases the domain controller is also the NTP
server.
4. Verify that the NTP server is up and provides the NTP service.
5. Check the network path between the FluidFS cluster and the NTP server, using ping, for example.
Verify that the response time is in the millisecond range.
Troubleshooting System Shutdown
Description
During a system shutdown using Storage Manager, the system does not stop and the NAS controllers
do not shut down after 20 minutes.
Cause The system shutdown procedure is comprised of two separate processes:
● Stopping the file system
● Powering down the NAS controllers
The file 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 file 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 file system has not stopped, you must let it continue stopping. The file system reaches a 10
minute timeout, flushes 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 files 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 file in an NTFS security style NAS volume.
● Setting UID/GID ownership for a file in an NTFS security style NAS volume.
● Setting an ACL for a file in a UNIX security style NAS volume.
● Changing the read-only flag for a file in a UNIX security style NAS volume.
● Setting SID/GSID ownership for a file in a UNIX security style NAS volume.
The NAS volume security style must reflect the main protocol used to access its files.
FluidFS Administration 493