Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 4 Nov 2001 16:15:39 -0800 (PST)
From:      Matthew Dillon <dillon@apollo.backplane.com>
To:        Mark Santcroos <marks@ripe.net>, current@FreeBSD.ORG
Subject:   more on ... Re: buf_daemon() lockup
Message-ID:  <200111050015.fA50Fdk09561@apollo.backplane.com>
References:  <20011101092118.A434@laptop.6bone.nl> <200111042259.fA4MxSc93566@apollo.backplane.com> <200111050006.fA506f309535@apollo.backplane.com>

next in thread | previous in thread | raw e-mail | index | archive | help
    Hmm..  that last patch didn't do it.  I've noticed some errors on the
    console before the lockup:

unexpected md driver lock: 0xe1813900: type VREG, usecount 2, writecount 1, refcount 3871, flags (VOBJBUF)
        tag VT_UFS, ino 4, on dev da0s1h (13, 131079) lock type inode: EXCL (count 1) by pid 6

unexpected md driver lock: 0xe1813900: type VREG, usecount 1, writecount 1, refcount 3874, flags (VOBJBUF)
		tag VT_UFS, ino 4, on dev da0s1h (13, 131079) lock type inode: EXCL (count 1) by pid 6

    This occured both with and without my patch.  Perhaps it is responsible
    for the problem?  My 'cp -pr /boot /mnt' gets stuck in an inode lock
    and bufdaemon gets stuck in wdrain.

						-Matt


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111050015.fA50Fdk09561>