What does 'zdb -l /dev/dsk/<device>s0' show for each device?

- Eric

On Tue, Aug 21, 2007 at 04:45:40PM -0500, Jeff Bachtel wrote:
> On Tue, Aug 21, 2007 at 01:39:26PM -0700, Richard Elling wrote:
> > Jeff Bachtel wrote:
> > >On Tue, Aug 21, 2007 at 09:38:17AM -0700, Richard Elling wrote:
> > >>can you see the LUN in format?
> > >
> > >Yes. Additionally, I can dd from the rdsk device to a file, and get
> > >enough data to confirm that the disk devices are members of the old
> > >zpools, and still have data.
> > 
> > OK, I suspect the complaint is because ZFS sees the exact same ID
> > on both drives.
> 
> Which ID would that be, and which drives?
> 
> I've updated one of the systems to snv 72, and I'm still getting the
> "Create devinfo" warning, and the imports are still not going.
> 
> cfgadm seems, sane, a la:
> 
> imsfs-mirror:~> sudo cfgadm -la c2
> Ap_Id                          Type         Receptacle   Occupant Condition
> c2                             fc-fabric    connected    configured unknown
> c2::21000004d9600099           disk         connected    configured unknown
> c2::21000004d960cded           disk         connected    configured unknown
> 
> devinfo, once I figured out how to call it, also seems sane:
> imsfs-mirror:~> sudo devinfo -i /dev/rdsk/c2t21000004D960CDEDd7s2
> /dev/rdsk/c2t21000004D960CDEDd7s2       0       0       32130   512
> 2
> imsfs-mirror:~> sudo devinfo -p /dev/rdsk/c2t21000004D960CDEDd7s2
> /dev/rdsk/c2t21000004D960CDEDd7s2       36      682     0
> 1465031610      0       5
> 
> As I mentioned, I can dd the raw device and get valid data (although
> I've no way to verify that ZFS metadata is at the beginning of the
> disks).
> 
> Is there a documented example of using DTrace to examine what zpool is
> seeing/discarding while it scans for pools? One of these ZFS pools had
> its members totally renamed (the port used on the disk array got
> switched, and so the WWN changed), but the other should still be the
> same.
> 
> I'm close to downgrading to snv_69 on one of the machines to see if it
> can import the pools, but after doing some research it seems that
> other people have had mysterious import problems that never resolved.
> 
> (Richard, I'm sending this back to zfs-discuss, but only because I
> added more debug info that might mean something to someone else.)
> 
> Jeff
> 
> 
> >  -- richard
> 
> -- 
> Jeff Bachtel  ([EMAIL PROTECTED],TAMU)     http://www.cepheid.org/~jeff
> "The sciences, each straining in  [finger [EMAIL PROTECTED] for PGP key]
> its own direction, have hitherto harmed us little;" - HPL, TCoC
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

--
Eric Schrock, Solaris Kernel Development       http://blogs.sun.com/eschrock
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to