Rick McNeal wrote: > It's possible someone is opening the device for exclusive use. Though > I would expect a different error number/message if that was the case. > I still need to look through the code and determine where an HARDWARE > check condition is set. Most likely during the initial opening of the > device which is part of the framework code and not the SCSI INQUIRY > command proper.
Rick, I think the issue is pretty clear, at least from what I can see: > >> # ls -l /dev/zvol/rdsk/data/vol/ >> total 3 >> lrwxrwxrwx 1 root root 42 Jan 20 12:33 lun001 -> >> ../../../../../devices/pseudo/z...@0:3c,raw >> lrwxrwxrwx 1 root root 42 Jan 20 16:33 testlun -> >> ../../../../../devices/pseudo/z...@0:3c,raw >> lrwxrwxrwx 1 root root 42 Jan 21 14:09 testlun1 -> >> ../../../../../devices/pseudo/z...@0:3c,raw >> >> # ls -l /devices/pseudo/zfs* >> brw------- 1 root sys 182, 1 Jan 23 15:00 >> /devices/pseudo/z...@0:1c >> crw------- 1 root sys 182, 1 Jan 23 15:00 >> /devices/pseudo/z...@0:1c,raw >> brw------- 1 root sys 182, 2 Jan 23 15:00 >> /devices/pseudo/z...@0:2c >> crw------- 1 root sys 182, 2 Jan 23 15:00 >> /devices/pseudo/z...@0:2c,raw >> crw-rw-rw- 1 root sys 182, 0 Jan 23 14:29 >> /devices/pseudo/z...@0:zfs >> >> There are no "z...@0:3c" device nodes. A "devfsadm -C" has no effect. I'm >> out >> of my depth with the zvol device nodes, so maybe someone can enlighten me. :) I don't know how it could happen that my /dev entries for my zvols points to a non-existent device. I haven't tried to do anything "clever"-- just using zfs(1M) to manage zvols and iSCSI sharing. Anyone care to speculate about what might have happened here? Thanks, Eric _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
