From owner-freebsd-geom@FreeBSD.ORG Thu Oct 7 13:56:44 2004 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 422FE16A4CE; Thu, 7 Oct 2004 13:56:44 +0000 (GMT) Received: from athena.softcardsystems.com (mail.softcardsystems.com [12.34.136.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDD5943D5F; Thu, 7 Oct 2004 13:56:43 +0000 (GMT) (envelope-from sah@softcardsystems.com) Received: from athena (athena [12.34.136.114])i97EtPKP025964; Thu, 7 Oct 2004 09:55:25 -0500 Date: Thu, 7 Oct 2004 09:55:25 -0500 (EST) From: Sam X-X-Sender: sah@athena To: John-Mark Gurney In-Reply-To: <20041007050405.GP22681@funkthat.com> Message-ID: References: <20041007050405.GP22681@funkthat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-geom@freebsd.org cc: freebsd-arch@freebsd.org Subject: Re: fdisk/geom, AoE 5.2.1 X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Oct 2004 13:56:44 -0000 > Sam wrote this message on Wed, Oct 06, 2004 at 23:34 -0500: >> I've got the AoE driver ported and running on >> 5.2.1. Much faster than I anticipated; the geom >> interface is delightful. >> >> I can read and write to the disk. I cannot, >> however, partition it and I'm soliciting the >> list for ideas as to why. >> >> If I fdisk -u an AoE device, fdisk claims all >> was successful, but in reality nothing gets written. >> Further calls to fdisk support this. >> >> I'm probably not tickling something right. Is it >> possible I need to grease the path for the disk >> partition table in geom? I didn't see anything of >> the like. Maybe it's a tasting issue? > > On last close (from fdisk hopefully), the provider will be passed > back for tasting since the meta data could possibly have changed.. > > Have you verified that the writes are hitting the disk? and that the > fdisk table can be seen from another machine? Verified that you can > read what you write to the disk? Arg. My goof. I wrote zeros, read zeros and assumed i could write to the disk. In fact I could - even when I wanted to read. I won't go into the details, but suffice it to say you can't do: if (bp->bio_flags & BIO_READ) // do read else // do write and expect the correct behaviour. :) Thanks - Sam