I've been using an 8.1.1 2-node VSIM for several months. Every few weeks I am faced with vol0 filling up. I've shutdown snapshots on vol0, disabled autosupport and when it happens I go into /mroot/etc/log and delete rotated log files and /autosupport files. I'll note that the ASUP files keep getting generated even though I've disabled asup.
Has anyone else encountered this and come up with a better strategy to deal with the issue?
lab-stor::> autosupport show (autosupport) Node State From To Mail Hosts --------------------- --------- ------------- ------------- ----------
I have configured the cluster mode (ip-43) with 2 nodes (IP-44 & 45) successfully. i have provided one IP(50) for SVM and network interface IP is 51. I have successfully opened the share folder with IP-50 & 51 but when i try to open the share folder with cluster IP(43) or 2 nodes IPs (44 and 45) then it can not be opened. All IPs ping properly.
If you login as diag and check out the /mroot directory you will find that there are three areas where alot of capacity is concentrated. With "du -sk *" you can search for these areas. This involves the autosupport , mlog and stats directory. Removing older files here will free up space dramatically. 🙂
Yes, I've increased my vol0 and aggr0. I think I've got quadruple the space now (4 data disks in aggr0 instead of the deafult of 1). But I suspect I've just pushed out the time when vol0 will fill up again with log files. On a normal system that runs 24x7 I presume log file rotation logic kicks in (midnight?) and keeps things trimmed. On a laptop based simulator environment the laptop is probably in my bag at midnight. That's why I'm looking for ways to deal with the issue.