From owner-freebsd-geom@FreeBSD.ORG Thu Jun 21 11:30:11 2007 Return-Path: X-Original-To: freebsd-geom@hub.freebsd.org Delivered-To: freebsd-geom@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B2D8216A421 for ; Thu, 21 Jun 2007 11:30:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 9CA8A13C4C6 for ; Thu, 21 Jun 2007 11:30:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l5LBUBQ8092463 for ; Thu, 21 Jun 2007 11:30:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l5LBUBP6092459; Thu, 21 Jun 2007 11:30:11 GMT (envelope-from gnats) Date: Thu, 21 Jun 2007 11:30:11 GMT Message-Id: <200706211130.l5LBUBP6092459@freefall.freebsd.org> To: freebsd-geom@FreeBSD.org From: Bernard Steiner Cc: Subject: Re: kern/113837: [geom] unable to access 1024 sector size storage X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bernard Steiner List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2007 11:30:11 -0000 The following reply was made to PR kern/113837; it has been noted by GNATS. From: Bernard Steiner To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/113837: [geom] unable to access 1024 sector size storage Date: Thu, 21 Jun 2007 12:32:43 +0200 (MET DST) [sorry I goofed up with send-pr; this is my first bug report...] No, it's not a geom issue. Same thing happens with geom disabled. Nothing to do with msdosfs, either. I have since tried the following: 1) booted into single user without any geom modules; same effect 2) dd with conv=noerror seems to deliver some data of some sort (though not sufficient for a valid file system) 3) reading 512, 1k, 2k, 4k off da3 fails. lseek() to 512, 1024, 1536, 2048 and *then* reading 512, 1k, 2k, 4k fails as well. Bernard