From owner-freebsd-current@FreeBSD.ORG Thu Oct 14 05:21:02 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 4814616A4CE; Thu, 14 Oct 2004 05:21:02 +0000 (GMT) Received: from mrynet.com (mrynet.com [63.231.249.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBA5A43D39; Thu, 14 Oct 2004 05:21:01 +0000 (GMT) (envelope-from staylor@mrynet.com) Received: from mrynet.com (staylor@localhost [127.0.0.1]) by mrynet.com (8.13.1/8.13.1) with ESMTP id i9E5L0JJ001097; Thu, 14 Oct 2004 00:21:01 -0500 (CDT) (envelope-from staylor@mrynet.com) Received: (from staylor@localhost) by mrynet.com (8.13.1/8.13.1/Submit) id i9E5L06d001096; Thu, 14 Oct 2004 00:21:00 -0500 (CDT) (envelope-from staylor) Message-Id: <200410140521.i9E5L06d001096@mrynet.com> From: staylor@mrynet.com (User Staylor) Date: Thu, 14 Oct 2004 00:21:00 -0500 X-Mailer: Mail User's Shell (7.2.6 beta(5) jp(8) 11/23/00) To: freebsd-current@freebsd.org, freebsd-geom@freebsd.org X-Mailman-Approved-At: Thu, 14 Oct 2004 12:10:41 +0000 Subject: GEOM will panic 6.0-current on userland wrong-length disk reads 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: Thu, 14 Oct 2004 05:21:02 -0000 Just discovered (and verified with latest build on current.freebsd.org) that the following will panic the new GEOM fdc driver in 6.0-current: # dd if=/dev/fd0 bs=55 panic: wrong length 55 for sectorsize 512 And further checking, discovered that ALL disk devices will cause a panic: dd if=/dev/ad0 bs=1234 panic: wrong length 1234 for sectorsize 512 Perhaps this is geom's way of complaining? Seems a rather radical way to handle non-matching-blocksize reads of disk devices. A simple programming error reading a disk dev node will panic the machine. -scott