tstormchaser
MIS
We have a Sun E5500 server that uses two D1000 disk arrays, each holding 6 disks for a total of 24 disks on the system. Whenver you go into the metadevices and type ./metadb you get a list of all of the metadb in sequential order. We put the metadb on slice 7 of each disk so when you do a metadb it prints out like the following
c1t0d0s7
c1t1d0s7
c1t2d0s7
c1t3d0s7
c1t4d0s7
c1t5d0s7
and so on for c2, c3, and c4.
This happens for every system we have fielded, except for one. It starts with c1t2d0s7 then lists c2t0d0s7, c2t1d0s7, c2t2d0s7, c2t3d0s7, then lists c1t0d0s7 throug target 5 and so on. I've never seen the metadbs listed in anything but a sequetial order. Does anyone know where the system comes up with this order and if there is anyway to change it. We are having major panic reboots on the this particular system and we think it has something to do with the metadb but not sure. Any help would be greatly appreciated.
c1t0d0s7
c1t1d0s7
c1t2d0s7
c1t3d0s7
c1t4d0s7
c1t5d0s7
and so on for c2, c3, and c4.
This happens for every system we have fielded, except for one. It starts with c1t2d0s7 then lists c2t0d0s7, c2t1d0s7, c2t2d0s7, c2t3d0s7, then lists c1t0d0s7 throug target 5 and so on. I've never seen the metadbs listed in anything but a sequetial order. Does anyone know where the system comes up with this order and if there is anyway to change it. We are having major panic reboots on the this particular system and we think it has something to do with the metadb but not sure. Any help would be greatly appreciated.