Storage and Backups-Netapp
Troubleshooting Workflow: permission denied (export rules) mounting the export
Applies to
-
Clustered Data ONTAP 8
-
Troubleshooting
-
NFS
Issue
Failure during the mount of an export:
permission denied (export rules)
message is displayed.
There can be various causes for this issue. The causes and the procedures to be performed to resolve the issue are described in the Solution section below.
How to enter the filer's CIFS shares in the DFS root tree
Applies to
Description
Distributed File System for Microsoft Windows NT Server (DFS) allows distributed file systems capabilities on Windows NT Server. A distributed file system provides a single tree structure for multiple shared volumes located on different servers. A user accessing a share using DFS doesn't need to know the name of the server where the share resides.
If a file server goes down, or if you need to move a volume from one server to another, you can do so without informing users of the change. You can increase data availability and transparently distribute load across multiple servers by using duplicate storage points for a single volume.
SyncMirror could not create resynchronization snapshot (1045120)
Applies to
-
SyncMirror
-
FlashPool
-
MetroCluster
-
ONTAP 9.1 and earlier
-
SYNCMIRROR SNAPSHOTS NOT ROTATING autosupport message
Issue
There is no space left on aggregate with Flashpool (Hybrid Aggregates) configured.
Fri FebFri Feb 7 09:10:11 CET [systemname:raid.mirror.resync.snapcrtfail:warning]: Aggregate <aggr_name>: could not create mirror resynchronization snapshot mirror_resync. (No space left on device)
SyncMirror could not create resynchronization snapshot (SSD space)
Applies to
-
SyncMirror
-
FlashPool
-
MetroCluster
-
ONTAP 9.2 and later
-
SSD space lower than 1%
Issue
There is no space left on aggregate with Flashpool configured
Fri FebFri Feb 7 09:10:11 CET [systemname:raid.mirror.resync.snapcrtfail:warning]: Aggregate <aggr_name>: could not create mirror resynchronization snapshot mirror_resync. (No space left on device)
MetroCluster cluster name mismatch after changing cluster name
Applies to
-
ONTAP 9
-
MetroCluster
-
Cluster renamed
Issue
"metrocluster show" reports different peer cluster names
Cluster A Local: ClusterA Remote: cluster_oldB
Cluster B Local: ClusterB Remote: cluster_oldA
ClusterA::> metrocluster show
Configuration: fabric
Cluster Entry Name State
------------------------------ ---------------------- ---------------------
Local: ClusterA
Configuration State configured
Mode normal
AUSO Failure Domain auso-on-cluster-disaster
Remote: cluster_oldB
Configuration State configured
Mode normal
AUSO Failure Domain auso-on-cluster-disaster
ClusterA::> cluster peer show
Peer Cluster Name Cluster Serial Number Availability Authentication
------------------------- --------------------- -------------- --------------
ClusterB 1-80-000011 Available ok
Can a Volume ID be reused in Element Software?
Applies to
Element Software.
Answer
No. The Volume ID is uniquely generated for every volume that is created. Even if a volume is deleted, the number will always increment when a new volume is created based on the last Volume ID that was used.