From owner-freebsd-hackers Tue Oct 29 10: 2: 2 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F104537B401 for ; Tue, 29 Oct 2002 10:02:01 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A4EE43E77 for ; Tue, 29 Oct 2002 10:01:58 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id g9TI1mrF094803 for ; Tue, 29 Oct 2002 19:01:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer In-Reply-To: Your message of "Tue, 29 Oct 2002 18:47:24 +0100." <20021029184724.A1682@gicco.homeip.net> Date: Tue, 29 Oct 2002 19:01:48 +0100 Message-ID: <94802.1035914508@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20021029184724.A1682@gicco.homeip.net>, Hanspeter Roth writes: > On Oct 29 at 18:34, Poul-Henning Kamp spoke: > >> That's a slightly more involved issue because you would have to >> actually try to write to it before you find out that you can't. > >Isn't there a means to determine the state of the protection before >the mount is attempted? As far as I know there isn't. I'm not sure if it is a device driver (morituri te salutem!) or hardware issue. -- 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message