Administrator Guide

Workaround Check whether the FluidFS cluster is down in the source system. If the FluidFS cluster is down, you must start
the le system on the source FluidFS cluster. The replication continues automatically when the le system
starts.
Replication Source is Not Optimal
Description Replication between the source and the target NAS volumes fails because the le system of the source NAS
volume is not optimal.
Cause Replication fails because the le system of the source is not optimal.
Workaround Check the le system status of the source system to understand why the le system is not optimal.
Replication Source Volume Is Busy Reclaiming Space
Description Replication between the source NAS volume and the target NAS volume fails because the source NAS volume
is busy reclaiming space.
Cause Replication failed because the source NAS volume is busy reclaiming space.
Workaround The replication continues automatically when space is available. Verify that the replication automatically
continues after a period of time (an hour).
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 dened 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 congured 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 dened, dene one. It is recommended synchronizing the NAS system clock with the
NTP server used by the Active Directory domain controller. This avoids time dierence 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 le system
FluidFS Administration 509