From owner-freebsd-geom@FreeBSD.ORG  Fri Sep 24 21:47:08 2004
Return-Path: <owner-freebsd-geom@FreeBSD.ORG>
Delivered-To: freebsd-geom@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 21B6116A4CE; Fri, 24 Sep 2004 21:47:08 +0000 (GMT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 7280543D41; Fri, 24 Sep 2004 21:47:07 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id i8OLl65Y054597;
	Fri, 24 Sep 2004 23:47:06 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: Lukas Ertl <le@freebsd.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Fri, 24 Sep 2004 17:15:37 +0200."
             <20040924171245.Q549@pcle2.cc.univie.ac.at> 
Date: Fri, 24 Sep 2004 23:47:06 +0200
Message-ID: <54596.1096062426@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
cc: freebsd-geom@freebsd.org
Subject: Re: Outstanding I/O after 10 seconds 
X-BeenThere: freebsd-geom@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: GEOM-specific discussions and implementations
	<freebsd-geom.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-geom>,
	<mailto:freebsd-geom-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-geom>
List-Post: <mailto:freebsd-geom@freebsd.org>
List-Help: <mailto:freebsd-geom-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-geom>,
	<mailto:freebsd-geom-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2004 21:47:08 -0000

In message <20040924171245.Q549@pcle2.cc.univie.ac.at>, Lukas Ertl writes:
>Hi there,
>
>I've now seen several times the following messages:
>
>WARNING: Final close of geom_dev(da9s1a) still has outstanding I/O after 
>10 seconds. Completing close anyway, panic may happen later.
>
>This happens when I run benchmarks on the specified device (like rawio). 
>The strange thing is that when I look at what triggers this message, then 
>cp->nstart is one less than cp->nend, like there was an additional 
>g_io_deliver() on a bio.
>
>Any ideas why cp->nend would be larger than cp->nstart?

A bug.  A very serious bug.  Likely a double biodone().

-- 
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.