You might want to increase the size of vol0, this is where the Data OnTap operating system files are kept. The C$ and etc$ shares will open to directories on this volume.   The used space looks really low, what version of Data OnTap are you running? ... View more

Ok, it should be pointing to vol0, can you do a "vol status vol0" "df -g vol0" "qtree status vol0"? ... View more

Do you see anything on the vault logs about volume resize attempts? I had a look at the provisioning policy in use at my shop but there doesn't seem to be a setting to enable or disable resizing. ... View more

Do you have any spare disks? You can assign the not owned disks to one of the nodes to set as spares so the aggregates can try to reconstruct themselves. Do you have support with NetApp? One node looks like it is down as well, is there other hardware issues happening? ... View more

Can you check the CIFS shares on the filer to see where c$ and etc$ are pointing? ... View more

SnapProtect works with DFM to handle the provisioning / re-sizing of the vault targets. ... View more

Could you be more specific with the message? Are you referring to some errors from during a disk scrub? There are background tasks that frequently check the disks for any issues and will prefail the disk if there are serious issues. Pre-failing will trigger a copy to a spare and then the disk will be listed as broken and need to be replaced.   If you want further info, provide some of the outputs you are seeing. ... View more

You are using () in the volume name? trying using quotes around it in the cdot command - might be interpreting the () as regex. ... View more

What version of DOT are you running? can you run the disk show command on both nodes? ... View more

You could do "volume show -snapshot-policy <name of policy>" that would list the volumes using that policy and if no one is using it ... then no results. ... View more

Use "-f" with the igroup add command. ... View more

You should be able to force add the initiators, it doesn't like to add without talking to the partner in case there is duplication, but if you know cluster B doesn't have that initiator in use, then you can override.   Is Cluster B down completely? If you want to maintain HA, Cluster B will require a few disks to create an aggregate for a root volume (vol0). ... View more

On the client servers that are mounting the volumes, you can set the version to be used in the mount options. The currently mounted things will be using version 3 since version 4 isn't running on the filer. But if you don't explicitly set the version in /etc/fstab, the next client server reboot might start using version 4 if the client has version 4 capabilities. ... View more

Each version of the OS has a complete set of documents which can be found on the now support site under documentation. ... View more

Good point, RG size of 11 would be good, also leaves only 2 spares instead of 4 idle disks. ... View more

what version of DOT are you running? The maximum for SATA disks in a single raid group is typically 20, so that would leave 4 spares, with two for parity, leaves 18 x 2TB for data.   I would do one raid group of 20. ... View more

Can you show the output of some commands on the filer such as the igroup status and the FC HBA info from sysconfig? ... View more

There is typically one snapshot that is the baseline (snapvault locked) except when an update is happening and then you'll see two, the one being used for the update and the previous successful.   The two old snapshots are not typical. I've seen it with stale snapvault relationships, are you seeing similar snapshots from the same dates on those other volumes? Perhaps there was an issue with the vault around that time. Or, it could be that the number of weekly vault snapshots was changed - you have an active schedule of 7 daily snaps being created, if it was changed from 9 at one point, it might have not removed the two outliers properly. ... View more

What is the snapvault schedule now?   Either way, I think you can just remove those two old snapshots manually. ... View more

Can you check on both the source and destination filers? ... View more

Can you check the snapvault status to see if you have any stale relationships that are "locking" the snapshots? ... View more

can you do a "df -g" on the filer for the volume to see the usage that way? ... View more

Maybe check to see if there is an issue file created in the /etc of the node(s), "node run -node * rdfile /etc/issue" ... View more