On 07/12/99 23:47:14 you wrote:

My netapp running my news spool is dying with:

saving 192M to /etc/crash/core.7.nz ("../common/wafl/write_alloc.c:1412: Assertion failure.")

F630, 200GB disk, OnTap 5.3.1

Thinking of running wack... after idling it.

In my experience write_alloc.c crashes are often related to filesystem inconsistencies. Running wack sounds like a good idea.

So far, 7 days, 7 crashes. Haven't touched it in weeks, didn't even know it had died since it boots up so quick.

First, you should put yourself on its autosupport, that way it will notify you as soon as it reboots. You can even link it to your email pager if you like. Then you can either read the full email to see what happened or check the system messages logs.

As to the crashes, the fact there is 7 in 7 days would seem important, if indeed you are getting one every day. You don't say if they are all at the same time; if they are, then it might be indicative of a particular process running (cron job) at a particular time every day. Since it's a news spool, it is not unlikely that your entire filesystem gets scanned every day anyway, so even if they are at different times it could be a particular directory or file that is corrupted that crashes the filer ever time the news server tries to modify it.

Netapp support, as always, is the best place to get help when you have a crash.

Bruce