From owner-freebsd-current@FreeBSD.ORG Mon Aug 2 01:43:00 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 530F916A4CE; Mon, 2 Aug 2004 01:43:00 +0000 (GMT) Received: from bloodwood.hunterlink.net.au (smtp-local.hunterlink.net.au [203.12.144.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1889543D66; Mon, 2 Aug 2004 01:42:59 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: from [61.8.34.87] (ppp2257.dyn.pacific.net.au [61.8.34.87]) i721WZ9Q028505; Mon, 2 Aug 2004 11:32:36 +1000 From: Sam Lawrance To: Pawel Jakub Dawidek Content-Type: text/plain Message-Id: <1091411071.922.20.camel@dirk.no.domain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 02 Aug 2004 11:44:31 +1000 Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: 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 01:43:00 -0000 I'm running current from around the 24th of July. About to build world to see if it makes any difference. 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. 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). NAME: test_cd.stripe geom name: test_cd.stripe mediasize: 10231808 (9.8M) sectorsize: 512 mode: r1w1e0 state: UP status: total=2, online=2 providers: md3 md2 type: automatic stripesize: 4096 id: 1411913070 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.