Date: Fri, 10 Oct 2003 07:40:23 -0600 From: Scott Long <scottl@freebsd.org> To: Aaron Wohl <freebsd@soith.com> Cc: Josh Brooks <user@mail.econolodgetulsa.com> Subject: Re: confusing aaccli output ... Message-ID: <3F86B6C7.7050307@freebsd.org> In-Reply-To: <20031010103606.415923B222@www.fastmail.fm> References: <20031005202453.B54619-100000@mail.econolodgetulsa.com> <20031010103606.415923B222@www.fastmail.fm>
next in thread | previous in thread | raw e-mail | index | archive | help
Aaron Wohl wrote: > Does anyone have a script to run aaccli a few times a day and see if the > raid is happy? > > It used to be easy with dptutil (previous control program from adaptec > for the 3200s)... each status had "Optimal" which changed to Degraded or > whatever. > > aaccli seems geared more twords doing things to the raid than providing > status. Id like to know what all the possible failures are and how to > check for them with aaccli. I have a cron job check the status every few > hours... but with aaccli ive never been sure I checked for all the > failure kinds. > You can script aaccli by piping in the commands that you would normally type and parsing the output: $ aaccli < aac_script.txt > aac_output.txt aac_script.txt: open aac0 container list disk list exit
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F86B6C7.7050307>