SCCLI 'hangs' when you don't specify an array LUN on 3320

I have a 3320, the SCCLI 'hangs' when you don't specify an array LUN. End of truss output:

14651: stat("/dev/rdsk/c0t0d0s2", 0xFFBFF408) = 0

14651: stat("/dev/rdsk/c0t0d0s2", 0xFFBFF740) = 0

14651: stat("/dev/rdsk/c0t0d0s2", 0xFFBFF408) = 0

14651: open("/dev/rdsk/c0t0d0s2", O_RDWR|O_NDELAY)= 3

14651: ioctl(3, 0x04C9, 0xFFBFF3F8)Err#5 EIO

14651: nanosleep(0xFFBFF378, 0xFFBFF370) (sleeping...)

14651:Received signal #2, SIGINT, in nanosleep() [default]

14651: nanosleep(0xFFBFF378, 0xFFBFF370)Err#4 EINTR

[572 byte] By [ChrisDB] at [2007-11-26 11:47:50]

«« Cluster for IM
»» Sun 1 ASP Issue after Linox box reinstall

# 1

There needs to be a lun on the array in order for it to communicate in band. Normally lun 0 is there by default, and if you don't specify a lun # it tries to use lun 0.Is there any lun on the array? If so use that.

domburns at 2007-7-7 11:59:38 >

Storage General Discussion

Java programming resources: FAQs, tutorials, compiler and browser download sites, documentation, books lists, IDEs, etc.

SCCLI 'hangs' when you don't specify an array LUN on 3320

Storage Forums New Topic

Storage Forums Hot Topic

Storage Forums

All Classified