From owner-freebsd-current Sun Nov 4 23:16: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 6EA0737B416 for ; Sun, 4 Nov 2001 23:15:58 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fA57F0q33262; Mon, 5 Nov 2001 08:15:00 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Mark Santcroos , current@FreeBSD.ORG Subject: Re: patch #2 (was Re: buf_daemon() lockup) In-Reply-To: Your message of "Sun, 04 Nov 2001 17:12:39 PST." <200111050112.fA51Cdc42844@apollo.backplane.com> Date: Mon, 05 Nov 2001 08:15:00 +0100 Message-ID: <33260.1004944500@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200111050112.fA51Cdc42844@apollo.backplane.com>, Matthew Dillon wri tes: > >: >: 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 > > Ok. I think these unexpected md driver lock messages are bogus... I'll > leave it to Poul to remove it. The syncer or buf_daemon can be flushing > buffers associated with the underlying file simultaniously with other > processes doing MD ops. I actually just copied that part from your vn(4) driver, so by all means feel free to do what needs done to it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message