Date: Thu, 26 Apr 2007 02:01:57 +0100 From: Adrian Wontroba <aw1@stade.co.uk> To: freebsd-stable@freebsd.org Subject: Re: 6.2-STABLE deadlock? Message-ID: <20070426010157.GF66129@steerpike.hanley.stade.co.uk> In-Reply-To: <20070423025631.GA33256@steerpike.hanley.stade.co.uk> References: <20070313140848.GA89182@steerpike.hanley.stade.co.uk> <20070423025631.GA33256@steerpike.hanley.stade.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 23, 2007 at 03:56:32AM +0100, Adrian Wontroba wrote: > Another 6-STABLE (cvsupped on 27/03/07) example, with diagnostics taken > rather sooner after the hang. Processes with wmesg=ufs feature often in > the ps output. Thanks for the assorted replies. I'll try using INVARIANTS, as I'd much prefer a panic and automatic reboot rather than creeping death for this server which is only attended 06:00-22:00 weekdays yet is a critical point in our 24*7 monitoring. Sigh. Champagne tastes on a beer budget. Other background information (from memory as I can't access it from here): I'm not using unionfs / nullfs. I am using MFS and softupdates. NFS is in occassional use. NTFS is not used. The server is ancient. A 4 way Zeon, state of the art in 1998. The problem has gone from "absent" through "reproducible if you try hard enough" to "strikes according to Murphy" through 5.5-STABLE to 6.2-STABLE. Once the sendmail milter ABI damage is fixed I'll bring the machine up to date - it is also the build box for a dozen or so machines running something close to 6.2-RELEASE, and I'd rather not upgrade all of them them when the next ClamAV release appears. If / when it hangs again, I'll include more information and maybe even raise a real PR. -- Adrian Wontroba It's always a long day; 86400 doesn't fit into a short.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070426010157.GF66129>