From owner-freebsd-arch@FreeBSD.ORG  Mon Sep 13 18:42:14 2004
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id DB62316A4CE
	for <freebsd-arch@freebsd.org>; Mon, 13 Sep 2004 18:42:14 +0000 (GMT)
Received: from athena.softcardsystems.com (mail.softcardsystems.com
	[12.34.136.114])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 75D9443D4C
	for <freebsd-arch@freebsd.org>; Mon, 13 Sep 2004 18:42:14 +0000 (GMT)
	(envelope-from sah@softcardsystems.com)
Received: from athena (athena [12.34.136.114])i8DJg2qu008185;
	Mon, 13 Sep 2004 14:42:02 -0500
Date: Mon, 13 Sep 2004 14:42:02 -0500 (EST)
From: Sam <sah@softcardsystems.com>
X-X-Sender: sah@athena
To: Scott Long <scottl@samsco.org>
In-Reply-To: <Pine.LNX.4.60.0409131401150.6275@athena>
Message-ID: <Pine.LNX.4.60.0409131434100.6275@athena>
References: <Pine.LNX.4.60.0409131202270.6275@athena>
	<4145D7E8.9040209@samsco.org>
	<Pine.LNX.4.60.0409131401150.6275@athena>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
cc: freebsd-arch@freebsd.org
Subject: Re: 4.x device failure?
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Sep 2004 18:42:15 -0000

> To recap, the AoE device is mounted and I unload the module.
> The unload procedure fails outstanding bufs for the device
> and waits for the device to be closed.  The close never comes.
> Umounting the filesystem fails because he tries to open the
> device, I see it's now gone, and return ENODEV.  "Device not configured"

I'm sorry, it's due to the strategy when i fail the buffer with
ENXIO (obviously).  Failing with EIO displays identical behaviour,
just a different error message.

Sam