From owner-freebsd-geom@FreeBSD.ORG Fri Mar 25 05:26:08 2005 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 00AFA16A4CE; Fri, 25 Mar 2005 05:26:08 +0000 (GMT) Received: from mail.allbsd.org (vlsi00.si.noda.tus.ac.jp [133.31.130.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 360D043D3F; Fri, 25 Mar 2005 05:26:07 +0000 (GMT) (envelope-from hrs@FreeBSD.org) Received: from delta.allbsd.org (p11053-adsau14honb8-acca.tokyo.ocn.ne.jp [220.106.47.53]) (authenticated bits=128) by mail.allbsd.org (8.13.1/8.13.1) with ESMTP id j2P5Q3N7059966; Fri, 25 Mar 2005 14:26:05 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (alph.allbsd.org [192.168.0.10]) by delta.allbsd.org (8.13.1/8.13.1) with ESMTP id j2P5PojK089176; Fri, 25 Mar 2005 14:25:51 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Fri, 25 Mar 2005 14:25:33 +0900 (JST) Message-Id: <20050325.142533.35104027.hrs@allbsd.org> To: pjd@FreeBSD.org From: Hiroki Sato In-Reply-To: <20050324135602.GZ591@darkness.comp.waw.pl> References: <20050324082319.GU591@darkness.comp.waw.pl> <20050324.183055.74659435.hrs@allbsd.org> <20050324135602.GZ591@darkness.comp.waw.pl> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Fri_Mar_25_14_25_33_2005_879)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.83/782/Thu Mar 24 21:29:35 2005 on gatekeeper.allbsd.org X-Virus-Status: Clean cc: freebsd-geom@FreeBSD.org Subject: Re: strange error of GEOM_RAID3 on RELENG_5 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: Fri, 25 Mar 2005 05:26:08 -0000 ----Security_Multipart(Fri_Mar_25_14_25_33_2005_879)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Pawel Jakub Dawidek wrote in <20050324135602.GZ591@darkness.comp.waw.pl>: pj> This is very strange and I've no idea why you get EPERM from ad[246]s1a. Ah, I found a simple use of dd failed. Sorry for the false alarm... I used a disklabel like this: a: 100g * 4.2BSD c: * * unused When the offset of /dev/ad2s1a is 0, "dd if=/dev/zero of=/dev/ad2s1a bs=512 count=1" works fine but "dd if=/dev/zero of=/dev/ad2s1a bs=512 count=2" fails (count > 2 or bs!=512 also occurs EPERM with whatever skip= value). When the offset is set to >2, dd works as expected. The second sector seems to contain the disklabel information and "disklabel -w /dev/ad2s1a auto" generates an offset of 16 for a: partition. Is using an offset of 0 wrong? I assumed that the offset can be 0 and /dev/ad2s1a does not (effectively) overlap with the disklabel area and so on, but am I mistaken about it? And if the offset is necessary, I still do not understand why "dd if=/dev/zero of=/dev/ad2s1a bs=512 count=2 skip=1000" fails. -- | Hiroki SATO ----Security_Multipart(Fri_Mar_25_14_25_33_2005_879)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD4DBQBCQ6DNTyzT2CeTzy0RApjwAJivZ8/aU2TEUjWIPZoXvoSd3bHnAKCB4htT sHfHqrEYU1gsDvtoeNELHg== =DMHT -----END PGP SIGNATURE----- ----Security_Multipart(Fri_Mar_25_14_25_33_2005_879)----