I have a zfs pool on a USB hard drive attached to my system. I had unplugged it and when I reconnect it, zpool import does not see the pool. # cd /dev/dsk # fstyp c3t0d0s0 zfs When I truss zpool import, it looks everywhere (seemingly) *but* c3t0d0s0 for the pool... The relevant portion...> stat64("/dev/dsk/c3t0d0s1", 0x08043150) = 0 > open64("/dev/dsk/c3t0d0s1", O_RDONLY) Err#5 EIO > stat64("/dev/dsk/c1t0d0p3", 0x08043150) = 0 > open64("/dev/dsk/c1t0d0p3", O_RDONLY) Err#16 EBUSYThis is Nevada B49, BFUed to B50 and then BFUed to 10/9/2006 nightly. I have been seeing this behavior for a while so I don''t think it is the result of a very recent change... Thoughts? Jim Litchfield
> # fstyp c3t0d0s0 > zfss0? How is this disk labeled? From what I saw, when you put EFI label on a USB disk, the "whole disk" device is going to be d0 (without slice). What do these commands print: # fstyp /dev/dsk/c3t0d0 # fdisk -W /dev/rdsk/c3t0d0 # fdisk -W /dev/rdsk/c3t0d0p0 -Artem.
Artem Kachitchkine wrote:> >> # fstyp c3t0d0s0 >> zfs > > s0? How is this disk labeled? From what I saw, when you put EFI label > on a USB disk, the "whole disk" device is going to be d0 (without > slice). What do these commands print: > > # fstyp /dev/dsk/c3t0d0 >unknown_fstyp (no matches)> # fdisk -W - /dev/rdsk/c3t0d0 >/dev/rdsk/c3t0d0 default fdisk table Dimensions: 512 bytes/sector 63 sectors/track 255 tracks/cylinder 36483 cylinders [ eliding almost all the systid cruft ] * 238: EFI_PMBR * Id Act Bhead Bsect Bcyl Ehead Esect Ecyl Rsect Numsect 238 0 255 63 1023 255 63 1023 1 586114703> # fdisk -W /dev/rdsk/c3t0d0p0 >Same dimension info as above... * Id Act Bhead Bsect Bcyl Ehead Esect Ecyl Rsect Numsect 238 0 255 63 1023 255 63 1023 1 586114703> -Artem.