Hi.
S10U2 Generic_118833-23 (SPARC)
LUNs provided by Symmetrix box.
# zpool create t2 raidz c7t5d176 c7t5d177 c7t5d178 c7t5d179 c7t5d180 c7t5d181
c7t5d182 c7t5d183 c7t5d184 c7t5d185 c7t5d186 c7t5d187 c7t5d188 c7t5d189 c7t5d190
invalid vdev specification
use '-f' to override the following errors:
raidz contains devices of different sizes
#
Just remove last one and try again:
# zpool create t2 raidz c7t5d176 c7t5d177 c7t5d178 c7t5d179 c7t5d180 c7t5d181
c7t5d182 c7t5d183 c7t5d184 c7t5d185 c7t5d186 c7t5d187 c7t5d188 c7t5d189
#
# zpool destroy t2
#
Hmm.. lets see if last two disks differ:
# prtvtoc /dev/rdsk/c7t5d189s0
* /dev/rdsk/c7t5d189s0 partition map
*
* Dimensions:
* 512 bytes/sector
* 17677440 sectors
* 17677373 accessible sectors
*
* Flags:
* 1: unmountable
* 10: read-only
*
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
0 4 00 34 17660989 17661022
8 11 00 17661023 16384 17677406
# prtvtoc /dev/rdsk/c7t5d190s0
* /dev/rdsk/c7t5d190s0 partition map
*
* Dimensions:
* 512 bytes/sector
* 17677440 sectors
* 17677373 accessible sectors
*
* Flags:
* 1: unmountable
* 10: read-only
*
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
0 4 00 34 17660989 17661022
8 11 00 17661023 16384 17677406
#
They look the same and still d190 is somewhow different.
#truss -v all zpool create ....
[...]
/1: open("/dev/dsk/c7t5d187", O_RDONLY) = 9
/1: fstat64(9, 0xFFBFB598) = 0
/1: d=0x047C0000 i=16781665 m=0060640 l=1 u=0 g=3
rdev=0x008008AF
/1: at = Sep 20 18:25:27 CEST 2006 [ 1158769527 ]
/1: mt = Sep 20 18:25:27 CEST 2006 [ 1158769527 ]
/1: ct = Sep 20 18:25:27 CEST 2006 [ 1158769527 ]
/1: bsz=8192 blks=0 fs=devfs
/1: close(9) = 0
/1: open("/dev/dsk/c7t5d188", O_RDONLY) Err#2 ENOENT
/1: stat64("/dev/dsk/c7t5d188", 0xFFBFB598) Err#2 ENOENT
/1: open("/dev/dsk/c7t5d189", O_RDONLY) = 9
/1: fstat64(9, 0xFFBFB598) = 0
/1: d=0x047C0000 i=16781697 m=0060640 l=1 u=0 g=3
rdev=0x008008BF
/1: at = Sep 20 18:25:27 CEST 2006 [ 1158769527 ]
/1: mt = Sep 20 18:25:27 CEST 2006 [ 1158769527 ]
/1: ct = Sep 20 18:25:27 CEST 2006 [ 1158769527 ]
/1: bsz=8192 blks=0 fs=devfs
/1: close(9) = 0
/1: open("/dev/dsk/c7t5d190", O_RDONLY) = 9
/1: fstat64(9, 0xFFBFB598) = 0
/1: d=0x047C0000 i=16781713 m=0060640 l=1 u=0 g=3
rdev=0x008008C7
/1: at = Sep 20 19:04:06 CEST 2006 [ 1158771846 ]
/1: mt = Sep 20 19:04:06 CEST 2006 [ 1158771846 ]
/1: ct = Sep 20 19:04:06 CEST 2006 [ 1158771846 ]
/1: bsz=8192 blks=0 fs=devfs
/1: close(9) = 0
/1: fstat64(2, 0xFFBFA5C8) = 0
/1: d=0x047C0000 i=12582920 m=0020620 l=1 u=0 g=7
rdev=0x00600002
/1: at = Sep 21 11:21:54 CEST 2006 [ 1158830514 ]
/1: mt = Sep 21 11:21:54 CEST 2006 [ 1158830514 ]
/1: ct = Sep 20 18:21:33 CEST 2006 [ 1158769293 ]
/1: bsz=8192 blks=0 fs=devfs
/1: write(2, " i n v a l i d v d e v".., 27) = 27
/1: write(2, " u s e ' - f ' t o ".., 43) = 43
/1: write(2, " r a i d z", 5) = 5
/1: write(2, " c o n t a i n s d e".., 37) = 37
/1: _exit(1)
Hmmmm... so maybe it's d188 after all.
# ls -l /dev/dsk/c7t5d187
lrwxrwxrwx 1 root other 46 Sep 20 18:25 /dev/dsk/c7t5d187 ->
../../devices/[EMAIL PROTECTED],0/[EMAIL PROTECTED],401000/[EMAIL
PROTECTED],bb:wd
# ls -l /dev/dsk/c7t5d188
/dev/dsk/c7t5d188: No such file or directory
# ls -l /dev/dsk/c7t5d189
lrwxrwxrwx 1 root other 46 Sep 20 18:25 /dev/dsk/c7t5d189 ->
../../devices/[EMAIL PROTECTED],0/[EMAIL PROTECTED],401000/[EMAIL
PROTECTED],bd:wd
# ls -l /dev/dsk/c7t5d190
lrwxrwxrwx 1 root root 46 Sep 20 19:04 /dev/dsk/c7t5d190 ->
../../devices/[EMAIL PROTECTED],0/[EMAIL PROTECTED],401000/[EMAIL
PROTECTED],be:wd
#
So format -e I put SMI label then again EFI label and now there's a symlink:
# ls -l /dev/dsk/c7t5d188
lrwxrwxrwx 1 root root 46 Sep 21 11:31 /dev/dsk/c7t5d188 ->
../../devices/[EMAIL PROTECTED],0/[EMAIL PROTECTED],401000/[EMAIL
PROTECTED],bc:wd
But still with d190 I can't create a pool.
# zpool create t2 raidz c7t5d176 c7t5d177 c7t5d178 c7t5d179 c7t5d180 c7t5d181
c7t5d182 c7t5d183 c7t5d184 c7t5d185 c7t5d186 c7t5d187 c7t5d188 c7t5d189 c7t5d190
invalid vdev specification
use '-f' to override the following errors:
raidz contains devices of different sizes
#
# dtrace -n syscall::fstat64:entry'{self->st=arg1;self->fd=arg0;}' -n
syscall::fstat64:return'/self->st/{this->a=(struct stat64_32
*)copyin(self->st,sizeof(struct stat64_32));printf("%s size:%d",
fds[self->fd].fi_pathname, (long
long)this->a->st_size);self->st=0;self->pn=0;}' -c "zpool create t2 raidz
c7t5d176 c7t5d177 c7t5d178 c7t5d179 c7t5d180 c7t5d181 c7t5d182 c7t5d183
c7t5d184 c7t5d185 c7t5d186 c7t5d187 c7t5d188 c7t5d189 c7t5d190" | grep ":wd"
dtrace: description 'syscall::fstat64:entry' matched 1 probe
dtrace: description 'syscall::fstat64:return' matched 1 probe
invalid vdev specification
use '-f' to override the following errors:
raidz contains devices of different sizes
dtrace: pid 13314 has exited
8 12562 fstat64:return /devices/[EMAIL PROTECTED],0/[EMAIL
PROTECTED],401000/[EMAIL PROTECTED],b2:wd size:9050849280
8 12562 fstat64:return /devices/[EMAIL PROTECTED],0/[EMAIL
PROTECTED],401000/[EMAIL PROTECTED],b3:wd size:9050849280
8 12562 fstat64:return /devices/[EMAIL PROTECTED],0/[EMAIL
PROTECTED],401000/[EMAIL PROTECTED],b4:wd size:9050849280
8 12562 fstat64:return /devices/[EMAIL PROTECTED],0/[EMAIL
PROTECTED],401000/[EMAIL PROTECTED],b6:wd size:9050849280
8 12562 fstat64:return /devices/[EMAIL PROTECTED],0/[EMAIL
PROTECTED],401000/[EMAIL PROTECTED],b8:wd size:9050849280
8 12562 fstat64:return /devices/[EMAIL PROTECTED],0/[EMAIL
PROTECTED],401000/[EMAIL PROTECTED],b9:wd size:9050849280
8 12562 fstat64:return /devices/[EMAIL PROTECTED],0/[EMAIL
PROTECTED],401000/[EMAIL PROTECTED],ba:wd size:9050849280
8 12562 fstat64:return /devices/[EMAIL PROTECTED],0/[EMAIL
PROTECTED],401000/[EMAIL PROTECTED],bb:wd size:9050849280
8 12562 fstat64:return /devices/[EMAIL PROTECTED],0/[EMAIL
PROTECTED],401000/[EMAIL PROTECTED],bc:wd size:9050357760
8 12562 fstat64:return /devices/[EMAIL PROTECTED],0/[EMAIL
PROTECTED],401000/[EMAIL PROTECTED],bd:wd size:9050849280
8 12562 fstat64:return /devices/[EMAIL PROTECTED],0/[EMAIL
PROTECTED],401000/[EMAIL PROTECTED],be:wd size:9050357760
#
Hmmm.. thats interesting.
Disk d190 has size 9050357760 as reported by fstat64().
Disk d189 has size 9050849280
Disk d188 has size 9050357760
And other disks have 9050849280.
Now why these two disks are reported as different size?
# ./inq.solaris -no_dots| grep d190
/dev/rdsk/c7t5d190s2 :EMC :SYMMETRIX :5568 :9419E050 :8838720
# ./inq.solaris -no_dots| grep d189
/dev/rdsk/c7t5d189s2 :EMC :SYMMETRIX :5568 :9419D050 :8838720
# ./inq.solaris -no_dots| grep d188
/dev/rdsk/c7t5d188s2 :EMC :SYMMETRIX :5568 :9419C050 :8838720
#
Last column is reported size.
Any idea?
ps. of course I can force pool creation but still something wrong is here.
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
