From owner-freebsd-scsi Wed Feb 12 0:18:30 2003 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CAB537B401 for ; Wed, 12 Feb 2003 00:18:28 -0800 (PST) Received: from mail.econolodgetulsa.com (mail.econolodgetulsa.com [198.78.66.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9E2943F93 for ; Wed, 12 Feb 2003 00:18:27 -0800 (PST) (envelope-from user@mail.econolodgetulsa.com) Received: from mail (user@mail [198.78.66.163]) by mail.econolodgetulsa.com (8.12.3/8.12.3) with ESMTP id h1C8IUdR082013 for ; Wed, 12 Feb 2003 00:18:30 -0800 (PST) (envelope-from user@mail.econolodgetulsa.com) Date: Wed, 12 Feb 2003 00:18:29 -0800 (PST) From: Josh Brooks To: freebsd-scsi@freebsd.org Subject: confusing aaccli output Message-ID: <20030212001508.U39971-100000@mail.econolodgetulsa.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, I am seeing this in aaccli: AAC0> container list Executing: container list Num Total Oth Chunk Scsi Partition Label Type Size Ctr Size Usage B:ID:L Offset:Size ----- ------ ------ --- ------ ------- ------ ------------- 0 Mirror 34.1GB Open 0:01:0 64.0KB:34.1GB /dev/aacd0 array01 0:00:0 64.0KB!34.1GB 1 Mirror 34.1GB Open 0:02:0 64.0KB:34.1GB /dev/aacd1 array02 0:03:0 64.0KB:34.1GB At first glance it looks fine. Two healthy containers. But what is that exclamation point: 0:00:0 64.0KB!34.1GB Interesting. Now I look at /var/log/messages: Feb 9 17:26:36 system /kernel: aac0: **Monitor** Drive 0:0:0 returning error Feb 9 17:26:36 system /kernel: aac0: **Monitor** ID(0:00:0) - drive failure (retries exhausted) Feb 9 17:26:36 system /kernel: aac0: **Monitor** Mirror Container 0 Drive 0:0:0 Failure Feb 9 17:26:46 system /kernel: aac0: **Monitor** Mirror Failover Container 0 no failover assigned So what is going on here ? messages tell me I have a broken mirror, but aaccli shows me a healthy one. Iam afraid to run a: container set failover because aaccli shows it as already belonging to the container... Any advice/comments - especially regarding what I should do next - is appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message