From owner-freebsd-scsi@FreeBSD.ORG Sun Sep 26 20:10:37 2004 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 0E6F416A4CE for ; Sun, 26 Sep 2004 20:10:37 +0000 (GMT) Received: from forrie.com (forrie.ne.client2.attbi.com [24.147.45.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 621DA43D45 for ; Sun, 26 Sep 2004 20:10:36 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from [127.0.0.1] ([192.168.1.99]) by forrie.com with ESMTP id i8QKAQBw080495 for ; Sun, 26 Sep 2004 16:10:29 -0400 (EDT) (envelope-from forrie@forrie.com) Message-ID: <415722AA.9080500@forrie.com> Date: Sun, 26 Sep 2004 16:12:26 -0400 From: Forrest Aldrich User-Agent: Mozilla Thunderbird 0.8 (Windows/20040925) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.ne.client2.attbi.com) X-MailScanner-LocalNet: Found to be clean Subject: Status of iSCSI 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: Sun, 26 Sep 2004 20:10:37 -0000 I read the April 2004 report (on freebsd.org); presuming that's up-to-date, it may be a while before we have iSCSI support in FreeBSD. I wanted to verify here, etc. I'm involved in a project that will require something of that nature. Thanks, Forrest From owner-freebsd-scsi@FreeBSD.ORG Sun Sep 26 20:30:19 2004 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 4676916A500 for ; Sun, 26 Sep 2004 20:30:19 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E1E243D53 for ; Sun, 26 Sep 2004 20:30:18 +0000 (GMT) (envelope-from scottl@FreeBSD.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i8QKUbpp055227; Sun, 26 Sep 2004 14:30:37 -0600 (MDT) (envelope-from scottl@FreeBSD.org) Message-ID: <4157267D.4090009@FreeBSD.org> Date: Sun, 26 Sep 2004 14:28:45 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040831 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Forrest Aldrich References: <415722AA.9080500@forrie.com> In-Reply-To: <415722AA.9080500@forrie.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-scsi@FreeBSD.org Subject: Re: Status of iSCSI 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: Sun, 26 Sep 2004 20:30:19 -0000 Forrest Aldrich wrote: > I read the April 2004 report (on freebsd.org); presuming that's > up-to-date, it may be a while before we have iSCSI support in FreeBSD. > I wanted to verify here, etc. > > I'm involved in a project that will require something of that nature. > > > Thanks, > Forrest > [Note that email to you is bouncing, so I'm responding publically] There was an implementation done by Lucent last year for 4.x, but it has a sticky license and is probably out of date. I and several others see iSCSI as something that really needs to get done, but the 3-4 months of development time is more than can be done on evenings and weekends. I would also want to do it 'right' and implement new infrastructure in CAM to accompany it rather than making it monolithic like the Lucent implementation. What kind of project do you need it for, and what kind of resources do you have right now? Scott From owner-freebsd-scsi@FreeBSD.ORG Sun Sep 26 21:42:16 2004 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 C2B2516A4CE for ; Sun, 26 Sep 2004 21:42:16 +0000 (GMT) Received: from oceanpark.com (bdsl.66.15.120.169.gte.net [66.15.120.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FD1443D2D for ; Sun, 26 Sep 2004 21:42:16 +0000 (GMT) (envelope-from allard@oceanpark.com) Received: from oceanpark.com (localhost.localdomain [127.0.0.1]) by oceanpark.com (8.12.8/8.12.8) with ESMTP id i8QLjl3f002330 for ; Sun, 26 Sep 2004 14:45:47 -0700 Received: (from root@localhost) by oceanpark.com (8.12.8/8.12.8/Submit) id i8QLjlRj002327 for freebsd-scsi@freebsd.org; Sun, 26 Sep 2004 14:45:47 -0700 X-Sent-To: allard@oceanpark.com Received: FROM oceanpark.com (66 159 242 157) by oceanpark.com with ESMTP ; 26 SEP 2004 21:45:46 UT Message-ID: <415737A4.4090501@oceanpark.com> Date: Sun, 26 Sep 2004 14:41:56 -0700 From: Dennis G Allard User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: non-responding PERC with aaccli ... 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: Sun, 26 Sep 2004 21:42:17 -0000 Hi Josh. I'm looking for someone who can help me bring a hot failover drive online via a AFACLI tool? Are you available for a quick question or two? I will pay your rate for your help. Here is my question: I am working for a company that has some serious problems in their aging hardware. I'm a veteran programmer but have never configured hardware RAID before now. Here is the problem statement and my best *guess* as to a solution, based on my reading of the AFACLI documentation. Context: We have a Dell Poweredge 2450 on Red Hat 6.2 in the following state: >> AFA0> enclosure show slot >> Executing: enclosure show slot >> >> Enclosure >> ID (B:ID:L) Slot scsiId Insert Status >> ----------- ---- ------ ------- ------------------------------------------ >> 0 0:06:0 0 0:00:0 1 OK FAILED CRITICAL ACTIVATE >> 0 0:06:0 1 0:01:0 1 OK FAILED CRITICAL ACTIVATE >> 0 0:06:0 2 0:02:0 1 ERROR FAULTY FAILED CRITICAL ACTIVATE >> 0 0:06:0 3 0:03:0 1 OK UNCONFIG HOTSPARE ACTIVATE >> >> AFA0> disk list >> Executing: disk list >> >> B:ID:L Device Type Blocks Bytes/Block Usage Shared >> ------ -------------- --------- ----------- ---------------- ------ >> 0:00:0 Disk 71132959 512 Initialized NO >> 0:01:0 Disk 71132960 512 Initialized NO >> 0:02:0 Disk 0 0 Offline NO >> 0:03:0 Disk 71132960 512 Initialized NO >> >> AFA0> container list >> Executing: container list >> Num Total Oth Chunk Scsi Partition >> Label Type Size Ctr Size Usage B:ID:L Offset:Size >> ----- ------ ------ --- ------ ------- ------ ------------- >> 0 RAID-5 67.7GB 32KB Open 0:00:0 64.0KB:33.8GB >> /dev/sda SEPT 0:01:0 64.0KB:33.8GB >> 0:02:0 64.0KB!33.8GB >> >> >> AFA0> Based on my reading from the Web, I interpret the above to mean that we have a RAID-5 array with two functioning disks after the third disk failed, meaning that we no longer have redundancy and are in a very precarious situation. There is a fourth drive available for use as a hot spare but it currently is not in the RAID-5 array. Problem Statement: How do I make the hot spare (0,3,0) replace the hosed drive (0,2,0). Proposed Solution: I should use AFACLI and do: container set failover 0 (0,3,0) Question: Is the above command the right thing to do? If not, what? If so, is there any prelimary preparation of the disk needed? Can doing the above command cause something horrible to happen? Is there anything I need to do to get rid of the "!" drive (0,2,0) from the array? Thanks for any help you can provide. regards, Dennis -- Dennis G. Allard telephone: 1.310.399.4740 Ocean Park Software http://oceanpark.com ________________________________________________________________________ From owner-freebsd-scsi@FreeBSD.ORG Mon Sep 27 11:02:03 2004 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 C9A6516A4D4 for ; Mon, 27 Sep 2004 11:02:03 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2FD443D39 for ; Mon, 27 Sep 2004 11:02:03 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i8RB23WQ014705 for ; Mon, 27 Sep 2004 11:02:03 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8RB227j014699 for freebsd-scsi@freebsd.org; Mon, 27 Sep 2004 11:02:02 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 27 Sep 2004 11:02:02 GMT Message-Id: <200409271102.i8RB227j014699@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Subject: Current problem reports assigned to you 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: Mon, 27 Sep 2004 11:02:04 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [2000/08/18] kern/20689 scsi Newbusified version of ncr driver does no f [2000/09/12] kern/21220 scsi mlx0: I/O error - attempt to write beyond f [2001/05/03] kern/27059 scsi (symbios) SCSI subsystem hangs under heav o [2001/06/29] kern/28508 scsi problems with backup to Tandberg SLR40 st o [2002/06/17] kern/39388 scsi ncr/sym drivers fail with 53c810 and more o [2002/07/22] kern/40895 scsi wierd kernel / device driver bug f [2002/09/15] kern/42796 scsi NCR/SYM 53C825 driver detects scsi cdrom f [2002/11/25] kern/45713 scsi If you use the amr driver, it is impossib f [2002/12/09] kern/46152 scsi Panic in adw dumping to tape f [2003/05/16] kern/52331 scsi 4.7 to 4.8-REL upgrade: SCSI disks on sym f [2003/09/14] kern/56759 scsi [hang] System freezes when writing CD Adv f [2003/09/14] kern/56760 scsi [hang] system hangs at boot with adaptec f [2003/09/14] kern/56871 scsi dd can't write variable length data block f [2003/09/18] kern/56973 scsi SCSI errors from on-board Adaptec (AIC7xx s [2003/09/30] kern/57398 scsi Current fails to install on mly(4) based o [2003/12/26] kern/60598 scsi wire down of scsi devices conflicts with a [2004/01/10] kern/61165 scsi [panic] kernel page fault after calling c o [2004/09/15] kern/71778 scsi 5.3 BETA3 doesnt see Adaptec 2015S FW Rev 18 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/12/06] kern/23314 scsi aic driver fails to detect Adaptec 1520B o [2001/08/15] kern/29727 scsi [amr] [patch] amr_enquiry3 structure in a o [2002/02/23] kern/35234 scsi World access to /dev/pass? (for scanner) o [2002/06/02] kern/38828 scsi [feature request] DPT PM2012B/90 doesn't o [2002/10/29] kern/44587 scsi dev/dpt/dpt.h is missing defines required o [2003/10/01] kern/57468 scsi [patch] Quirk for Quantum LPS540S o [2003/10/01] kern/57469 scsi [patch] Quirk for Conner CP3500 o [2004/09/22] kern/72010 scsi [patch] mt -f /dev/rsa0.ctl comp off, or 8 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Sep 27 16:20:58 2004 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 38DD816A4CE for ; Mon, 27 Sep 2004 16:20:58 +0000 (GMT) Received: from oceanpark.com (bdsl.66.15.120.169.gte.net [66.15.120.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id E26E043D41 for ; Mon, 27 Sep 2004 16:20:54 +0000 (GMT) (envelope-from allard@oceanpark.com) Received: from oceanpark.com (localhost.localdomain [127.0.0.1]) by oceanpark.com (8.12.8/8.12.8) with ESMTP id i8RGOS3f013377 for ; Mon, 27 Sep 2004 09:24:28 -0700 Received: (from root@localhost) by oceanpark.com (8.12.8/8.12.8/Submit) id i8RGOSai013375 for freebsd-scsi@freebsd.org; Mon, 27 Sep 2004 09:24:28 -0700 X-Sent-To: kris@iguana.be Received: FROM oceanpark.com (66 159 242 157) by oceanpark.com with ESMTP ; 27 SEP 2004 16:24:21 UT Message-ID: <41583DC8.7000301@oceanpark.com> Date: Mon, 27 Sep 2004 09:20:24 -0700 From: Dennis G Allard User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: AFACLI failover success (was: non-responding PERC with aaccli ...) 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: Mon, 27 Sep 2004 16:20:58 -0000 Thanks for everyone who replied. The original procedure for using AFACLI to activate a HOTSPARE that I outlined worked except, after performing `container set global_failover (0,3,0), I had to do `controller rescan` before the failover kicked in. This in spite of the fact that `controller show automatic_failover` was ENABLED. Since I do not subscribe to this mailing list (or any mailing list, preferring IETF standard newsgroup culture), I am sending this summary as a stand-alone post. (It would be good if someone were to post a follow up to the original thread and include the following text to complete that thread, thanks)... DETAILS: (1 of 4) ORIGINAL STATE (pre-failover): AFA0> enclosure show slot > Executing: enclosure show slot > > Enclosure > ID (B:ID:L) Slot scsiId Insert Status > ----------- ---- ------ ------- ------------------------------------------ > 0 0:06:0 0 0:00:0 1 OK FAILED CRITICAL ACTIVATE > 0 0:06:0 1 0:01:0 1 OK FAILED CRITICAL ACTIVATE > 0 0:06:0 2 0:02:0 1 ERROR FAULTY FAILED CRITICAL ACTIVATE > 0 0:06:0 3 0:03:0 1 OK UNCONFIG HOTSPARE ACTIVATE > > AFA0> disk list > Executing: disk list > > B:ID:L Device Type Blocks Bytes/Block Usage Shared > ------ -------------- --------- ----------- ---------------- ------ > 0:00:0 Disk 71132959 512 Initialized NO > 0:01:0 Disk 71132960 512 Initialized NO > 0:02:0 Disk 0 0 Offline NO > 0:03:0 Disk 71132960 512 Initialized NO > > AFA0> container list > Executing: container list > Num Total Oth Chunk Scsi Partition > Label Type Size Ctr Size Usage B:ID:L Offset:Size > ----- ------ ------ --- ------ ------- ------ ------------- > 0 RAID-5 67.7GB 32KB Open 0:00:0 64.0KB:33.8GB > /dev/sda SEPT 0:01:0 64.0KB:33.8GB > 0:02:0 64.0KB!33.8GB > > > AFA0> (2 of 4) ACTIONS TAKEN: container set global_failover (0,3,0) controller rescan Excerpts from acutal session: Note: [[my comments are in double square brackets like these]] > AFA0> task list > Executing: task list > > Controller Tasks > > TaskId Function Done% Container State Specific1 Specific2 > ------ -------- ------- --------- ----- --------- --------- > > No tasks currently running on controller > > AFA0> container set global_failover (0,3,0) > Executing: container set global_failover (BUS=0,ID=3,LUN=0) > > AFA0> task list > Executing: task list > > Controller Tasks > > TaskId Function Done% Container State Specific1 Specific2 > ------ -------- ------- --------- ----- --------- --------- > > No tasks currently running on controller [[Hmmm - why not?]] > > AFA0> > AFA0> > AFA0> disk show space > Executing: disk show space > > Scsi B:ID:L Usage Size > ----------- ---------- ------------- > 0:00:0 Container 64.0KB:33.8GB > 0:00:0 Free 33.8GB:59.0KB > 0:01:0 Container 64.0KB:33.8GB > 0:01:0 Free 33.8GB:59.0KB > 0:02:0 Dead 64.0KB:33.8GB > 0:02:0 Free 33.8GB:59.0KB > 0:03:0 Free 64.0KB:33.8GB > > AFA0> > AFA0> > AFA0> container list > Executing: container list > Num Total Oth Chunk Scsi Partition > Label Type Size Ctr Size Usage B:ID:L Offset:Size > ----- ------ ------ --- ------ ------- ------ ------------- > 0 RAID-5 67.7GB 32KB Open 0:00:0 64.0KB:33.8GB > /dev/sda SEPT 0:01:0 64.0KB:33.8GB > 0:02:0 64.0KB!33.8GB > > > AFA0> enclosure show slot > Executing: enclosure show slot > > Enclosure > ID (B:ID:L) Slot scsiId Insert Status > ----------- ---- ------ ------- ------------------------------------------ > 0 0:06:0 0 0:00:0 1 OK FAILED CRITICAL ACTIVATE > 0 0:06:0 1 0:01:0 1 OK FAILED CRITICAL ACTIVATE > 0 0:06:0 2 0:02:0 1 ERROR FAULTY FAILED CRITICAL ACTIVATE > 0 0:06:0 3 0:03:0 1 OK UNCONFIG HOTSPARE ACTIVATE > > AFA0> > AFA0> > AFA0> > AFA0> container show failover > Executing: container show failover > > Container Scsi B:ID:L > --------- ---------------------------------- > GLOBAL 0:03:0 > 0 --- No Devices Assigned --- > > AFA0> > AFA0> > AFA0> > AFA0> controller show automatic_failover > Executing: controller show automatic_failover > Automatic failover ENABLED [[Well????]] > > AFA0> > AFA0> > AFA0> [[I guessed to try...]] > AFA0> controller rescan > Executing: controller rescan > > AFA0> > AFA0> task list > Executing: task list > > Controller Tasks > > TaskId Function Done% Container State Specific1 Specific2 > ------ -------- ------- --------- ----- --------- --------- > 101 Rebuild 0.1% 00 RUN 00000000 00000000 > > AFA0> task list > Executing: task list > > Controller Tasks > > TaskId Function Done% Container State Specific1 Specific2 > ------ -------- ------- --------- ----- --------- --------- > 101 Rebuild 0.1% 00 RUN 00000000 00000000 [[Much Better!!!]] > > AFA0> task list > Executing: task list > > Controller Tasks > > TaskId Function Done% Container State Specific1 Specific2 > ------ -------- ------- --------- ----- --------- --------- > 101 Rebuild 0.2% 00 RUN 00000000 00000000 > > AFA0> task list > Executing: task list > > Controller Tasks > > TaskId Function Done% Container State Specific1 Specific2 > ------ -------- ------- --------- ----- --------- --------- > 101 Rebuild 0.6% 00 RUN 00000000 00000000 > > AFA0> task list > Executing: task list > > Controller Tasks > > TaskId Function Done% Container State Specific1 Specific2 > ------ -------- ------- --------- ----- --------- --------- > 101 Rebuild 0.6% 00 RUN 00000000 00000000 > > AFA0> task list > Executing: task list > > Controller Tasks > > TaskId Function Done% Container State Specific1 Specific2 > ------ -------- ------- --------- ----- --------- --------- > 101 Rebuild 1.3% 00 RUN 00000000 00000000 > > AFA0> > AFA0> > AFA0> > AFA0> enclosure show slot > Executing: enclosure show slot > > Enclosure > ID (B:ID:L) Slot scsiId Insert Status [[note the REBUILD]] > ----------- ---- ------ ------- ------------------------------------------ > 0 0:06:0 0 0:00:0 1 OK REBUILD FAILED CRITICAL ACTIVATE > 0 0:06:0 1 0:01:0 1 OK REBUILD FAILED CRITICAL ACTIVATE > 0 0:06:0 2 0:02:0 1 OK FAILED CRITICAL UNCONFIG ACTIVATE > 0 0:06:0 3 0:03:0 1 OK REBUILD FAILED CRITICAL HOTSPARE > ACTIVATE > > AFA0> > AFA0> > AFA0> > AFA0> container list > Executing: container list > Num Total Oth Chunk Scsi Partition > Label Type Size Ctr Size Usage B:ID:L Offset:Size > ----- ------ ------ --- ------ ------- ------ ------------- > 0 RAID-5 67.7GB 32KB Open 0:00:0 64.0KB:33.8GB > /dev/sda SEPT 0:01:0 64.0KB:33.8GB > 0:03:0 64.0KB:33.8GB > > > AFA0> > AFA0> > AFA0> disk list > Executing: disk list > > B:ID:L Device Type Blocks Bytes/Block Usage Shared > ------ -------------- --------- ----------- ---------------- ------ > 0:00:0 Disk 71132959 512 Initialized NO > 0:01:0 Disk 71132960 512 Initialized NO > 0:02:0 Disk 0 0 Offline NO > 0:03:0 Disk 71132960 512 Initialized NO > > AFA0> > AFA0> > AFA0> disk show space > Executing: disk show space > > Scsi B:ID:L Usage Size > ----------- ---------- ------------- > 0:00:0 Container 64.0KB:33.8GB > 0:00:0 Free 33.8GB:59.0KB > 0:01:0 Container 64.0KB:33.8GB > 0:01:0 Free 33.8GB:59.0KB > 0:03:0 64.0KB:33.8GB [[0:02:0 is gone -- good]] > 0:03:0 Free 33.8GB:59.0KB > > AFA0> > AFA0> > AFA0> [[ultimately, the REBUILD took ~2.5 hours]] (3 of 4) FINAL STATE (post-failover): > afacli > --------------------------------------------------------------------------------------------------------------------------------------------- > DELL PowerEdge Expandable RAID Controller 2 Command Line Interface > Copyright 1998-2000 Adaptec, Inc. All rights reserved > --------------------------------------------------------------------------------------------------------------------------------------------- > > FASTCMD> open afa0 > Executing: open "afa0" > > AFA0> enclosure show slot > Executing: enclosure show slot > > Enclosure > ID (B:ID:L) Slot scsiId Insert Status > ----------- ---- ------ ------- ------------------------------------------ > 0 0:06:0 0 0:00:0 1 OK ACTIVATE > 0 0:06:0 1 0:01:0 1 OK ACTIVATE > 0 0:06:0 2 0:02:0 1 OK FAILED CRITICAL UNCONFIG ACTIVATE > 0 0:06:0 3 0:03:0 1 OK HOTSPARE ACTIVATE [[why still see 'HOTSPARE'?]] > > AFA0> > AFA0> > AFA0> disk list > Executing: disk list > > B:ID:L Device Type Blocks Bytes/Block Usage Shared > ------ -------------- --------- ----------- ---------------- ------ > 0:00:0 Disk 71132959 512 Initialized NO > 0:01:0 Disk 71132960 512 Initialized NO > 0:02:0 Disk 0 0 Offline NO > 0:03:0 Disk 71132960 512 Initialized NO > > AFA0> > AFA0> > AFA0> container list > Executing: container list > Num Total Oth Chunk Scsi Partition > Label Type Size Ctr Size Usage B:ID:L Offset:Size > ----- ------ ------ --- ------ ------- ------ ------------- > 0 RAID-5 67.7GB 32KB Open 0:00:0 64.0KB:33.8GB > /dev/sda SEPT 0:01:0 64.0KB:33.8GB > 0:03:0 64.0KB:33.8GB > > > AFA0> > AFA0> > AFA0> disk show space > Executing: disk show space > > Scsi B:ID:L Usage Size > ----------- ---------- ------------- > 0:00:0 Container 64.0KB:33.8GB > 0:00:0 Free 33.8GB:59.0KB > 0:01:0 Container 64.0KB:33.8GB > 0:01:0 Free 33.8GB:59.0KB > 0:03:0 Container 64.0KB:33.8GB > 0:03:0 Free 33.8GB:59.0KB > > AFA0> > AFA0> > AFA0> container show failover > Executing: container show failover > > Container Scsi B:ID:L > --------- ---------------------------------- > GLOBAL 0:03:0 > 0 --- No Devices Assigned --- > > AFA0> > AFA0> > AFA0> controller show automatic_failover > Executing: controller show automatic_failover > Automatic failover ENABLED > > AFA0> > AFA0> > AFA0> (4 of 4) REMAINING QUESTIONS A. Given that `controller show automatic_failover` = ENABLED both before and after, why was it necessary for me to issue a `controller rescan` in order to make the rebuild task kick in? B. Why does `enclosure show slot` still list drive (0,3,0) as having state label 'HOTSPARE'? C. How do I get rid of the (0,2,0) drive? What I am going to try is: enclosure prepoare slot 0 2 -end of post- Cheers, Dennis -- Dennis G. Allard telephone: 1.310.399.4740 Ocean Park Software http://oceanpark.com ________________________________________________________________________ From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 29 03:45:50 2004 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 83DD016A4CE for ; Wed, 29 Sep 2004 03:45:50 +0000 (GMT) Received: from forrie.com (forrie.ne.client2.attbi.com [24.147.45.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9D8143D1F for ; Wed, 29 Sep 2004 03:45:49 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from [127.0.0.1] (i-99.forrie.net. [192.168.1.99]) by forrie.com with ESMTP id i8T3jgRm065790 for ; Tue, 28 Sep 2004 23:45:43 -0400 (EDT) (envelope-from forrie@forrie.com) Message-ID: <415A3060.1060402@forrie.com> Date: Tue, 28 Sep 2004 23:47:44 -0400 From: Forrest Aldrich User-Agent: Mozilla Thunderbird 0.8 (Windows/20040928) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.ne.client2.attbi.com) X-MailScanner-LocalNet: Found to be clean Subject: Re: Status of iSCSI 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, 29 Sep 2004 03:45:50 -0000 [Scott, sorry about the bounced mail - it was an old IP block I had, it's fixed now.] I'm working on a project that requires a scalable mail store, which is poised to support 25k users initially, but scale to 100's of thousands of users. The budget won't provide for a SAN right now; iSCSI is a little new, but unfortunately it's not supported in FreeBSD at this time. I've been looking into the storage market areas specifically of Linux and/vs FreeBSD. A Linux/NAS/iSCSI model and that of a FreeBSD/NAS/NFS model -- not sure we want to do direct storage at this time, if we did, we'd need to plan how that purchased hardware would fit into a larger plan. NAS has the advantage of being independent; some have their own OS and most have redundancies in place. I'm not sure if it's possible to dual-attach Linux or FreeBSD boxes to a FC fabric; a while ago, that wasn't possible. The front-end servers will be split up into scalable groups - ie: some servers doing SpamAssassin, some antivirus, some MTA-in and MTA-out, etc. The common denomenator, and driving factor of this design, is the backend mail store. I'd like to explore what (realistic) options FreeBSD may have here - as I dread the thought of Linux-anything in this scenario. All input/feedback welcomed. Forrest There was an implementation done by Lucent last year for 4.x, but it has a sticky license and is probably out of date. I and several others see iSCSI as something that really needs to get done, but the 3-4 months of development time is more than can be done on evenings and weekends. I would also want to do it 'right' and implement new infrastructure in CAM to accompany it rather than making it monolithic like the Lucent implementation. What kind of project do you need it for, and what kind of resources do you have right now? Scott Forrest Aldrich wrote: > I read the April 2004 report (on freebsd.org); presuming that's > up-to-date, it may be a while before we have iSCSI support in FreeBSD. > I wanted to verify here, etc. > > I'm involved in a project that will require something of that nature. > > > Thanks, > Forrest > From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 29 04:46:44 2004 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 B594316A4CE for ; Wed, 29 Sep 2004 04:46:44 +0000 (GMT) Received: from beck.quonix.net (beck.quonix.net [146.145.66.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17FEB43D48 for ; Wed, 29 Sep 2004 04:46:44 +0000 (GMT) (envelope-from john@essenz.com) Received: from [192.168.1.100] (pool-141-158-247-68.phil.east.verizon.net [141.158.247.68]) by beck.quonix.net (8.12.11/8.12.11) with ESMTP id i8T4kZ3U021569 for ; Wed, 29 Sep 2004 00:46:36 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <415A3060.1060402@forrie.com> References: <415A3060.1060402@forrie.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <4FBA10EE-11D1-11D9-B2A1-0003933DDCFA@essenz.com> Content-Transfer-Encoding: 7bit From: John Von Essen Date: Wed, 29 Sep 2004 00:37:46 -0400 To: freebsd-scsi@freebsd.org X-Mailer: Apple Mail (2.619) X-SpamAssassin-2.64-Score: 0.5/6 RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL X-MimeDefang-2.44: beck.quonix.net X-Scanned-By: MIMEDefang 2.44 Subject: Re: Status of iSCSI 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, 29 Sep 2004 04:46:44 -0000 (Forrest - Had to post to list too as my mail also bounced back) Not sure if your budget can handle it, but if I where you.... I would stick with NFS over GigE network. But go with a very robust hardened NFS soluton, like a NetApp FAS960 Fileserver. Throughput is very good, SPOF is non-existent, the disk shelves are fiber channel so you can start with 0.5Tb and scale as high (30Tb) as you want on the fly (within nfs filesystem mount limits). A good NetApp system with 1/2 a terabyte will run you around $70,000 (last time I checked). Can be lower through refurb and/or second hand markets. There are cheaper alternatives but these are no where near the performance level of the NetApp units. -john On Sep 28, 2004, at 11:47 PM, Forrest Aldrich wrote: > [Scott, sorry about the bounced mail - it was an old IP block I had, > it's fixed now.] > > I'm working on a project that requires a scalable mail store, which is > poised to support 25k users initially, but scale to 100's of thousands > of users. > > The budget won't provide for a SAN right now; iSCSI is a little new, > but unfortunately it's not supported in FreeBSD at this time. > > I've been looking into the storage market areas specifically of Linux > and/vs FreeBSD. A Linux/NAS/iSCSI model and that of a > FreeBSD/NAS/NFS model -- not sure we want to do direct storage at this > time, if we did, we'd need to plan how that purchased hardware would > fit into a larger plan. > > NAS has the advantage of being independent; some have their own OS and > most have redundancies in place. I'm not sure if it's possible to > dual-attach Linux or FreeBSD boxes to a FC fabric; a while ago, that > wasn't possible. > > The front-end servers will be split up into scalable groups - ie: some > servers doing SpamAssassin, some antivirus, some MTA-in and MTA-out, > etc. > > The common denomenator, and driving factor of this design, is the > backend mail store. I'd like to explore what (realistic) options > FreeBSD may have here - as I dread the thought of Linux-anything in > this scenario. > > All input/feedback welcomed. > > > > Forrest > > > > > > There was an implementation done by Lucent last year for 4.x, but it > has > a sticky license and is probably out of date. I and several others see > iSCSI as something that really needs to get done, but the 3-4 months of > development time is more than can be done on evenings and weekends. I > would also want to do it 'right' and implement new infrastructure in > CAM > to accompany it rather than making it monolithic like the Lucent > implementation. > > What kind of project do you need it for, and what kind of resources do > you have right now? > > Scott > > > Forrest Aldrich wrote: > > I read the April 2004 report (on freebsd.org); presuming that's > > up-to-date, it may be a while before we have iSCSI support in > FreeBSD. > > I wanted to verify here, etc. > > > > I'm involved in a project that will require something of that nature. > > > > > > Thanks, > > Forrest > > > > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > > John Von Essen (john@essenz.com) President, Essenz Consulting (www.essenz.com) Phone: (800) 248-1736 Fax: (800) 852-3387 From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 29 05:42:26 2004 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 48C4016A4CE for ; Wed, 29 Sep 2004 05:42:26 +0000 (GMT) Received: from forrie.com (forrie.ne.client2.attbi.com [24.147.45.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0EDA43D53 for ; Wed, 29 Sep 2004 05:42:25 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from [127.0.0.1] (i-99.forrie.net. [192.168.1.99]) by forrie.com with ESMTP id i8T5gHmV068440 for ; Wed, 29 Sep 2004 01:42:19 -0400 (EDT) (envelope-from forrie@forrie.com) Message-ID: <415A4BB3.3070107@forrie.com> Date: Wed, 29 Sep 2004 01:44:19 -0400 From: Forrest Aldrich User-Agent: Mozilla Thunderbird 0.8 (Windows/20040928) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.ne.client2.attbi.com) X-MailScanner-LocalNet: Found to be clean Subject: Re: Status of iSCSI 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, 29 Sep 2004 05:42:26 -0000 [ John, *.east.verizon.net is a painful source of spam for me, so it's blocked here; sorry ] We've considered the NFS route, too; and it's been a while since I've used it. I forgot about mount limitations within NFS. There are some arguments against this scenario (internally) which I will have to further gather data upon. Another concern in the design is allocating the accounts in a balanced way across the various mount points. Delicate matter - since not every user is going to have the same email habits. I'd be curious of performance stats you may have experience with on this scenario. We could could also get a NAS-type device that isn't as high-end as Netapp (Snap Appliance?). Thanks! Forrest (Forrest - Had to post to list too as my mail also bounced back) Not sure if your budget can handle it, but if I where you.... I would stick with NFS over GigE network. But go with a very robust hardened NFS soluton, like a NetApp FAS960 Fileserver. Throughput is very good, SPOF is non-existent, the disk shelves are fiber channel so you can start with 0.5Tb and scale as high (30Tb) as you want on the fly (within nfs filesystem mount limits). A good NetApp system with 1/2 a terabyte will run you around $70,000 (last time I checked). Can be lower through refurb and/or second hand markets. There are cheaper alternatives but these are no where near the performance level of the NetApp units. -john On Sep 28, 2004, at 11:47 PM, Forrest Aldrich wrote: > [Scott, sorry about the bounced mail - it was an old IP block I had, > it's fixed now.] > > I'm working on a project that requires a scalable mail store, which is > poised to support 25k users initially, but scale to 100's of thousands > of users. > > The budget won't provide for a SAN right now; iSCSI is a little new, > but unfortunately it's not supported in FreeBSD at this time. > > I've been looking into the storage market areas specifically of Linux > and/vs FreeBSD. A Linux/NAS/iSCSI model and that of a > FreeBSD/NAS/NFS model -- not sure we want to do direct storage at this > time, if we did, we'd need to plan how that purchased hardware would > fit into a larger plan. > > NAS has the advantage of being independent; some have their own OS and > most have redundancies in place. I'm not sure if it's possible to > dual-attach Linux or FreeBSD boxes to a FC fabric; a while ago, that > wasn't possible. > > The front-end servers will be split up into scalable groups - ie: some > servers doing SpamAssassin, some antivirus, some MTA-in and MTA-out, > etc. > > The common denomenator, and driving factor of this design, is the > backend mail store. I'd like to explore what (realistic) options > FreeBSD may have here - as I dread the thought of Linux-anything in > this scenario. > > All input/feedback welcomed. > > > > Forrest > > > > > > There was an implementation done by Lucent last year for 4.x, but it > has > a sticky license and is probably out of date. I and several others see > iSCSI as something that really needs to get done, but the 3-4 months of > development time is more than can be done on evenings and weekends. I > would also want to do it 'right' and implement new infrastructure in > CAM > to accompany it rather than making it monolithic like the Lucent > implementation. > > What kind of project do you need it for, and what kind of resources do > you have right now? > > Scott > > > Forrest Aldrich wrote: > > I read the April 2004 report (on freebsd.org); presuming that's > > up-to-date, it may be a while before we have iSCSI support in > FreeBSD. > > I wanted to verify here, etc. > > > > I'm involved in a project that will require something of that nature. > > > > > > Thanks, > > Forrest > > > > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > > John Von Essen (john@essenz.com) President, Essenz Consulting (www.essenz.com) Phone: (800) 248-1736 Fax: (800) 852-3387 From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 29 11:13:08 2004 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 6BD3716A4CE for ; Wed, 29 Sep 2004 11:13:08 +0000 (GMT) Received: from email.eurowings.com (email.eurowings.com [193.96.182.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25F1743D53 for ; Wed, 29 Sep 2004 11:13:08 +0000 (GMT) (envelope-from h.kipp@eurowings.com) Received: from localhost (localhost [127.0.0.1]) by email.eurowings.com (Postfix) with ESMTP id 0F71614E240; Wed, 29 Sep 2004 13:13:07 +0200 (CEST) Received: from eurowings.com (unknown [10.100.24.81]) by email.eurowings.com (Postfix) with ESMTP id 0AD9414E1A9; Wed, 29 Sep 2004 13:13:05 +0200 (CEST) Message-ID: <415A98C0.2030005@eurowings.com> Date: Wed, 29 Sep 2004 13:13:04 +0200 From: Holger Kipp User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040602 X-Accept-Language: de, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at eurowings.com Subject: Interesting SCSI-Problem with Quantum Atlas10K3 (from freebsd-stable) 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, 29 Sep 2004 11:13:08 -0000 Hello, maybe someone could help me a bit with this. OS is FreeBSD 4.10 , .. , 4.2 Questions at the end. 3 SCSI-Harddisks (Quantum ATLAS10K3) as Raid5 (vinum) produce the following errors on current hardware (ie LSI mtp-controller dual channel U320) - it takes a few file operations, though: mpt0: bullet missed in timeout mpt1: bullet missed in timeout (offending disks are located at mpt) I/O-Performance is ok, but a simple 'find' that is running through all directories will bring the system to a near-halt after half a minute or so. Copying a 90MB file on the vinum-raid works like a charm and does not trigger this behaviour. I tried reducing / disabling tagged queueing, but that did not help Even added an entry in cam_xpt.c with /*quirks*/0, /*mintags*/24, /*maxtags*/32 which seemed to worsen the effect. According to the datasheet I just found. These disks have a queue depth of 64. Mounting the drives (or the vinum-drive) read-only gives no errors, and rebuilding the array does not give an error either. So it looks like I need many consecutive read- and write- operations to trigger this behaviour (like with find, changing access times of directories). I have not found any possibility of updating the firmware either, so any clue is welcome. Disks located at mpt0 do not show any problems, even with buildworld. I had similar problems with the same disks on older hardware (Asus P2B-S) with FreeBSD 4-2, then upgraded to 4.10-STABLE and changed all the hardware except for the harddisks. - Anyone else who had these problems? - How can I find out on what drive the command queue grows indefinitely (till the system halts completely), if this is at all the case? - can I tune FreeBSD in this respect? - what are the exact meanings of mintags and maxtags and should I try something like /*quirks*/0, /*mintags*/2, /*maxtags*/64 ? - ... Hints on how to use camdebug in this case are also welcome! Best regards, Holger Kipp From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 29 15:12:16 2004 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 485E216A4CE for ; Wed, 29 Sep 2004 15:12:16 +0000 (GMT) Received: from beck.quonix.net (beck.quonix.net [146.145.66.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0A0E43D48 for ; Wed, 29 Sep 2004 15:12:15 +0000 (GMT) (envelope-from john@essenz.com) Received: from [192.168.1.100] (pool-141-158-247-68.phil.east.verizon.net [141.158.247.68]) by beck.quonix.net (8.12.11/8.12.11) with ESMTP id i8TFC9UP029280 for ; Wed, 29 Sep 2004 11:12:09 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <415A4BB3.3070107@forrie.com> References: <415A4BB3.3070107@forrie.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: John Von Essen Date: Wed, 29 Sep 2004 11:03:22 -0400 To: freebsd-scsi@freebsd.org X-Mailer: Apple Mail (2.619) X-SpamAssassin-2.64-Score: 0.5/6 RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL X-MimeDefang-2.44: beck.quonix.net X-Scanned-By: MIMEDefang 2.44 Subject: Re: Status of iSCSI 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, 29 Sep 2004 15:12:16 -0000 Sent to list since I cant email you.... I would check your spam filters, something is not working correctly. My home pc is on verizon DSL, however, I dont run a mail server here, I relay mail to a legit mail server (146.145.66.90/quonix.net) for delivery. So when my email comes to you the "relay IP" should be the 146 number, not the verizon number. Though the verizon IP will appear somewhere in the email header as the origin - but you cant really block email like that. Your effectively blocking email from every single East Coast Verizon user. -john On Sep 29, 2004, at 1:44 AM, Forrest Aldrich wrote: > [ John, *.east.verizon.net is a painful source of spam for me, so it's > blocked here; sorry ] > > We've considered the NFS route, too; and it's been a while since I've > used it. From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 29 20:12:46 2004 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 5FC1516A4CE for ; Wed, 29 Sep 2004 20:12:46 +0000 (GMT) Received: from web21425.mail.yahoo.com (web21425.mail.yahoo.com [216.136.232.44]) by mx1.FreeBSD.org (Postfix) with SMTP id 53C4143D39 for ; Wed, 29 Sep 2004 20:12:46 +0000 (GMT) (envelope-from mjacob44@yahoo.com) Message-ID: <20040929201246.55598.qmail@web21425.mail.yahoo.com> Received: from [146.174.53.5] by web21425.mail.yahoo.com via HTTP; Wed, 29 Sep 2004 13:12:46 PDT Date: Wed, 29 Sep 2004 13:12:46 -0700 (PDT) From: Matthew Jacob To: Holger Kipp , freebsd-scsi@freebsd.org In-Reply-To: <415A98C0.2030005@eurowings.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Interesting SCSI-Problem with Quantum Atlas10K3 (from freebsd-stable) 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, 29 Sep 2004 20:12:46 -0000 It's not a command queue length issue. The message indicates that we had a disk command timeout that when we turned around and called the interrupt service routine that the command did get serviced after all. You didn't say what kind of MPT h/w you're running on. __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail From owner-freebsd-scsi@FreeBSD.ORG Thu Sep 30 11:57:08 2004 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 0861B16A4CE for ; Thu, 30 Sep 2004 11:57:08 +0000 (GMT) Received: from mx01.ewc.edu (mx01.ewc.edu [68.152.80.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8489343D53 for ; Thu, 30 Sep 2004 11:57:05 +0000 (GMT) (envelope-from mjoyner@vbservices.net) Received: from [192.168.4.160] (host-161.firewall.ewc.edu [68.152.80.161]) by mx01.ewc.edu (8.12.9p2/8.12.9) with ESMTP id i8UBuqxS084217; Thu, 30 Sep 2004 07:56:52 -0400 (EDT) (envelope-from mjoyner@vbservices.net) Message-ID: <415BF47F.6070209@vbservices.net> Date: Thu, 30 Sep 2004 07:56:47 -0400 From: Michael Joyner User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040906 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Forrest Aldrich References: <415A4BB3.3070107@forrie.com> In-Reply-To: <415A4BB3.3070107@forrie.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new cc: freebsd-scsi@freebsd.org Subject: Re: Status of iSCSI 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: Thu, 30 Sep 2004 11:57:08 -0000 > I'd be curious of performance stats you may have experience with on this > scenario. We could could also get a NAS-type device that isn't as > high-end as > Netapp (Snap Appliance?). > Snap Servers are *EVIL* Run Away! From owner-freebsd-scsi@FreeBSD.ORG Thu Sep 30 16:16:28 2004 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 C1C6916A4CE for ; Thu, 30 Sep 2004 16:16:28 +0000 (GMT) Received: from forrie.com (forrie.ne.client2.attbi.com [24.147.45.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 103C143D55 for ; Thu, 30 Sep 2004 16:16:26 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from [127.0.0.1] (i-99.forrie.net. [192.168.1.99]) by forrie.com with ESMTP id i8UGGHwu021930; Thu, 30 Sep 2004 12:16:19 -0400 (EDT) (envelope-from forrie@forrie.com) Message-ID: <415C31CB.2070407@forrie.com> Date: Thu, 30 Sep 2004 12:18:19 -0400 From: Forrest Aldrich User-Agent: Mozilla Thunderbird 0.8 (Windows/20040928) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Joyner References: <415A4BB3.3070107@forrie.com> <415BF47F.6070209@vbservices.net> In-Reply-To: <415BF47F.6070209@vbservices.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.ne.client2.attbi.com) X-MailScanner-LocalNet: Found to be clean cc: freebsd-scsi@freebsd.org Subject: Re: Status of iSCSI 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: Thu, 30 Sep 2004 16:16:28 -0000 Care to qualify that statement? (ie: back it up with useful information, and not rhetoric ;-)) Michael Joyner wrote: >> I'd be curious of performance stats you may have experience with on >> this scenario. We could could also get a NAS-type device that isn't >> as high-end as >> Netapp (Snap Appliance?). >> > > Snap Servers are *EVIL* > Run Away! From owner-freebsd-scsi@FreeBSD.ORG Thu Sep 30 16:43:59 2004 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 8BA1716A4CE for ; Thu, 30 Sep 2004 16:43:59 +0000 (GMT) Received: from mx01.ewc.edu (mx01.ewc.edu [68.152.80.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C33A43D1F for ; Thu, 30 Sep 2004 16:43:59 +0000 (GMT) (envelope-from mjoyner@vbservices.net) Received: from [192.168.4.160] (host-161.firewall.ewc.edu [68.152.80.161]) by mx01.ewc.edu (8.12.9p2/8.12.9) with ESMTP id i8UGhexS091074; Thu, 30 Sep 2004 12:43:40 -0400 (EDT) (envelope-from mjoyner@vbservices.net) Message-ID: <415C37B6.7050503@vbservices.net> Date: Thu, 30 Sep 2004 12:43:34 -0400 From: Michael Joyner User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040906 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Forrest Aldrich References: <415A4BB3.3070107@forrie.com> <415BF47F.6070209@vbservices.net> <415C31CB.2070407@forrie.com> In-Reply-To: <415C31CB.2070407@forrie.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new cc: freebsd-scsi@freebsd.org Subject: Re: Status of iSCSI 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: Thu, 30 Sep 2004 16:43:59 -0000 NFS EXPORTS must be configured manually per ip per uid so if you have 15 UIDS you need to map ownership on files via NFS to say 5 workstations you have to do 15*5 configurations via a webform. will not talk Windows 2003 AD I have 3 here (bought before my time), and absolutely hate them. Forrest Aldrich wrote: > Care to qualify that statement? (ie: back it up with useful information, > and not rhetoric ;-)) > > > > > Michael Joyner wrote: > >>> I'd be curious of performance stats you may have experience with on >>> this scenario. We could could also get a NAS-type device that isn't >>> as high-end as >>> Netapp (Snap Appliance?). >>> >> >> Snap Servers are *EVIL* >> Run Away! > > From owner-freebsd-scsi@FreeBSD.ORG Thu Sep 30 16:47:17 2004 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 848EB16A4CE for ; Thu, 30 Sep 2004 16:47:17 +0000 (GMT) Received: from forrie.com (forrie.ne.client2.attbi.com [24.147.45.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2600143D58 for ; Thu, 30 Sep 2004 16:47:17 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from [127.0.0.1] (i-99.forrie.net. [192.168.1.99]) by forrie.com with ESMTP id i8UGl79I022738; Thu, 30 Sep 2004 12:47:11 -0400 (EDT) (envelope-from forrie@forrie.com) Message-ID: <415C3904.8030004@forrie.com> Date: Thu, 30 Sep 2004 12:49:08 -0400 From: Forrest Aldrich User-Agent: Mozilla Thunderbird 0.8 (Windows/20040928) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Joyner References: <415A4BB3.3070107@forrie.com> <415BF47F.6070209@vbservices.net> <415C31CB.2070407@forrie.com> <415C37B6.7050503@vbservices.net> In-Reply-To: <415C37B6.7050503@vbservices.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.ne.client2.attbi.com) X-MailScanner-LocalNet: Found to be clean cc: freebsd-scsi@freebsd.org Subject: Re: Status of iSCSI 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: Thu, 30 Sep 2004 16:47:17 -0000 I see. Our application would be to a backend mailstore - so there would be only the mail-related "ids" that would connect... so I don't know that this would apply. However, we're preferring to use iSCSI - which may require an OS change unfortunately, unless we find another means. Can someone here make a recommendation. To keep FreeBSD at the front-end, we'd have to go fibre, but that's a little out of my experience, and I've been told there are issues with multiple connections to a FC share (or something of that nature). _F Michael Joyner wrote: > NFS EXPORTS must be configured manually per ip per uid > > so if you have 15 UIDS you need to map ownership on files via NFS to > say 5 workstations you have to do 15*5 configurations via a webform. > > will not talk Windows 2003 AD > > I have 3 here (bought before my time), and absolutely hate them. > > Forrest Aldrich wrote: > >> Care to qualify that statement? (ie: back it up with useful >> information, and not rhetoric ;-)) >> >> >> >> >> Michael Joyner wrote: >> >>>> I'd be curious of performance stats you may have experience with on >>>> this scenario. We could could also get a NAS-type device that >>>> isn't as high-end as >>>> Netapp (Snap Appliance?). >>>> >>> >>> Snap Servers are *EVIL* >>> Run Away! >> >> >> From owner-freebsd-scsi@FreeBSD.ORG Sat Oct 2 17:38:03 2004 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 48AFB16A4CE for ; Sat, 2 Oct 2004 17:38:03 +0000 (GMT) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D46443D49 for ; Sat, 2 Oct 2004 17:38:03 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id CBE04491E4E for ; Sat, 2 Oct 2004 14:37:58 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 07723-08 for ; Sat, 2 Oct 2004 17:37:58 +0000 (GMT) Received: from ganymede.hub.org (blk-222-46-91.eastlink.ca [24.222.46.91]) by hub.org (Postfix) with ESMTP id 186BB491C27 for ; Sat, 2 Oct 2004 14:15:48 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id C7D5437DE5; Sat, 2 Oct 2004 14:15:47 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id C4503365C6 for ; Sat, 2 Oct 2004 14:15:47 -0300 (ADT) Date: Sat, 2 Oct 2004 14:15:47 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-scsi@freebsd.org Message-ID: <20041002140359.A64687@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Subject: power issues cause drives to 'disappear' 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: Sat, 02 Oct 2004 17:38:03 -0000 I have 5 servers running right now ... 3 with hardware raid, 2 with vinum ... all RAID5 ... and I'm getting some odd behaviour that I really can't explain ... All the servesr are using Seagate drives ... one is using 72G ones, the others all 36G, same models ... all hot swap ... neptune (72g drives), about a month ago or so, one drive went "stale" ... I had screwed up when I build the vinum array, and did it as a concat vs raid5, so lost everything ... my fault ... but, when I rebuilt it as raid5, I included all the drives, including teh one that said it had 'gone bad' ... mars (36G drives), same thing ... drive on a raid5 went "stale" ... ran a vinum start on the drive, everything came back fine and periodic checks showed it as being fine ... today, pluto, 36G drives with an iir controller "lost a drive" ... I'm suspecting that if I 'revive' it (assuming I can figure out how to), it too will prove to be fine ... If the drive didn't revive, then I'd think bad hard drive ... but they are, and run fine afterwards ... Now, unfortunately, I just checked both mars/neptune, and see taht I have again a stale drive on each ... I didn't think last time to record which drive was stale, so don't know if its the same ones :( I'm going to do that this time though ... So, the question is ... would a power 'flux' cause something like this? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-scsi@FreeBSD.ORG Sat Oct 2 17:40:39 2004 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 44D3C16A4CE for ; Sat, 2 Oct 2004 17:40:39 +0000 (GMT) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1926543D1D for ; Sat, 2 Oct 2004 17:40:39 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id F26AE4917A9 for ; Sat, 2 Oct 2004 14:40:36 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 11308-04 for ; Sat, 2 Oct 2004 17:40:36 +0000 (GMT) Received: from ganymede.hub.org (unknown [24.222.46.91]) by hub.org (Postfix) with ESMTP id B6932491B85 for ; Sat, 2 Oct 2004 13:54:44 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 63816365FE; Sat, 2 Oct 2004 13:53:28 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 5FE24365C6 for ; Sat, 2 Oct 2004 13:53:28 -0300 (ADT) Date: Sat, 2 Oct 2004 13:53:28 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-scsi@freebsd.org Message-ID: <20041002135254.R64687@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Subject: MPI returned on iir driver ... 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: Sat, 02 Oct 2004 17:40:39 -0000 Can someone tell me what this means? Oct 2 03:14:20 pluto /kernel: iir0: SCSI-B, ID 1: MPI returned 0x0000004B Oct 2 03:14:20 pluto /kernel: iir0: SCSI-B, ID 1: MPI returned 0x0000004B Oct 2 03:14:20 pluto /kernel: iir0: SCSI-B, ID 0: MPI returned 0x0000004B Oct 2 03:14:20 pluto /kernel: iir0: SCSI-B, ID 4: MPI returned 0x0000004B Oct 2 03:14:20 pluto /kernel: iir0: SCSI-B, ID 3: MPI returned 0x0000004B Oct 2 03:14:20 pluto /kernel: iir0: SCSI-B, ID 3: MPI returned 0x0000004B Thanks ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-scsi@FreeBSD.ORG Sat Oct 2 20:06:08 2004 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 6065316A4CE for ; Sat, 2 Oct 2004 20:06:08 +0000 (GMT) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 362B743D48 for ; Sat, 2 Oct 2004 20:06:08 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id E530C48FFC8 for ; Sat, 2 Oct 2004 17:06:04 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 62874-10 for ; Sat, 2 Oct 2004 20:06:04 +0000 (GMT) Received: from ganymede.hub.org (blk-222-46-91.eastlink.ca [24.222.46.91]) by hub.org (Postfix) with ESMTP id 7095B48FFC1 for ; Sat, 2 Oct 2004 17:06:04 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 23B9E36DE5; Sat, 2 Oct 2004 17:06:06 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 22C5836D73 for ; Sat, 2 Oct 2004 17:06:06 -0300 (ADT) Date: Sat, 2 Oct 2004 17:06:06 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-scsi@freebsd.org Message-ID: <20041002170505.T64687@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Subject: scsi drive going offline ... heat? 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: Sat, 02 Oct 2004 20:06:08 -0000 someone just mentioned to me that if a drive gets too hot, the raid controller can detect that and 'power it down', which might account for the one going down this morning ... could/would the drive itself be able to do that, so that vinum would see it going down? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664