Skip to content

Conversation

@smckown
Copy link

@smckown smckown commented Sep 19, 2014

Don't assume that the virtual disk IDs are contiguous starting with ID
0. For example, it is possible to have two VDs with IDs 1 and 3.

Don't assume that the virtual disk IDs are contiguous starting with ID
0.  For example, it is possible to have two VDs with IDs 1 and 3.
@smckown
Copy link
Author

smckown commented Sep 19, 2014

Hi,

Two of our servers were upgraded, and their VD IDs are no longer contiguous. Here's a patch that might propertly address this problem. It seems to work fine here, but I'm assuming that the "Target Id" field is the correct ID value and not the "Virtual Drive" field, as can be seen from the output of:

megacli -LDInfo -LALL -a0 -NoLog | grep "^Virtual Drive: "

In our case, both numbers are exactly the same. I found another user who created a delta to solve this same problem, at https://github.com/npinto/megaclisas-status.

@eLvErDe eLvErDe changed the title megaclisas-status: support out of order VDs [megaclisas-status] support out of order VDs Oct 13, 2015
@ElCoyote27
Copy link
Contributor

Could you please test with the latest version of megaclisas-status? I believe I had fixed that in my tree..
Thanks,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants