From owner-freebsd-geom@FreeBSD.ORG Fri Aug 17 22:10:07 2007 Return-Path: Delivered-To: freebsd-geom@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CF1716A417 for ; Fri, 17 Aug 2007 22:10:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2346313C480 for ; Fri, 17 Aug 2007 22:10:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l7HMA6bm059638 for ; Fri, 17 Aug 2007 22:10:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7HMA6QS059637; Fri, 17 Aug 2007 22:10:06 GMT (envelope-from gnats) Date: Fri, 17 Aug 2007 22:10:06 GMT Message-Id: <200708172210.l7HMA6QS059637@freefall.freebsd.org> To: freebsd-geom@FreeBSD.org From: linimon@lonesome.com (Mark Linimon) Cc: Subject: Re: kern/115572: [gbde] gbde partitions fail at 28bit/48bit LBA addressing boundary X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Linimon List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Aug 2007 22:10:07 -0000 The following reply was made to PR kern/115572; it has been noted by GNATS. From: linimon@lonesome.com (Mark Linimon) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/115572: [gbde] gbde partitions fail at 28bit/48bit LBA addressing boundary Date: Fri, 17 Aug 2007 17:07:23 -0500 ----- Forwarded message from Graham ----- Sorry, but my only solution at the moment is to use geli ! We should not guess at the cause, I know, but I am writing chunks in succession to a newly gbde initialised drive, checking access after each shot, with the intent of narrowing down to the specific write which causes the damage --- i.e. the next read and write at the 28/48 boundary fails. This may take a little time, but I'd like to find a small specific write block address which does the damage. It will then be easier (with a specific case) to work through the block address mapping which ghappens in gbde. Then maybe a fix....hope this strategy is ok. On an optimistic note --- if we can pin this down, it may help explain some of the other gbde corruption cases in the bug list. I will keep you posted as soon as I can find a small, specific case which causes the problem. regards Graham ----- End forwarded message -----