Re: URGENT: [diagnostic] cache_lock: blocked on 0xda5265a8 ""

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:Hi,
:What's meant to be between the "" ?
:
:I got 2 of those on one of our production mail server
:
:[diagnostic] cache_lock: blocked on 0xda5265a8 ""
:[diagnostic] cache_lock: blocked on 0xda5265a8 ""

    "" will usually be the root of a mount point.

:It seems to happen always after a few weeks of problemless operation.
:
:I suspected hard drive fault, even though there shouldnt be a problem
:because its running in hardware raid mode 1.

     It does sound like a fault in the disk driver or disk.  'dmesg' output
     after the processes are observed to start locking up may also help
     diagnose the problem.  'ps axl' may also help (so we can see what
     the processes are stuck in).

     To really debug the problem you need to generate a kernel panic and
     kernel core so we can track down where the problem occured.  This is
     usually accomplished by dropping it into the debugger and manually
     panicing the system.  swap has to be at least as large as main memory
     and dumpdev has to be set in /etc/rc.conf.  e.g:

     dumpdev="/dev/ad0s1b"

     'dumpdev /dev/ad0s1b' (or whatever the appropriate disk device is)
     can be run manually to set the dumpdev if you don't intend to reboot
     after making the rc.conf change.

						-Matt