Has anyone noticed OnTAP 4.2a crashing when the WAFL filesystem uses up all available disk space or inodes? I was doing a series of ndmpcopies to several filers, with the intent to complete fill them to capacity with as many 2GB files as I could fit. One of the four filers crashed and rebooted early this morning:
Tue Nov 25 06:00:04 EST [statd]: 6:00am up 14:40 1362 NFS ops, 0 CIFS ops, 0 HTTP ops Tue Nov 25 07:00:03 EST [statd]: 7:00am up 15:40 1362 NFS ops, 0 CIFS ops, 0 HTTP ops Tue Nov 25 12:37:32 GMT [rc]: saving 59M to /etc/crash/core.0-small ("trap 13 code = 0 eip = 196aad cs = 8 eflags = 10246 ") Tue Nov 25 12:38:04 GMT [rc]: saving 258M to /etc/crash/core.0 ("trap 13 code = 0 eip = 196aad cs = 8 eflags = 10246 ") Tue Nov 25 12:38:41 GMT [wafl_lopri]: file system is full Tue Nov 25 12:38:41 GMT [rc]: (out of disk space?) Tue Nov 25 07:38:51 EST [rc]: relog syslog Tue Nov 25 07:00:03 EST [statd]: 7:00am up 15:40 1362 NFS ops, 0 CIFS ops, 0 HTTP ops Tue Nov 25 07:38:51 EST [rc]: NetApp Release 4.2a boot complete. Tue Nov 25 07:38:52 EST [asup_main]: System Notification mail sent
There wasn't enough room to save the large core file, but the small one appears to be intact. I saw something similar happen on a different filer when it ran out of inodes (unfortuately, I didn't save a copy of the panic message).
If the crashes are related to full filesystem conditions, I won't worry about it too much. Just curious. ;-)