Date: Mon, 05 Nov 2001 08:15:00 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Mark Santcroos <marks@ripe.net>, current@FreeBSD.ORG Subject: Re: patch #2 (was Re: buf_daemon() lockup) Message-ID: <33260.1004944500@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 04 Nov 2001 17:12:39 PST." <200111050112.fA51Cdc42844@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?33260.1004944500>