From owner-freebsd-current@FreeBSD.ORG Mon Aug 2 06:53:54 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 5931516A4CE for ; Mon, 2 Aug 2004 06:53:54 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 073FF43D55 for ; Mon, 2 Aug 2004 06:53:54 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id D7367ACAF4; Mon, 2 Aug 2004 08:53:52 +0200 (CEST) Date: Mon, 2 Aug 2004 08:53:52 +0200 From: Pawel Jakub Dawidek To: Sam Lawrance Message-ID: <20040802065352.GM39839@darkness.comp.waw.pl> References: <1091411071.922.20.camel@dirk.no.domain> <20040802063851.GL39839@darkness.comp.waw.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yklP1rR72f9kjNtc" Content-Disposition: inline In-Reply-To: <20040802063851.GL39839@darkness.comp.waw.pl> 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:53:54 -0000 --yklP1rR72f9kjNtc Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 02, 2004 at 08:38:51AM +0200, Pawel Jakub Dawidek wrote: +> +> 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. +>=20 +> 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. +>=20 +> It'll be also great if you can provide exact procedure which will also +> me to reproduce this problem. +>=20 +> PS. If you plan to upgrade your machine, remember than naming has changed +> in gstripe from /dev/.stripe to /dev/stripe/. One more note. I'm quite sure it is not related to gstripe, because its implementation is very simple: it doesn't use [mt]sleep(9) (so there is no missing wakeup()), it doesn't use any mutexes, so while debugging you may want also look at other components. --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --yklP1rR72f9kjNtc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBDeUAForvXbEpPzQRAvcpAJ9+/7pECUm41+mRPiUtLACkx2X0PQCcDWBR OvGGO3RwGTHR9XzINnhhUls= =5RFD -----END PGP SIGNATURE----- --yklP1rR72f9kjNtc--