Hi Matt, > I would like to use the smart_ plugin with my cciss controller. > smartmontools supports cciss in a fashion similar to 3ware, you can > specify the disk to query when talking to the controller. For example > I can run > > /usr/sbin/smartctl -d cciss,0 -A -i /dev/cciss/c0d0 > > and it returns info for disk 0 on the first controller. The main > difference from 3ware controllers is the fact that the device is in a > subdirectory (/dev/cciss/c#d# vs /dev/twa#). However the smart_ plugin > already has to deal with extra directories for SunOS device names, so > it should be possible. > > Attached is an attempt at a patch, and the output of the above > command. > It's not working and I can't figure out why, maybe the output is > different than expected? It's hard to tell from the code what it is > expecting, maybe comparing with working output would help. thanks for the report! :-) I tested your patch and played around with a hp server with cciss controller. Your patch works well - the plugin detects now the right disk. But the output of smartctl looks very different from the 'normal' one. In line 114 detects the plugin the start of an attribute block from the header "ID# ATTRIBUTE_NAME..." but in the output this header is missing.
Running /usr/sbin/smartctl -d cciss,0 -a -A -i /dev/cciss/c0d0 spits out some more stats like Error counter logs. I am unsure if this is an useful value to gather and graph with munin. If you say yes - i'll try to integrate it. best regards, Matthias
signature.asc
Description: PGP signature
