From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 13:42:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E165A16A4CE; Sun, 7 Mar 2004 13:42:21 -0800 (PST) Received: from crf-consulting.co.uk (82-44-220-218.cable.ubr10.haye.blueyonder.co.uk [82.44.220.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7346043D2D; Sun, 7 Mar 2004 13:42:20 -0800 (PST) (envelope-from nik@crf-consulting.co.uk) Received: from clan.nothing-going-on.org (clan.nothing-going-on.org [192.168.1.20])i27LgIIP015975; Sun, 7 Mar 2004 21:42:19 GMT (envelope-from nik@catkin) Received: from clan.nothing-going-on.org (localhost [127.0.0.1]) i27LgIMm087959; Sun, 7 Mar 2004 21:42:18 GMT (envelope-from nik@clan.nothing-going-on.org) Received: (from nik@localhost)i27LgIto087958; Sun, 7 Mar 2004 21:42:18 GMT (envelope-from nik) Date: Sun, 7 Mar 2004 21:42:18 +0000 From: Nik Clayton To: Nik Clayton Message-ID: <20040307214218.GA87623@clan.nothing-going-on.org> References: <22B16B3E-6D5F-11D8-BDE4-000393863D48@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9jxsPFA5p3P2qPhR" Content-Disposition: inline In-Reply-To: <22B16B3E-6D5F-11D8-BDE4-000393863D48@freebsd.org> User-Agent: Mutt/1.4.2.1i Organization: FreeBSD Project cc: current@freebsd.org Subject: Re: System hangs with vnode backed md(4) devices -- still a problem? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 21:42:22 -0000 --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 03, 2004 at 10:07:17PM +0000, Nik Clayton wrote: > Toward the end of last year, through to earlier this year, -current had = =20 > a problem with vnode backed md(4) devices. Specifically, >=20 > truncate -s 6G foo.md > mdconfig -a -t vnode -f foo.md -u 0 > newfs /dev/md0 > mount /dev/md0 /mnt > rsync /large/amount/of/data /mnt >=20 > would cause the rsync process to eventually get stuck in a wdrain =20 > state, and other processes in the system would gradually hang -- =20 > processes were still running, but doing anything that might need to =20 > read from a buffer caused the process to hang. Eventually, everything = =20 > would be hung. >=20 > If I'm reading the mailing lists right, this was supposed to be solved = =20 > here: > =20 > http://lists.freebsd.org/pipermail/freebsd-current/2003-November/=20 > 013183.html >=20 > However, I'm still seeing the problem in -current from Jan 14th. So =20 > I'm wondering if anyone else is seeing it, and if not, a rough idea of = =20 > when it was fixed. =20 Following some off-list suggestions, I can report that=20 mount -o sync /dev/md0 /mnt solves the "copying large amounts of data will hang" problem. However, it replaces it with an "unmounting the md0 device hangs" problem. N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Project http://www.freebsd.org/docproj/ \\\'',) \/ \= ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/= _) --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAS5c6k6gHZCw343URAuE0AKCQq2Sh25adm4KcIBqW9EVPl2O2AwCdFYyK 4EfviJVt74q3GxJ53EbXQD8= =xxdg -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR--