Very Computer

raidutil -c c2t5d0 -n 0,1,2,3,4,5,6,7,8,9 -s
17275,17275,17275,17275,17275,17275,17275,17275,17275,16871  -l 5 -g
10,20,11,21,12,22,13,23,14,24,25

No existing LUNs were found on c2t5d0.

^CCapacity available in drive group:  352965760 blocks  (172346 MB).
Creating LUN 0

Registering new logical unit 0 with system.
^CFormatting logical unit 0  RAID 5   17275 MB LUNs found on c2t5d0.
  LUN 0    RAID 5    17275 MB
Creating LUN 1

Registering new logical unit 1 with system.
^CFormatting logical unit 1  RAID 5   17275 MB LUNs found on c2t5d0.
  LUN 0    RAID 5    17275 MB
  LUN 1    RAID 5    17275 MB
Creating LUN 2

Registering new logical unit 2 with system.
^CFormatting logical unit 2  RAID 5   17275 MB LUNs found on c2t5d0.
  LUN 0    RAID 5    17275 MB
  LUN 1    RAID 5    17275 MB
  LUN 2    RAID 5    17275 MB
Creating LUN 3

As you can see, it hangs after every 'Registering new logical unit ...'

Pressing 'Ctrl-C', as you can see above, jolts it into proceeding!

What is going on? Why is it* after creating each LUN?

Thanks

# drivutil -d c2t5d0

Drives in Group for labqa_001

  Group          Drive List  [Channel,Id]

 Unassigned     [1,0]; [2,0]; [1,1]; [2,1]; [1,2]; [2,2]; [1,3]; [2,3];
[1,4]; [2,4]; [1,5]; [2,5];

drivutil succeeded!

# export disk_group="10,20,11,21,12,22,13,23,14,24,25"
# raidutil -c c2t5d0 -n 0 -s 17275  -l 5 -g $disk_group
No existing LUNs were found on c2t5d0.

It just sits there and hangs. ps -ef|grep raid shows add_disk taking CPU
time, but it just sits there.

I used to be able to create LUNs on this RAID module just yesterday. What
went wrong?

When I Ctrl-C this, things get really messed up. Even raidutil -i or -D all
or -X gives me 'Unable to open device. status = 17' errors.

Help! Thanks

how about some details regarding SOlaris version and patch level?

--
Posted via http://dbforums.com

# pkginfo -l SUNWosar
   PKGINST:  SUNWosar
      NAME:  Open Storage Array (Root)
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  06.22,REV=01.54
    VSTOCK:  06.22.01.54
    STATUS:  completely installed

Strange, I would have thought there was better protection against this kind
of thing happening i.e. a trap in the 'raidutil' wrapper shell script or a
/etc/init.d cleanup script when the machine reboots or something. Having
'raidutil' hang and behave erratically like this due to a silly tmp file is
so amateur-ish! Oh well...!

Thanks