Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Oct 2003 07:24:48 -0700 (PDT)
From:      David Raistrick <drais@wow.atlasta.net>
To:        Aaron Wohl <freebsd@soith.com>
Cc:        freebsd-scsi@freebsd.org
Subject:   Re: confusing aaccli output ...
Message-ID:  <Pine.BSF.4.50L0.0310100716490.66765-100000@wow.atlasta.net>
In-Reply-To: <3F86B6C7.7050307@freebsd.org>
References:  <20031005202453.B54619-100000@mail.econolodgetulsa.com> <20031010103606.415923B222@www.fastmail.fm> <3F86B6C7.7050307@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

On Fri, 10 Oct 2003, Scott Long wrote:

> 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


For quickies you can also just add them to the commandline with the
delimiter:

$ aaccli  open aac0 : container list : disk list

You can change the delimiter with the -d option if you need something
other then :

Handy.

On the disk list topic, I had a disk disappear from the list this morning.
The first time I ran disk list, aaccli paused while trying to contact the
disk, then listed it as offline:


Executing: disk list

C:ID:L  Device Type     Blocks    Bytes/Block Usage            Shared Rate
------  --------------  --------- ----------- ---------------- ------ ----
1:00:0   Disk            17916240  512         Initialized      NO     80
1:01:0   Disk            17916240  512         Initialized      NO     80

1:02:0   Disk            0         0           Offline          NO     0


Since then the offline disk no longer shows at all

C:ID:L  Device Type     Blocks    Bytes/Block Usage            Shared Rate
------  --------------  --------- ----------- ---------------- ------ ----
1:00:0   Disk            17916240  512         Initialized      NO     306
1:01:0   Disk            17916240  512         Initialized      NO     306


Sort of annoying, since the later report has no indication that it ever
knew the disk was there.

The container list /does/ have a very minor indication that there is a
problem with the disk:

 0    RAID-5  200MB       64KB Open    1:00:0 64.0KB: 100MB
 /dev/aacd0                            1:01:0 64.0KB: 100MB
                                       1:02:0 64.0KB! 100MB


Notice the "!" instead of a ":" for 1:02:0.


Just fwiw, something to keep an eye out for.



---
david raistrick
drais@atlasta.net		http://www.expita.com/nomime.html



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.50L0.0310100716490.66765-100000>