On Mon, Oct 09, 2006 at 11:08:14PM -0700, Matthew Ahrens wrote:
> Siegfried Nikolaivich wrote:
> >>zdb -l /dev/dsk/c0t1d0
> >
> >Sorry for posting again, but I think you might have meant
> >/dev/dsk/c0t1d0s0 there. The only difference between the following
> >outputs is the guid for each device.
>
Siegfried Nikolaivich wrote:
zdb -l /dev/dsk/c0t1d0
Sorry for posting again, but I think you might have meant
/dev/dsk/c0t1d0s0 there. The only difference between the following
outputs is the guid for each device.
Yeah, good catch. So this means that it seems to be able to read the
label o
> zdb -l /dev/dsk/c0t1d0
Sorry for posting again, but I think you might have meant /dev/dsk/c0t1d0s0
there. The only difference between the following outputs is the guid for each
device.
# zdb -l /dev/dsk/c0t0d0s0
LABEL 0
--
> > zdb -v tank
Forgot to add "zdb: can't open tank: error 5" to the end of the output of that
command.
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zf
Thanks for the response Matthew.
> > I don't think it's a hardware issue because it
> seems to be still
> > working fine, and has been for months.
>
> "Working fine", except that you can't access your
> pool, right? :-)
Well the computer and disk controller work fine when I tried it in Linux wit
