From owner-freebsd-scsi@FreeBSD.ORG Wed May 7 11:37:03 2003 Return-Path: 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 ED34037B401 for ; Wed, 7 May 2003 11:37:03 -0700 (PDT) Received: from mail.econolodgetulsa.com (mail.econolodgetulsa.com [198.78.66.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AE6A43F75 for ; Wed, 7 May 2003 11:37:03 -0700 (PDT) (envelope-from user@mail.econolodgetulsa.com) Received: from mail (mail [198.78.66.163])h47Ib3eq065205 for ; Wed, 7 May 2003 11:37:03 -0700 (PDT) (envelope-from user@mail.econolodgetulsa.com) Date: Wed, 7 May 2003 11:37:02 -0700 (PDT) From: Josh Brooks To: freebsd-scsi@freebsd.org Message-ID: <20030507113048.Y5537-100000@mail.econolodgetulsa.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: aaccli core dumps ... looking for solution... X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 May 2003 18:37:04 -0000 Hello, I had some mirrors that had members marked offline, and before I buy new disks and replace them i wanted to try (at least once) to verify them and rejoin them and see how long they last. So, I started aaccli and ran: disk verify /repair=TRUE (2,1,0) and then ran: disk verify /repair=TRUE (3,2,0) so i was running two verifys concurrently - I checked it by running `task list` a few times, and they were both proceeding just fine. So I went to bed. I wake up this morning, and the machine is fine, but I can no longer use aaccli. When I run it, it starts, I get the prompt, and I can run things like `controller list`, but when I try to `open aac0` i get: CLI > open aac0 Executing: open "aac0" AAC0> Floating exception (core dumped)r: , State:DNE 100.0% So ... it looks like the ANSI screen drawing screws up a little, as it prints the core dump message on top of the status: done message ... ------- So, I am wondering what to do ... I cannot check the state of my disks without being able to open the controller ... but I also cannot reboot this machine right now (since, presumably that would just make this problem go away). Any suggestions ? I was thinking of running one of these commands: controller rescan - Rescans the SCSI buses, and updates all underlying structures. controller reset_scsi_bus - Resets the specified SCSI bus. controller resume_io - Does rescan operation and then resumes IO after pause_io. But I am afraid to run them on this live, running system - can anyone tell me if any of these commands, in general, are safe to run as an attempt to "slap the controller and make it behave" ? Any comments appreciated...