On 14/07/2006 6:08 PM, User Freebsd wrote:
Just in case, do you use mlocked mappings ? Also, why so huge number
of crons exist in the system ? The are all forking now. It may be (can
not say definitely without further investigation) just a fork bomb.
re: crons ... this, I'm not sure of, but my suspicion was that the crons
weren't able to complete, since the file system was locked up, but the
next one was being attempted to run ... *shrug*
This seems consistent with behaviour I've seen in on several 6.0-RELEASE
machines.. from the limited information I've been able to get from the
machines, there has appeared to be multiple tasks from cron all piled up
upon one another. In particular, the daily periodic tasks that run the
various 'find' were one of the things I noticed (although we run
numerous tasks out of cron)...
If something is blocking the filesystem and causing find (and possibly
other processes) to become stuck, these would just keep mounting up
until it all falls over (with numerous maxproc exceeded etc errors).
These are on machines without NFS, but the symptoms are very very
similar.. NWFS and SMBFS are commonly used on a number of the machines
I've seen the problem on, which may be relevant -- perhaps it affects
more than just NFS?
I may experiment with building up a test server locally and trying to
reproduce similar loads to see if I can trigger the problem in-house..
at least that way I can hook up a serial console and get some more
detailed information...
Regards
Antony
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
