Okay - first post - be gentle.
FC720 old and unloved, has finally started having issues where it ceases to handle CIFS request correctly. The problem manifests as a failure to respond to client requests.
Two areas of possible "change" I think likely;
Linux client mounting the CIF partitons.
Wed Feb 16 11:57:57 GMT [de1]: CIFS t2 request 6 not implemented debuginfo( 15d 9e RH9CLIENT)
Or the Windows clients finally being stable enough to stay up long enough to exhaust some resource (good riddance to NT4).
In particular I'd be interested in seeing what the CIFS Session information looks like on other filers.
I see a lot of repeats.....
W2KIISSERV (WINDOMAIN\iusr_anon - pcuser) 10 0 W2KIISSERV (WINDOMAIN\iusr_anon - pcuser) 10 0 W2KIISSERV (WINDOMAIN\iusr_anon - pcuser) 10 0 W2KIISSERV (WINDOMAIN\iusr_anon - pcuser) 10 0 W2KIISSERV (WINDOMAIN\iusr_anon - pcuser) 10 0 W2KIISSERV (WINDOMAIN\iusr_anon - pcuser) 10 0 W2KIISSERV (WINDOMAIN\iusr_anon - pcuser) 10 0 W2KIISSERV (WINDOMAIN\iusr_anon - pcuser) 10 0 W2KIISSERV (WINDOMAIN\iusr_anon - pcuser) 10 0 W2KIISSERV (WINDOMAIN\iusr_anon - pcuser) 10 0 W2KIISSERV (WINDOMAIN\iusr_anon - pcuser) 10 91
... is that normal?
However I have no clear handle on what is going wrong.
The box just supplies CIFS service to a bunch of W2K webservers using IIS. The problem seems to manifest itself randomly, but does look like it is accumulating over time. Last time it managed 6 days. A reboot or restart of CIFS seems to clear it.
When it happens nothing unusual is logged.
The box is claiming to handle about 500,000 to 1,000,000 CIFS ops an hour. This doesn't seem to change much when the box fails?! All the status reports look normal. I guess it could be a networking issue, but it only affects the FC720, and is fixed by a reboot.
We are in the process of sourcing replacement hardware because is has basically reached the end of it's life. Till recently it "just worked", so no one touched it, and as a result has archaic firmware 2.3_a2.
If it was supported and with a future, I'd probably stick a firmware upgrade in straight away and see if this fixes it. But if anyone has any clues where to look, or what might be doing this....