areca check doesn’t work correctly while rebuilding

[glensc]

areca check doesn’t work correctly while rebuilding

[glensc]

stop trolling! as this is what you make by creating pointless issues!

if there is anything to fix, submit command outputs and i see what i can do. killing issue for now

[calestyo]

Hi.

I didn't sent further output, as I though it wasn’t necessary because there is no new output, it’s IMHO rather a problem with how the output is logically evaluated to a status.

In case you care:
http://pastebin.com/QnGF6m5L

As noted before, I think the status must be CRITICAL, not WARNING, given that, even after finishing rebuild there will be still disks that are failed (and actually check_raid) will (after rebuilding) go from WARNING to CRITICAL.
Also as noted before, I could just test this with 2.2.

More general:
To be honest it seems to me that you actually don’t really want anyone to contribute or come up with ideas how to improve robustness of functionality of check_raid.
This has nothing to do with how fast you fix or implement something; I'm pretty aware that we all do this in our spare time.
One could argue that it’s simply a strange habit that you don’t want to have one ticket per issue (as it is common in basically all projects), but when clearly describing an issue as I did before and then being accused of trolling... I don’t see how any contribution could be wanted.

So keep this (and my other open issues) whether you want or not... I won’t care any further as long as I must assume that it is not appreciated or even wanted anyway.

Chris.

[glensc]

creating new issue, because you refuse to test with recent code (with some weird excuse, run the plugin as root for testing is not forbidden), is trolling to me. i'm sorry if you don't understand this, but this is additional workload to me, if you create issues with no information.

[glensc]

Also i don't like you converting issue tracker into discussion board. there's email for that.

[glensc]

check_raid 3.0 reports this test data from pastebin as CRITICAL with output message [Array#1(data): Rebuilding] see the attached commits

[calestyo]

Well the thing is our faculty’s cluster is located in Europes biggest computing facility and we have to live with the (sudo) rights they give us.
Anyway... I got some one time exception now and the output with 3.0 is:

PATH="/opt/lsi/sas2ircu:/opt/MegaRAID/MegaCli:/opt/areca:/opt/adaptec:${PATH}" ./check_raid.pl

UNKNOWN: mdstat:[Plugin error]; areca:[Array#1(data): Rebuilding]

Don't know why it checks for mdstat ... it's not used.

[glensc]

it checks for mdstat because it sees /proc/mdstat file, unload the kernel module if you don't use md devices