Looking at zpool_vdev.c#663 If I remove links to a whole disk zpool would skip
size checking.
So I did:
# rm /dev/dsk/c7t5d190
# rm /dev/dsk/c7t5d189
# rm /dev/dsk/c7t5d188
And now:
# zpool create t2 raidz c7t5d176 c7t5d177 c7t5d178 c7t5d179 c7t5d180 c7t5d181
c7t5d182 c7t5d183 c7t5d184 c7t5d185 c7t5d186 c7t5d187 c7t5d188 c7t5d189 c7t5d190
#
ok, it did worked.
However it looks like zpool ignores vdev size checking if it can't get one from
fstat() or stat().
1. What would happen is size actually are different but it wasn't checked and
pool was created?
ZFS will panic or generate r/w error when accessing non existant blocks?
2. What about my case - why format() or EMC's inq (and Symmetrix itself) show
that all these devices are the same size while fstat() shows different?
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
