Date: Tue, 9 Jan 2007 15:06:25 +0100 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Fernan Aguero <fernan.aguero@gmail.com> Cc: geom@freebsd.org Subject: Re: clear metadata using dd? Message-ID: <20070109140625.GD62430@garage.freebsd.pl> In-Reply-To: <520894aa0701090524t217a36ecje1cf7b40d8a2a7e0@mail.gmail.com> References: <520894aa0701081445i43d76098m418ce695d2133e53@mail.gmail.com> <20070109001437.GC97624@in-addr.com> <520894aa0701081813x3925b7f1r278785bb01f4232@mail.gmail.com> <20070109083846.GA62430@garage.freebsd.pl> <520894aa0701090524t217a36ecje1cf7b40d8a2a7e0@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--8w3uRX/HFJGApMzv Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 09, 2007 at 10:24:04AM -0300, Fernan Aguero wrote: > On 1/9/07, Pawel Jakub Dawidek <pjd@freebsd.org> wrote: > >On Mon, Jan 08, 2007 at 11:13:15PM -0300, Fernan Aguero wrote: > >> On 1/8/07, Gary Palmer <gpalmer@freebsd.org> wrote: > >> >On Mon, Jan 08, 2007 at 07:45:06PM -0300, Fernan Aguero wrote: > >> > >> [snipped] > >> > >> >> gama# gstripe label -v gs0 /dev/ad4s3 /dev/ad6s3 > >> >> Can't store metadata on /dev/ad4s3: Operation not permitted. > >> >> > >> >> This might be because ad4s3 had been part of a gmirror device befor= e I > >> >> reorganized my disks and moved the mirror to the s2 slice. > >> > >> [snipped] > >> > >> >Any reason that "gstripe clear" or "gmirror clear" doesn't work? Tha= ts what > >> >they're meant to do, as far as I know. > >> > >> because ad4s3 is no longer part of gm0? > > > >You get "Operation not permitted." because someone already keep ad4s3 > >open for writing. Could you send output of 'sysctl -b kern.geom.confxml' > >so we can find out who? >=20 > http://omega.iib.unsam.edu.ar/kern.geom.confxml [...] In this output size of ad4 is 160041885696 bytes. In your first post, slices are configured this way: gama# fdisk -s /dev/ad4 /dev/ad4: 310101 cyl 16 hd 63 sec Part Start Size Type Flags 1: 63 16771041 0xa5 0x00 2: 16771923 146795229 0xa5 0x80 3: 146795292 188742708 0xa5 0x00 If ad4s3 starts at 146795292 sectors and is 188742708 sectors big, which bascially means, that ad4s3 end at offset: (146795292+188742708)*512 =3D 171795456000 bytes 160041885696 < 171795456000, which means your slices are misconfigured. Correct that and it should work. > And also, why does the GEOM config contain information for devices that a= re not > managed by geom? My da0 and swap devices (ad4s1b, ad6s1b) are not geom > based ... Every single storage provider in FreeBSD is managed by GEOM. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --8w3uRX/HFJGApMzv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFo6FhForvXbEpPzQRAqluAJ9Il3EKI6V2g4aEO8r2K3YA1LQ+mwCfcGEa ZJzEjje04GLrcgAkDfooJe8= =hSuM -----END PGP SIGNATURE----- --8w3uRX/HFJGApMzv--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070109140625.GD62430>