Our 16-node NetWare cluster has lots of volumes on them.

All our servers boot from the SAN, so LUN 0 is for each server's SYS volume and DOS Boot partition.

But the clustered data volumes have unique LUNs (ie, if we had 30 clustered volumes, each one has a unique LUN from 1-30).

I don't remember WHY we did it that way (maybe we had to for resource failover?)

But I know that Linux sometimes has issues with non-consecutive LUNs.

when we migrate to OES2 Linux, should we keep the LUN numbering/masking as it is?