2013-06-13 06:24 AM
I have built a complete model of a new environment that I will be installing in 3 weeks on 8.2;however after a while the system gets loses the cluster and reports the information below. Has anyone experience this or have a solution in cleaning up the /mroot volume which is 100% full according to df command.
login as: admin
Using keyboard-interactive authentication.
** SYSTEM MESSAGES **
The root volume (/mroot) is dangerously low on space (<10MB). To make space
available, delete old Snapshot copies, delete unneeded files, and/or expand the
root volume's capacity. After enough space is made available, reboot this
controller. If needed, contact support personnel for assistance.
ausstor750-01::> cluster show <- lost the cluster
Error: "show" is not a recognized command
Solved! SEE THE SOLUTION
2013-06-13 07:23 AM
Hi Noe Ortiz,
Welcome to communities.
Error message says
To make space available, delete old Snapshot copies, delete unneeded files, and/or expand the root volume's capacity.
After enough space is made available, reboot this controller. If needed, contact support personnel for assistance.
you can enter the node level and delete the snapshots for vol0
Here are the commands
Enter node level -- node run local
snap list vol0
snap delete -a vol0
Are you sure you want to delete all snapshots for volume vol0? y
snap list vol0 (to verify that old snapshots are deleted.)
in addition to this you can increase the vol0 size
Add disk to aggrs (aggr0)
increase the volume size using vol size +100m vol0
Repeat these on all nodes which are complaining root-vol-dangerlously low
After you are done this on all nodes reboot the nodes
Hope this helps
2013-06-13 07:33 AM
cleaning up the snapshots did the trick. I had already added an additional disk, rebooted but things didn't change. I'm new to Netapp and didn't think to run "node run local". Thank you so much!
2013-06-13 09:59 AM
Welcome to Clustered Data Ontap 8.2.
Glad to know it worked for you.
You may want to turn on snapshot autodelete for vol0 ON or turn off snapshot schedule for vol0
snap sched vol0 0 0 0
This should avoid any future occurrence of /mroot filling up automatically.
2015-06-11 08:41 AM
Same in 8.3 simulator.
Root size is automatically choosen during setup...luckly I had some spare disk and I was able to elarge the root aggregate, then the volume.
Why they don't avoid the risk to loose the cluster (if no spare) with a more smart setup?