Simulator Discussions

Simulator ONTAP 8.3 - Root Volume Space Problem

rbrinson
40,329 Views

I have installed two instances of the ESX version of the 8.3 Simulator and within a few days I run into space problems on the root volume.  See the messages below from the console.  I have also runto into this same problem with instances installed in ESX in a Partner's lab.  It appears that there are logs or some other file(s) that are continually being created and filling up the root volume.  The Partner dug a little deeper and reports that it looks like the Simulator is buitl on a Linux image and that it is the Linux image that is actually having a space problem. 

 

CONSOLE OUTPUT:

login as: admin
Using keyboard-interactive authentication.
Password:
***********************
**  SYSTEM MESSAGES  **
***********************

CRITICAL: This node is not healthy because the root volume is low on space
(<10MB). The node can still serve data, but it cannot participate in cluster
operations until this situation is rectified. Free space using the nodeshell or
contact technical support for assistance.


cdot83::>

 

VM Characteristics:  See Attachment.

1 ACCEPTED SOLUTION

shatfield
39,976 Views

And here's the quick&dirty node shell variant:

 

From the problem node's console:

  1. login to the cluster shell
  2. run local
  3. disk assign all
  4. aggr status
    The root aggr will have "root" in the option list. Typically its aggr0
  5. aggr add aggregate_name 3@1g
    Assuming the default 1gb disks were used.  Adjust as necessary.
  6. vol status
    The root vol will have "root" in the options list.  typically its vol0
  7. vol size root_volume +2290m
    The size increase availble may vary depending on the type of disks used.  2560m or 2290m are most common.  Try 2560 first, if that fails fall back to 2290, if that fails the error will give the max size in kb
  8. exit
  9. reboot

You may or may not need a second reboot to remove the recovery flag in the loader.  If required it will tell you when you log in from the node shell.

 

After a clean reboot, go back and disable aggr snaps and vol snaps on the root, delete any existing snaps, and clean out old logs and asup files in the mroot.

 

 

View solution in original post

23 REPLIES 23

SeanHatfield
6,255 Views

Try adding them from the node shell

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

AVAZQUEZ79
21,180 Views

Thanks for the solution.  This did for me.  Remember to delete the snapshots on the vol0 first, or you will get the database error.  Merry Christmas!!

aborzenkov
29,622 Views
The point is to free some space to allow you to increase root volume size.
Public