Date: Fri, 4 Oct 2002 19:09:12 +0100 From: n0go013 <ttz@blahdeblah.demon.co.uk> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: current <freebsd-current@freebsd.org>, not on list - please copy <hackers@freebsd.org> Subject: Re: [ GEOM tests ] vinum drives lost Message-ID: <20021004180912.GD10830@pooh.blahdeblah.demon.co.uk> In-Reply-To: <35389.1033748850@critter.freebsd.dk> References: <20021004161119.GA10830@pooh.blahdeblah.demon.co.uk> <35389.1033748850@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04.10-18:27, Poul-Henning Kamp wrote:
> In message n0go013 writes :
> >On 04.10-15:40, fergus wrote:
> > > On 04.10-14:20, Poul-Henning Kamp wrote:
> > > [...]
> > > > I suspect vinum uses this sysctl to get an inventory of disks in
> > > > the system, so can I get you to try again making sure you have
> > > > rev. 1.20 of src/sys/geom/geom_disk.c ?
> > [...]
> > > i'll let you know the test results when i have some.
> >
> > same results -- can't initialise any drives. i think the example below
> > points more directly to the issue but i'm pretty sure it is because the
> > direct read from the disk does not return a valid disklabel. without a
> > 'vinum' partition entry vinum spews.
>
> I have no idea how vinum does this or something else, but clearly
> something is not done the right way in vinum...
apparently by allocating a bio header via 'geteblk' and calling the
DEV_STRATEGY macro. not that it means anything to me but probably to
you it does (well i get the idea but . . .).
what is the correct way to read the disklabel ? i'll hack around and
see if i can't clean up this and the other pieces of direct IO.
--
t
t
z
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021004180912.GD10830>