On Wed, 19 Jul 2006, Kostik Belousov wrote:
You did not provided the output of "show lockedbufs",
Added to my debug list ...
but, even without that data, I doubt that the buf subsystem deadlocked by
itself.
I make an conjecture that the problem is either with you disk hardware (i.e.,
actual hard drive or disk controller), or in the controller driver.
The problem that I have with this theory is that it isn't just one server
doing this, or one type of hardware ... all three of the servers that I've
upgraded to FreeBSD 6.x are doing it at some point or another ... I'm just
getting jupiter (older Dual-PIII server) rebooted now :(
Also note that under FreeBSD 4.x, all three of these machines were pretty
much my more solid machines, with even more vServers running on them then
I'm able to run with 6.x ... once I got rid of using unionfs, stability
skyrocketed :(
Hrmmmm ... but, your 'controller driver' comment ... that is one common
thing amongst all three servers ... they are all running the iir driver
... not sure the *exact* controller, but pluto (older Dual-PIII) shows it
as:
iir0: <Intel Integrated RAID Controller> mem 0xfc8f0000-0xfc8f3fff irq 30 at
device 9.0 on pci1
iir0: [GIANT-LOCKED]
Beyond that controller, jupiter/pluto are Dual-PIII with 36G Seagate
drives, uranus is a Dual-Xeon with 72G Seagate drives ...
At least, you could show us the dmesg.
I'll have to get that for you after next reboot, as /var/run/dmesg.boot
shows:
uranus# less /var/run/dmesg.boot
WARNING: /tmp was not properly dismounted
WARNING: /usr was not properly dismounted
WARNING: /var was not properly dismounted
And that's it :(
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED]
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
