From owner-freebsd-current@FreeBSD.ORG Mon Aug 2 06:38:53 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 D893C16A4CE for ; Mon, 2 Aug 2004 06:38:53 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8059A43D31 for ; Mon, 2 Aug 2004 06:38:53 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id CC73AACAF4; Mon, 2 Aug 2004 08:38:51 +0200 (CEST) Date: Mon, 2 Aug 2004 08:38:51 +0200 From: Pawel Jakub Dawidek To: Sam Lawrance Message-ID: <20040802063851.GL39839@darkness.comp.waw.pl> References: <1091411071.922.20.camel@dirk.no.domain> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DXIF1lRUlMsbZ3S1" Content-Disposition: inline In-Reply-To: <1091411071.922.20.camel@dirk.no.domain> User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 cc: freebsd-current@freebsd.org Subject: Re: processes freezing when writing to gstripe'd device 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: Mon, 02 Aug 2004 06:38:54 -0000 --DXIF1lRUlMsbZ3S1 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 02, 2004 at 11:44:31AM +1000, Sam Lawrance wrote: +> I'm running current from around the 24th of July. About to build world +> to see if it makes any difference. +>=20 +> I am observing processes performing operations on a gstripe device +> freeze in state 'bufwait'. An 'rm' process is stuck right now. The rest +> of the system is fine. +>=20 +> The devices are two vnode backed md devices which I created just for +> testing. The same thing occurred using two freebsd partitions of size +> 15G each (not slices). +>=20 +> NAME: test_cd.stripe +> geom name: test_cd.stripe +> mediasize: 10231808 (9.8M) +> sectorsize: 512 +> mode: r1w1e0 +> state: UP +> status: total=3D2, online=3D2 +> providers: md3 md2 +> type: automatic +> stripesize: 4096 +> id: 1411913070 +>=20 +> What's the best way to look in to this? I can't attach to rm with gdb +> (it just ends up waiting for something). I can drop to kdb, but have no +> idea where to go from there. You could use 'ps' command from DDB to which processes are alseep. Then you can run 'tr ' where is PID of sleeping process. Look for processes related somehow to this problem. It'll be also great if you can provide exact procedure which will also me to reproduce this problem. PS. If you plan to upgrade your machine, remember than naming has changed in gstripe from /dev/.stripe to /dev/stripe/. --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --DXIF1lRUlMsbZ3S1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBDeF7ForvXbEpPzQRAnUYAKC1H/RcI9S181k0nrrpXQpw3r2jeACgr9cp BOitsqE6VROoPaZ9ErveHvE= =5YrC -----END PGP SIGNATURE----- --DXIF1lRUlMsbZ3S1--