Before doing this procedure properly shutdown the VM and take a snapshot of it then make the changes. After adding disk to the simulator you need to increase the agg0 size by adding disk, next grow vol0 with the newly added capacity.
Before doing this procedure properly shutdown the VM and take a snapshot of it then make the changes. After adding disk to the simulator you need to increase the agg0 size by adding disk, next grow vol0 with the newly added capacity.
but for me, it is neither the snapshot nor the vol0 serving data. I just started with NetApp administration a few month ago, so I am still an beginner.
I am having a brand new Netapp Ontap 9.8 Sim downloaded on Feb. 18 2021. Running within VMWare Player on my win10 workstation.
Nevertheless, after starting and create the 2-node cluster, my sim continues to fill up the vol0. The first setup was full within 8 hours and broke the cluster entirely over night. This was repeating two times, because my daily business did not allows to spent much time on this. On my fourth try, I was at least able to add virtual disks and increase the vol0, disable and delete the aggr snapshots. Vol0 is still filling up, but now I have more time to delete. I did not even started to create a data aggr.
Thanks to some explanations here on how to clean up vol0 with diag mode, I found within /mroot/etc/log/mlog a lot of sktrace.log files. Even deleted, they are still expanding by 100mb per ~5 hours.
-rw-r--r-- 2 root wheel 12M Mar 2 13:54 sktrace.log -rw-r--r-- 1 root wheel 100M Feb 27 03:00 sktrace.log.0000000021 -rw-r--r-- 1 root wheel 100M Feb 27 09:02 sktrace.log.0000000022 -rw-r--r-- 1 root wheel 100M Feb 27 14:38 sktrace.log.0000000023 -rw-r--r-- 1 root wheel 18M Feb 27 15:42 sktrace.log.0000000024 -rw-r--r-- 1 root wheel 100M Feb 27 21:22 sktrace.log.0000000025 -rw-r--r-- 1 root wheel 100M Feb 28 02:17 sktrace.log.0000000026 -rw-r--r-- 1 root wheel 100M Feb 28 07:57 sktrace.log.0000000027 -rw-r--r-- 1 root wheel 100M Feb 28 13:22 sktrace.log.0000000028 -rw-r--r-- 1 root wheel 43M Feb 28 15:42 sktrace.log.0000000029 -rw-r--r-- 1 root wheel 100M Feb 28 20:56 sktrace.log.0000000030 -rw-r--r-- 1 root wheel 100M Mar 1 02:00 sktrace.log.0000000031 -rw-r--r-- 1 root wheel 100M Mar 1 06:51 sktrace.log.0000000032 -rw-r--r-- 1 root wheel 100M Mar 1 11:30 sktrace.log.0000000033 -rw-r--r-- 1 root wheel 84M Mar 1 15:42 sktrace.log.0000000034 -rw-r--r-- 1 root wheel 100M Mar 1 20:07 sktrace.log.0000000035 -rw-r--r-- 1 root wheel 100M Mar 2 00:23 sktrace.log.0000000036 -rw-r--r-- 1 root wheel 100M Mar 2 04:34 sktrace.log.0000000037 -rw-r--r-- 1 root wheel 100M Mar 2 09:17 sktrace.log.0000000038 -rw-r--r-- 1 root wheel 100M Mar 2 13:20 sktrace.log.0000000039
The logs contains stuff like this
sim20c10-02% tail sktrace.log (skipped the date and log number per entry)
Where can I disable this level of debug messages? Again, cluster is only utilized with itself. The is no data aggr, no cifs/nfs sharing, no export policy.
