From owner-freebsd-scsi Sun May 13 8:17:41 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from smarthost1.mail.easynet.fr (smarthost1.mail.easynet.fr [212.180.1.68]) by hub.freebsd.org (Postfix) with ESMTP id E078C37B424 for ; Sun, 13 May 2001 08:17:37 -0700 (PDT) (envelope-from fonvi@easynet.fr) Received: from smtp1.mail.easynet.fr (slb-1-sippriv.mail.easynet.fr [10.0.1.57]) by smarthost1.mail.easynet.fr (Postfix) with ESMTP id 8AAB0B6D0 for ; Sun, 13 May 2001 17:17:36 +0200 (CEST) Received: from vobiscum.styx.org (adsl-4-42.adsl.easynet.fr [195.114.94.42]) by smtp1.mail.easynet.fr (Postfix) with ESMTP id 57B3DB6A8 for ; Sun, 13 May 2001 17:17:34 +0200 (CEST) Received: (from marc@localhost) by vobiscum.styx.org (8.11.3/8.9.3/ - 6/08/98) id f4DFLPW15841 for freebsd-scsi@freebsd.org; Sun, 13 May 2001 17:21:25 +0200 (CEST) (envelope-from marc) Date: Sun, 13 May 2001 17:21:25 +0200 From: Marc Fonvieille To: freebsd-scsi@freebsd.org Subject: aic(4) driver support on 4.X ? Message-ID: <20010513172125.A15589@vobiscum.styx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Useless-Header: Black Metal inc. X-Operating-System: FreeBSD 4.3-STABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I've got an Adaptec AVA1505 scsi card running fine with FreeBSD 3.5-Stable. Under 4.3-Stable with the following line in the kernel config: device aic0 at isa? the card isn't detected. It gives me the same result if i set port and irq in the kernel config. I noticed some changes on Current's source tree for this driver, maybe it could help me. Could someone MFC these changes? Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 14 11: 7: 6 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from relay.ioffe.rssi.ru (relay.ioffe.rssi.ru [194.85.224.33]) by hub.freebsd.org (Postfix) with ESMTP id 6298937B422 for ; Mon, 14 May 2001 11:07:03 -0700 (PDT) (envelope-from kopts@astro.ioffe.rssi.ru) Received: from astro.ioffe.rssi.ru (astro.ioffe.rssi.ru [194.85.229.130]) by relay.ioffe.rssi.ru (8.9.1/8.9.1) with ESMTP id WAA23237 for ; Mon, 14 May 2001 22:07:00 +0400 (MSD) Received: by astro.ioffe.rssi.ru (8.9.3/Clnt-2.14-AS-eef) id WAA92044; Mon, 14 May 2001 22:05:22 +0400 (MSD) Date: Mon, 14 May 2001 22:05:22 +0400 (MSD) From: Alexey Koptsevich To: scsi@freebsd.org Subject: 3ware patch Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, 3ware has released a patch for both firmware and software, Linux and Windows, for RAID5 mode of their controllers. Is FreeBSD driver believed to be free of errors? http://www.3ware.com/support/swlibrary.shtml Thanks, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 14 11:55: 5 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id B0C8337B423 for ; Mon, 14 May 2001 11:55:02 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f4EJ1SG01151; Mon, 14 May 2001 12:01:44 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200105141901.f4EJ1SG01151@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexey Koptsevich Cc: scsi@freebsd.org Subject: Re: 3ware patch In-reply-to: Your message of "Mon, 14 May 2001 22:05:22 +0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 May 2001 12:01:28 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > 3ware has released a patch for both firmware and software, Linux and > Windows, for RAID5 mode of their controllers. Is FreeBSD driver believed > to be free of errors? > > http://www.3ware.com/support/swlibrary.shtml I'm not aware of the actual nature of the problem yet; my technical contact at 3ware was just laid off, and I'm still trying to find a new one. I'll be analysing the Linux driver change this week, and will make any corresponding modifications as soon as I do. Until then, read the details of the problem as reported by 3ware and avoid the situations they describe as being problematic. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 15 1:10:21 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 30F5237B422 for ; Tue, 15 May 2001 01:10:03 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f4ENTcO01438; Mon, 14 May 2001 16:29:39 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200105142329.f4ENTcO01438@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexey Koptsevich Cc: scsi@FreeBSD.org Subject: Re: 3ware patch In-reply-to: Your message of "Mon, 14 May 2001 22:05:22 +0400." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Mon, 14 May 2001 16:29:37 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > = > Hello, > = > 3ware has released a patch for both firmware and software, Linux and > Windows, for RAID5 mode of their controllers. Is FreeBSD driver believe= d > to be free of errors? I've just exchanged email with my new technical contact at 3ware, and the= = problem as it's been explained to me will not affect FreeBSD. Here's the relevant sections from the mail describing the issue: ----8<---- RAID5 writes can result in corrupted parity.=A0 The data itself is not corrupted -- only the parity.=A0 The current Raid5 firmware performs _TWO= _ PCI accesses -- one for data, one for parity calculation.=A0 Thus if physical memory has changed before the second PCI access has completed, parity will be corrupted.=A0 This was a very bad oversight and has been corrected in the 7000, which only performs one PCI access. Linux ext2 FS performs a "fire and forget" on metadata.=A0 (Last write is= always the best write)=A0 These writes are asynchronous and never wait fo= r a completion. ----8<---- Since the FreeBSD block driver abstraction guarantees that data will not = be changed out from under the driver, there is no opportunity for this = limitation of the RAID implementation to cause problems. Note also that I've been informed that the 7000 series controllers will = not require the double-read behaviour, which should improve their RAID5 = performance considerably. -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 15 7:22:43 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from kumquat.hlcca.org (kumquat.hlcca.org [209.244.192.145]) by hub.freebsd.org (Postfix) with SMTP id 7663437B424 for ; Tue, 15 May 2001 07:22:24 -0700 (PDT) (envelope-from dakota@kumquat.hlcca.org) Received: (qmail 797 invoked by uid 143); 15 May 2001 10:21:32 -0000 Received: from localhost (HELO kumquat.hlcca.org) (sendmail-bs@127.0.0.1) by localhost with SMTP; 15 May 2001 10:21:32 -0000 X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Alfred Perlstein Cc: freebsd-stable@FreeBSD.ORG, freebsd-scsi@freebsd.org, jkikpole@cairodurham.org From: lists@mediumgreen.com Subject: Re: Random (?) kernel panics In-Reply-To: Message from Alfred Perlstein of "Tue, 08 May 2001 09:16:10 MST." <20010508091610.J18676@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 May 2001 10:21:32 +0000 Message-Id: <20010515142224.7663437B424@hub.freebsd.org> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I think I heard Alfred Perlstein say: >* lists@mediumgreen.com [010508 07:01] wrote: >> >> I cvsup'd to the latest stable on Friday and installed a new kernel >> yesterday and got another panic with the same message (supervisor write, >> page not present). My panic's NEVER can complete sync'ing the disks, so >> I don't ever get core's. Jaime got a core from his pacnic's with the >> same message, though. >> >> Does anyone have any suggestions on what do next? This machine has been >> down for an average of 5 hours per week since this started happening - >> my users are getting kinda antsy (sp?). > >Can you at least get a DDB traceback? Got another panic today - this time I had DDB in my kernel, so I've got more information. It sounds related to SCSI, so I'm including this message to freebsd-scsi. I apologize if there are typo's here - I wrote the information down and am typing it back in since I didn't know how (or if) I could get DDB to log to a file. sym0:4: message c sent on bad reselection. panic: assertion "i && sym_get_cam_status(cp->cam_ccb) == CAM_REQUEUE_REQ" failed: file "/usr/local/src/system/sys/dev/sym/sym_hipd.c", line 5204 Debugger("panic") Stopped at Debugger+0x34: movb $0,in_Debugger.396 db> trace Debugger(c0343863) at Debugger+0x34 panic(c0356a40, c0357200, c03569c0, 1454, c116100) at panic+0x70 sym_sir_task_recover(c116100, 7, c116100, 0, 7000286) at sym_sir_task_recovery+0x244 sym_int_sir(c1161000, c1e590c, 400000, c127c84, c01b5911) at sym_int_sir+0x73 sym_intr1(c116100, cd039f78, c02fc6f2, c1161000, 67049a) at sym_intr+0xd1 sym_intr(c116100, 67049a, 10, 10, 10) at sym_intr+0xb Xresume12() at Xresume12+0x2b --- interrupt, eip=0xc01f0a2d, esp=0xcd039f68, ebp=0xcd039f78 --- if_slotime(0, 400000, 2b0e, 8b1780c, 6) at if_slowtime+0x1d softclock(0, 2f, 2f, 2f, 6) at softclock+0xd1 doreti_swi() at doreti+0xf db> % dmesg Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-STABLE #4: Tue May 8 12:28:21 GMT 2001 dakota@kumquat.hlcca.org:/usr/obj/usr/local/src/system/sys/kumquat Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) Processor (908.09-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ff AMD Features=0xc0440000<,AMIE,DSP,3DNow!> real memory = 268353536 (262064K bytes) avail memory = 256954368 (250932K bytes) Preloaded elf kernel "kernel" at 0xc0440000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pci1: at 0.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 pci0: at 4.1 uhci0: port 0xd400-0xd41f irq 5 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 5 at device 4.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub2: ALCOR Generic USB Hub, class 9/0, rev 1.10/1.00, addr 2 uhub2: 4 ports with 4 removable, self powered sym0: <895> port 0xa400-0xa4ff mem 0xd6000000-0xd6000fff,0xd6800000-0xd68000ff irq 12 at device 10.0 on pci0 sym0: Tekram NVRAM, ID 7, Fast-40, SE, parity checking rl0: port 0xa000-0xa0ff mem 0xd5800000-0xd58000ff irq 10 at device 11.0 on pci0 rl0: Ethernet address: 00:e0:29:6f:69:43 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: (vendor=0x105a, dev=0x0d30) at 17.0 irq 10 pcib1: on motherboard pci2: on pcib1 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. sa0 at sym0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 8) da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) Mounting root from ufs:/dev/da0s1a ch0 at sym0 bus 0 target 4 lun 1 ch0: Removable Changer SCSI-2 device ch0: 10.000MB/s transfers (10.000MHz, offset 8) ch0: 6 slots, 1 drive, 0 pickers, 0 portals from /var/log/messages: May 15 02:35:36 kumquat /kernel: sym0:4: message c sent on bad reselection. May 15 09:11:24 kumquat /kernel: sym0: <895> port 0xa400-0xa4ff mem 0xd6000000-0xd6000fff,0xd6800000-0xd68000ff irq 12 at device 10.0 on pci0 May 15 09:11:24 kumquat /kernel: sym0: Tekram NVRAM, ID 7, Fast-40, SE, parity checking May 15 09:11:24 kumquat /kernel: Waiting 15 seconds for SCSI devices to settle May 15 09:11:24 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. May 15 09:11:24 kumquat /kernel: sa0 at sym0 bus 0 target 4 lun 0 May 15 09:11:24 kumquat /kernel: sa0: Removable Sequential Access SCSI-2 device May 15 09:11:24 kumquat /kernel: sa0: 10.000MB/s transfers (10.000MHz, offset 8) May 15 09:11:24 kumquat /kernel: da0 at sym0 bus 0 target 0 lun 0 May 15 09:11:24 kumquat /kernel: da0: Fixed Direct Access SCSI-3 device May 15 09:11:24 kumquat /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled May 15 09:11:24 kumquat /kernel: da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) May 15 09:11:24 kumquat /kernel: Mounting root from ufs:/dev/da0s1a May 15 09:11:24 kumquat /kernel: ch0 at sym0 bus 0 target 4 lun 1 May 15 09:11:24 kumquat /kernel: ch0: Removable Changer SCSI-2 device May 15 09:11:24 kumquat /kernel: ch0: 10.000MB/s transfers (10.000MHz, offset 8) May 15 09:11:24 kumquat /kernel: ch0: 6 slots, 1 drive, 0 pickers, 0 portals Any ideas on what I can do next? I also wanted to thank everyone for all their help so far. -matthew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 16 12: 8:53 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 6176037B422 for ; Wed, 16 May 2001 12:08:50 -0700 (PDT) (envelope-from haribeau@gmx.de) Received: (qmail 31423 invoked by uid 0); 16 May 2001 19:08:49 -0000 Received: from pd950542a.dip.t-dialin.net (HELO pcch) (217.80.84.42) by mail.gmx.net (mail02) with SMTP; 16 May 2001 19:08:49 -0000 Message-ID: <002401c0de3b$69c886c0$3301a8c0@pcch> From: "Clemens Hermann" To: Subject: mly problem (AR 170) Date: Wed, 16 May 2001 21:07:12 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, today I installed a mylex AcceleRaid 170 on FreeBSD 4.3 Release. I have two mirrors which worked right out of the box (da0/da1). The only problem: when I boot the system I get the following messages: mly0: physical device 0:6 gone mly0: physical device 0:6 gone mly0: enclosure 6 unit 0 access offlinemly0: physical device 0:6 gone mly0: physical device 0:6 gone There does no such disk exist, according to the controller-setup this is the processor. Are these messages a problem? Furthermore: - How can I check the status of the controller/devices? - How will I know when a drive fails? - do any userland tools exist? - is there any docu available? thanks in advance for any hints /ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 16 13:46:57 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id CB4A837B424 for ; Wed, 16 May 2001 13:46:53 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id PAA04117; Wed, 16 May 2001 15:46:50 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Wed, 16 May 2001 15:46:50 -0500 (CDT) From: Chris Dillon To: Clemens Hermann Cc: Subject: Re: mly problem (AR 170) In-Reply-To: <002401c0de3b$69c886c0$3301a8c0@pcch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 16 May 2001, Clemens Hermann wrote: > today I installed a mylex AcceleRaid 170 on FreeBSD 4.3 Release. I > have two mirrors which worked right out of the box (da0/da1). The > only problem: when I boot the system I get the following messages: > > mly0: physical device 0:6 gone > mly0: physical device 0:6 gone > mly0: enclosure 6 unit 0 access offlinemly0: physical device 0:6 gone > mly0: physical device 0:6 gone > > There does no such disk exist, according to the controller-setup > this is the processor. Are these messages a problem? Shouldn't be. I had problems with the enclosure management processor on the system I'm using, but Mike Smith fixed the mly driver recently and alleviated the problem. That fix should be in 4.3-RELEASE, I believe. > Furthermore: > - How can I check the status of the controller/devices? > - How will I know when a drive fails? > - do any userland tools exist? > - is there any docu available? No userland tools exist yet to manage the controller and its devices, that I know of. With a managed hot-plug enclosure, I'm not sure that you would even need any. I do know that the driver (via the kernel) will emit a warning when a RAID array goes critical. You can test it yourself by simply removing a drive from your redundant array, assuming you have a hot-plug setup. I've done this to test things out, and it works great. As long as you have the controller set up to do automatic rebuilds you should only have to replace the drive and wait for the array to be rebuilt. Once that is done, you will be notified when the array is optimal again. Here is some dmesg output from a system that booted up with a drive missing from its RAID array, and then automatically rebuilt the array when I inserted the new drive, all while the system was going about its normal business: mly0: mem 0xfc5fe000-0xfc5fffff irq 10 at device 1.1 on pci2 mly0: AcceleRAID 170 , 1 channel, firmware 6.00-7-00 (20001214), 32MB RAM da0 at mly0 bus 1 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 135.168MB/s transfers da0: 17480MB (35799040 512 byte sectors: 255H 63S/T 2228C) [ The system is booted and multiuser. Now, I insert the replacement drive...] mly0: physical device 0:1 found mly0: physical device 0:1 automatic rebuild started mly0: logical device 0 (da0) automatic rebuild started [ Many minutes pass while the array is rebuilt... ] mly0: logical device 0 (da0) rebuild completed mly0: physical device 0:1 rebuild completed mly0: physical device 0:1 online mly0: logical device 0 (da0) online -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 17 0:45:47 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mailout00.sul.t-online.com (mailout00.sul.t-online.com [194.25.134.16]) by hub.freebsd.org (Postfix) with ESMTP id 379C037B423 for ; Thu, 17 May 2001 00:45:44 -0700 (PDT) (envelope-from haribeau@gmx.de) Received: from fwd04.sul.t-online.de by mailout00.sul.t-online.com with smtp id 150ITq-0006h8-04; Thu, 17 May 2001 09:45:54 +0200 Received: from ramses.local (320080844193-0001@[62.225.210.102]) by fmrl04.sul.t-online.com with esmtp id 150IU2-1Z9UJcC; Thu, 17 May 2001 09:46:06 +0200 Received: from haribeau by ramses.local with local (Exim 3.12 #1 (Debian)) id 150KJO-0000SY-00; Thu, 17 May 2001 11:43:14 +0200 Date: Thu, 17 May 2001 11:43:14 +0200 From: Clemens Hermann To: Chris Dillon Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: mly problem (AR 170) Message-ID: <20010517114314.A1714@ramses.local> References: <002401c0de3b$69c886c0$3301a8c0@pcch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: von Chris Dillon am 16.Mai.2001 um 15:46:50 (-0500) X-Mailer: Mutt 1.2.5i (Linux 2.2.17 i586) X-Sender: 320080844193-0001@t-dialin.net Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Am 16.05.2001 um 15:46:50 schrieb Chris Dillon: Hi Chris, > > There does no such disk exist, according to the controller-setup > > this is the processor. Are these messages a problem? > > Shouldn't be. could you give me a hint what this messages mean? > No userland tools exist yet to manage the controller and its devices, > that I know of. With a managed hot-plug enclosure, I'm not sure that > you would even need any. I do know that the driver (via the kernel) > will emit a warning when a RAID array goes critical. You can test it > yourself by simply removing a drive from your redundant array, yes it works but I get the following lies in syslog: mly0: physical device 0:0 selection timeout mly0: logical device 0(da0) critical mly0: unknown event code-61 mly0: unknown event code-162 any ideas what the last two lines mean? Furthermore: Will I get the messages only in syslog or will they appear in the FreeBSD daily report mails? If not, is there a way to get them there? tia /ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 17 1: 5:48 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mailout00.sul.t-online.com (mailout00.sul.t-online.com [194.25.134.16]) by hub.freebsd.org (Postfix) with ESMTP id 3AEB337B423 for ; Thu, 17 May 2001 01:05:46 -0700 (PDT) (envelope-from haribeau@gmx.de) Received: from fwd07.sul.t-online.de by mailout00.sul.t-online.com with smtp id 150InE-00007V-0B; Thu, 17 May 2001 10:05:56 +0200 Received: from ramses.local (320080844193-0001@[62.225.210.102]) by fmrl07.sul.t-online.com with esmtp id 150InE-2Dc9UuC; Thu, 17 May 2001 10:05:56 +0200 Received: from haribeau by ramses.local with local (Exim 3.12 #1 (Debian)) id 150Kcw-0000VQ-00; Thu, 17 May 2001 12:03:26 +0200 Date: Thu, 17 May 2001 12:03:26 +0200 From: Clemens Hermann To: Chris Dillon Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: mly problem (AR 170) Message-ID: <20010517120326.A1925@ramses.local> References: <002401c0de3b$69c886c0$3301a8c0@pcch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: von Chris Dillon am 16.Mai.2001 um 15:46:50 (-0500) X-Mailer: Mutt 1.2.5i (Linux 2.2.17 i586) X-Sender: 320080844193-0001@t-dialin.net Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Chris, one thing else: Is it normal that my mly0 controller is not listed in /dev? /ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 17 10: 2:29 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id EDF2A37B422 for ; Thu, 17 May 2001 10:02:25 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id MAA18861; Thu, 17 May 2001 12:02:22 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 17 May 2001 12:02:21 -0500 (CDT) From: Chris Dillon To: Clemens Hermann Cc: , Subject: Re: mly problem (AR 170) In-Reply-To: <20010517114314.A1714@ramses.local> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 17 May 2001, Clemens Hermann wrote: I've copied Mike Smith on this, the author of the driver, since he will hopefully know more information about the error messages you're getting. > Am 16.05.2001 um 15:46:50 schrieb Chris Dillon: > > Hi Chris, > > > > There does no such disk exist, according to the controller-setup > > > this is the processor. Are these messages a problem? > > > > Shouldn't be. > > could you give me a hint what this messages mean? I can't even remember what you said they were, now. Would have been good to keep them in the reply. :-) > > No userland tools exist yet to manage the controller and its devices, > > that I know of. With a managed hot-plug enclosure, I'm not sure that > > you would even need any. I do know that the driver (via the kernel) > > will emit a warning when a RAID array goes critical. You can test it > > yourself by simply removing a drive from your redundant array, > > yes it works but I get the following lies in syslog: > > mly0: physical device 0:0 selection timeout > mly0: logical device 0(da0) critical > mly0: unknown event code-61 > mly0: unknown event code-162 > > any ideas what the last two lines mean? No idea. If you re-insert the drive, does it begin a rebuild? If it doesn't, make sure you actually have automatic rebuild enabled in the controller config, and that it is set up properly for your managed enclosure. Mike will hopefully know wether those "unknown events" are potentially serious or just informational flak. > Furthermore: Will I get the messages only in syslog or will they > appear in the FreeBSD daily report mails? If not, is there a way > to get them there? Anything printed by the kernel to the console will also show up in /var/log/messages and possibly even /var/log/console.log, depending on how you have syslogd set up. They will be sent to you in the daily security output showing the daily dmesg difference, assuming that the dmesg buffer isn't so overrun with other messages that they get lost. The best way to get that information in the mail is to write your own script that runs along with the daily periodic stuff and searches for output from the mly driver. Better yet, have it check the logs every hour or so and mail you or page you if it finds something. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 17 10: 5:31 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id B2CC037B422 for ; Thu, 17 May 2001 10:05:28 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id MAA18948; Thu, 17 May 2001 12:05:25 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 17 May 2001 12:05:25 -0500 (CDT) From: Chris Dillon To: Clemens Hermann Cc: Subject: Re: mly problem (AR 170) In-Reply-To: <20010517120326.A1925@ramses.local> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 17 May 2001, Clemens Hermann wrote: > one thing else: > Is it normal that my mly0 controller is not listed in /dev? Yes. mly uses the CAM subsystem, so devices attached to it appear as if under any regular SCSI controller, such as da* or cd* or whatever. There might be a device node for the controller itself at some time if future management utilities need one, but they probably won't. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 17 11:26:47 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by hub.freebsd.org (Postfix) with ESMTP id B9A9F37B424 for ; Thu, 17 May 2001 11:26:44 -0700 (PDT) (envelope-from haribeau@gmx.de) Received: from fwd03.sul.t-online.de by mailout02.sul.t-online.com with smtp id 150STw-00080U-00; Thu, 17 May 2001 20:26:40 +0200 Received: from ramses.local (320080844193-0001@[62.225.210.188]) by fmrl03.sul.t-online.com with esmtp id 150SUH-0JXZU8C; Thu, 17 May 2001 20:27:01 +0200 Received: from haribeau by ramses.local with local (Exim 3.12 #1 (Debian)) id 150UJd-0001nJ-00; Thu, 17 May 2001 22:24:09 +0200 Date: Thu, 17 May 2001 22:24:09 +0200 From: Clemens Hermann To: Chris Dillon Cc: freebsd-scsi@FreeBSD.ORG, msmith@wolves.k12.mo.us Subject: Re: mly problem (AR 170) Message-ID: <20010517222409.B6772@ramses.local> References: <20010517114314.A1714@ramses.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: von Chris Dillon am 17.May.2001 um 12:02:21 (-0500) X-Mailer: Mutt 1.2.5i (Linux 2.2.17 i586) X-Sender: 320080844193-0001@t-dialin.net Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Chris, > I've copied Mike Smith on this, the author of the driver, since he > will hopefully know more information about the error messages you're > getting. maybe, yes :) > I can't even remember what you said they were, now. Would have been > good to keep them in the reply. :-) sorry, I'll make it better next time. > No idea. If you re-insert the drive, does it begin a rebuild? yes thanks for your help /ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 19 5:27:42 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 53F0337B43C for ; Sat, 19 May 2001 05:27:40 -0700 (PDT) (envelope-from haribeau@gmx.de) Received: (qmail 5928 invoked by uid 0); 19 May 2001 12:27:38 -0000 Received: from p3ee1d2b7.dip.t-dialin.net (HELO pcch) (62.225.210.183) by mail.gmx.net (mp004-rz3) with SMTP; 19 May 2001 12:27:38 -0000 Message-ID: <000901c0e05e$dd9aa0e0$3301a8c0@pcch> From: "Clemens Hermann" To: Subject: mly rebuild problem Date: Sat, 19 May 2001 14:26:00 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 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 Hi, I use the mylex Acceleraid 170 on FreeBSD 4.3. When I use a mirror and one spare drive everything works fine if I remove one drive from the array. The spare is syncronized with the remainig drive of the array and after this there are two drives back online (spare and the remainig mirror-disk). If I re-insert the second disk from the mirror it is not synchronized. Same thing happens if I only have a two-drive mirror (without spare). If I remove one I get the kernel-message. If I re-insert is it is /not/ integrated into the array, just nothing happens. If I reboot the machine the drive is marked as critical in the controller-setup. I have acitvated automatic-rebuild in the controllers-setup. any hints? tia /ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message