From owner-freebsd-geom@FreeBSD.ORG Tue May 27 16:58:26 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20ED31065681 for ; Tue, 27 May 2008 16:58:26 +0000 (UTC) (envelope-from marauder@pi.avalonnetworks.us) Received: from pi.avalonnetworks.us (pi.avalonnetworks.us [76.164.27.10]) by mx1.freebsd.org (Postfix) with ESMTP id CA4228FC17 for ; Tue, 27 May 2008 16:58:25 +0000 (UTC) (envelope-from marauder@pi.avalonnetworks.us) Received: from Project_Infinity-MTA by pi.avalonnetworks.us with Novell_GroupWise; Tue, 27 May 2008 10:58:10 -0600 Message-Id: <483BE93B.5689.0089.0@pi.avalonnetworks.us> X-Mailer: Novell GroupWise Internet Agent 7.0 Date: Tue, 27 May 2008 10:57:52 -0600 From: "Marauder" To: "Rick Petty" References: <48357420.5689.0089.0@pi.avalonnetworks.us> <20080527035650.GA68298@keira.kiwi-computer.com> In-Reply-To: <20080527035650.GA68298@keira.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: freebsd-geom@freebsd.org Subject: Re: Unable to write to drive X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2008 16:58:26 -0000 Actually I managed to fix this problem on Friday with the help of Sean = Bruno. The problem was the one you described bellow that Read's and writes = must be multiple's of 512. Thank you everybody for your help Binon >>> "Rick C. Petty" 5/26/2008 9:56 PM >>> On Thu, May 22, 2008 at 01:24:49PM -0600, Marauder wrote: >=20 > I have a problem that is driving me crazy. Hopefully I'm submitting this = question to the correct place.=20 >=20 > My problem is... I have opened the drive /dev/ad0 with open("/dev/ad0", = O_WRONLY) and it return's a valid file descriptor. The I attempt to write = using the file descriptor returned. The write fails with errno=3D22 = (EINVAL) What does your write instruction look like? I don't know if this still applies, but writes used to fail if not an integer multiple of 512 bytes = in length. > I have attempted to first open /dev/io with READ/WRITE access to see if = that help's. No luck I believe the io(4) device is used to directly access the I/O ports via = the assembly instructions IN, INS, OUT, OUTS, CLI, and STI. This device is = not used to gain privs on other devices. -- Rick C. Petty _______________________________________________ freebsd-geom@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom=20 To unsubscribe, send any mail to "freebsd-geom-unsubscribe@freebsd.org"