From owner-freebsd-geom@FreeBSD.ORG Mon Mar 14 18:47:16 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 79FF216A4CE for ; Mon, 14 Mar 2005 18:47:16 +0000 (GMT) Received: from jupiter.datacompusa.com (host-64-179-57-99.gra.choiceone.net [64.179.57.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3176243D3F for ; Mon, 14 Mar 2005 18:47:11 +0000 (GMT) (envelope-from msb@datacompusa.com) Received: from [192.168.1.100] (msb.datacomp-intranet.com [192.168.1.100]) j2EIlAgQ049728 for ; Mon, 14 Mar 2005 13:47:10 -0500 (EST) (envelope-from msb@datacompusa.com) Mime-Version: 1.0 (Apple Message framework v619.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-geom@freebsd.org From: Michael Boers Date: Mon, 14 Mar 2005 13:46:15 -0500 X-Mailer: Apple Mail (2.619.2) Subject: gmirrored boot drives locks up during buildworld X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2005 18:47:16 -0000 I recently installed FreeBSD 5.3 on a machine to be my primary mysql server. The machine failed after about 3 weeks of heavy use. The machine did not panic, it just froze and some random characters appeared on the console. A reboot restored the system for another few weeks. On the third failure I took it out of production. The machine consists of a Intel Pentium 4 EE HT with a pair of 80 gigabyte IDE gmirrored boot drives and a pair of 250 gigabyte IDE gmirror data drives. With the machine out of production, I used while (true) do make clean; make buildworld; done to exercise the machine until it failed. Usually within three days. I swapped video cards, memory, hard drives, and played with bios settings to no avail. Finally I determined that when I ran without using gmirror, the machine would build indefinitely. Finally, I tried the buildworld test on a completely different (amd vs intel, scsi vs ide disks) machine and it failed in less than 3 hours. Because the system freezes rather than panics, I have no diagnostic information to provide. If this is a possible gmirror bug, please let me know if there is any other information I can provide. I am very interested in using gmirror but I want to make sure it is safe. Please feel free to call me at the below number if necessary. -- Michael Boers Datacomp 877-406-0231 Details on First Machine uname output: FreeBSD saturn.datacomp-intranet.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Mar 11 13:37:46 EST 2005 msb@saturn.datacomp-intranet.com:/usr/src/sys/i386/compile/SATURN i386 dmesg boot info: Copyright (c) 1992-2004 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 5.3-RELEASE #0: Fri Mar 11 13:37:46 EST 2005 msb@saturn.datacomp-intranet.com:/usr/src/sys/i386/compile/SATURN ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.40GHz (3400.13-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf25 Stepping = 5 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 1073676288 (1023 MB) avail memory = 1045311488 (996 MB) ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf8000000-0xfbffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) uhci0: port 0xcc00-0xcc1f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel 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 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xd400-0xd41f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xd800-0xd81f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib2: at device 30.0 on pci0 pci2: on pcib2 em0: port 0xbc00-0xbc3f mem 0xfeaa0000-0xfeabffff,0xfeac0000-0xfeadffff irq 19 at device 3.0 on pci2 em0: Ethernet address: 00:0e:0c:33:2c:96 em0: Speed:N/A Duplex:N/A re0: port 0xb800-0xb8ff mem 0xfeafff00-0xfeafffff irq 20 at device 6.0 on pci2 miibus0: on re0 rgephy0: on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto re0: Ethernet address: 00:11:09:81:40:a9 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 atapci1: port 0xdc00-0xdc0f,0xe000-0xe003,0xe400-0xe407,0xe800-0xe803,0xec00-0xec07 irq 18 at device 31.2 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 pci0: at device 31.3 (no driver attached) pci0: at device 31.5 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port pmtimer0 on isa0 orm0: at iomem 0xe0000-0xe0fff,0xcf800-0xd07ff,0xc0000-0xcf7ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 3400132108 Hz quality 800 Timecounters tick every 10.000 msec ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to deny, logging limited to 1 packets/entry by default acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ad0: 76319MB [155061/16/63] at ata0-master UDMA100 ad1: 76319MB [155061/16/63] at ata0-slave UDMA100 acd0: CDROM at ata1-master PIO4 ad4: 238475MB [484521/16/63] at ata2-master SATA150 GEOM_MIRROR: Device boot created (id=1429322453). GEOM_MIRROR: Device boot: provider ad0 detected. ad6: 238475MB [484521/16/63] at ata3-master SATA150 GEOM_MIRROR: Device boot: provider ad1 detected. GEOM_MIRROR: Device boot: provider ad1 activated. GEOM_MIRROR: Device boot: provider mirror/boot launched. GEOM_MIRROR: Device boot: rebuilding provider ad0. GEOM_MIRROR: Device databases created (id=59908152). GEOM_MIRROR: Device databases: provider ad4 detected. GEOM_MIRROR: Device databases: provider ad6 detected. GEOM_MIRROR: Device databases: provider ad6 activated. GEOM_MIRROR: Device databases: provider mirror/databases launched. GEOM_MIRROR: Device databases: rebuilding provider ad4. Mounting root from ufs:/dev/mirror/boota em0: Link is up 100 Mbps Full Duplex From owner-freebsd-geom@FreeBSD.ORG Mon Mar 14 19:06:54 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C07C816A4CE for ; Mon, 14 Mar 2005 19:06:54 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1750243D53 for ; Mon, 14 Mar 2005 19:06:54 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id 59CD5ACAE0; Mon, 14 Mar 2005 20:06:50 +0100 (CET) Date: Mon, 14 Mar 2005 20:06:50 +0100 From: Pawel Jakub Dawidek To: Michael Boers Message-ID: <20050314190650.GX9291@darkness.comp.waw.pl> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Etoca9nXhLMPgAOd" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 cc: freebsd-geom@freebsd.org Subject: Re: gmirrored boot drives locks up during buildworld X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2005 19:06:54 -0000 --Etoca9nXhLMPgAOd Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 14, 2005 at 01:46:15PM -0500, Michael Boers wrote: +> I recently installed FreeBSD 5.3 on a machine to be my primary mysql =20 +> server. The machine failed after about 3 weeks of heavy use. The =20 +> machine did not panic, it just froze and some random characters =20 +> appeared on the console. A reboot restored the system for another few = =20 +> weeks. On the third failure I took it out of production. +>=20 +> The machine consists of a Intel Pentium 4 EE HT with a pair of 80 =20 +> gigabyte IDE gmirrored boot drives and a pair of 250 gigabyte IDE =20 +> gmirror data drives. +>=20 +> With the machine out of production, I used +>=20 +> while (true) do make clean; make buildworld; done +>=20 +> to exercise the machine until it failed. Usually within three days. I = =20 +> swapped video cards, memory, hard drives, and played with bios settings = =20 +> to no avail. Finally I determined that when I ran without using =20 +> gmirror, the machine would build indefinitely. +>=20 +> Finally, I tried the buildworld test on a completely different (amd vs = =20 +> intel, scsi vs ide disks) machine and it failed in less than 3 hours. +>=20 +> Because the system freezes rather than panics, I have no diagnostic =20 +> information to provide. +>=20 +> If this is a possible gmirror bug, please let me know if there is any = =20 +> other information I can provide. I am very interested in using gmirror = =20 +> but I want to make sure it is safe. Please feel free to call me at the = =20 +> below number if necessary. Could increase kern.geom.mirror.debug to 1? Could you turn on HTT and compile your kernel with MP_WATCHDOG (you should also set debug.watchdog to 1)? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --Etoca9nXhLMPgAOd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFCNeDKForvXbEpPzQRAhDGAJ9Mg2g32OXT6LKbuSqSGIGNX6ok4gCgh+vk WQe+W2g/6aZIOmnBYDXboKg= =WoJO -----END PGP SIGNATURE----- --Etoca9nXhLMPgAOd-- From owner-freebsd-geom@FreeBSD.ORG Tue Mar 15 08:10:42 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C26CF16A4CE for ; Tue, 15 Mar 2005 08:10:42 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5944F43D39 for ; Tue, 15 Mar 2005 08:10:42 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id DADAAACBF9; Tue, 15 Mar 2005 09:10:38 +0100 (CET) Date: Tue, 15 Mar 2005 09:10:38 +0100 From: Pawel Jakub Dawidek To: freebsd-geom@freebsd.org Message-ID: <20050315081038.GD9291@darkness.comp.waw.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WIarmzxAAJZoYT0o" Content-Disposition: inline User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 Subject: GBDE and write_sector-shutdown-write_keys race. X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2005 08:10:42 -0000 --WIarmzxAAJZoYT0o Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi. If you, guys, remember this issue, I think I found a way to fix it. Now, there can be a race like this: write sector data <- power failure here write new sector keys My idea is to not use entire sector for 128bit AES keys, instead, we can save keys and sector mapping there (I'll explain it later). For every zone we need to leave one spare sector. If we have a write request algorithm is as follows: 1. Generate new key for this sector. 2. Write sector data into spare sector in a zone. 3. Write sector key and update mapping. Point number three is operates on the same sector, so we can assume its atomic. The sectors mapping looks like this (let's assume we have 4 sectors in zone and 1 spare sector): Real In-zone sector sector number number 1 -> 1 2 -> 2 3 -> 3 4 -> 4 (sector 5 is the spare sector) After writting to sector 3 we have: 1 -> 1 2 -> 2 3 -> 5 4 -> 4 (sector 3 is now the spare sector) After writing to sector 1 we have: 1 -> 3 2 -> 2 3 -> 5 4 -> 4 (sector 1 is now the spare sector) This thing will decrease number of sectors in zone, because we need to put mappings there, so we are losing some space. We also need a per-zone spare sector, so it reduces space again, but it gives as reliability. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --WIarmzxAAJZoYT0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFCNph+ForvXbEpPzQRAvKBAJ43poAUMDd1pCC2RHZmTcSvYyszMACdFx2/ J+JaEkQlAayHFx7ovCq/uz8= =pecs -----END PGP SIGNATURE----- --WIarmzxAAJZoYT0o-- From owner-freebsd-geom@FreeBSD.ORG Tue Mar 15 08:14:53 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 085F016A4CE; Tue, 15 Mar 2005 08:14:53 +0000 (GMT) Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2580643D1D; Tue, 15 Mar 2005 08:14:52 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id j2F8EohX008782; Tue, 15 Mar 2005 09:14:50 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Pawel Jakub Dawidek From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 15 Mar 2005 09:10:38 +0100." <20050315081038.GD9291@darkness.comp.waw.pl> Date: Tue, 15 Mar 2005 09:14:50 +0100 Message-ID: <8781.1110874490@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-geom@freebsd.org Subject: Re: GBDE and write_sector-shutdown-write_keys race. X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2005 08:14:53 -0000 In message <20050315081038.GD9291@darkness.comp.waw.pl>, Pawel Jakub Dawidek wr ites: >Now, there can be a race like this: > > write sector data > <- power failure here > write new sector keys Guys, I've said it before and I'll say it again: My hardware, even the cheapest of it, is far more reliable than OpenOffice. I am not going to do anything of the sort which Pawel proposes because _if_ I wanted to handle this issue, I would do it with journaling which would also bring a lot of cryptographic benefit. But again, I'm not even planing on touching this one in the first place. If you want to write your own disk encryption, by all means go for it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-geom@FreeBSD.ORG Tue Mar 15 09:21:00 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E0E616A4CE for ; Tue, 15 Mar 2005 09:21:00 +0000 (GMT) Received: from mail.hacknslash.org (bdsl.66.14.131.218.gte.net [66.14.131.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3A6943D2F for ; Tue, 15 Mar 2005 09:20:56 +0000 (GMT) (envelope-from octavian@hacknslash.org) Received: (qmail 31186 invoked from network); 15 Mar 2005 09:21:06 -0000 Received: from phobos.lexis.int (HELO ?10.0.0.15?) (10.0.0.15) by mail.hacknslash.org with AES256-SHA encrypted SMTP; 15 Mar 2005 09:21:06 -0000 Message-ID: <4236A8F3.8090105@hacknslash.org> Date: Tue, 15 Mar 2005 01:20:51 -0800 From: Octavian Hornoiu User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-geom@freebsd.org X-Enigmail-Version: 0.90.1.1 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/mixed; boundary="------------040408070302030509030706" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: gmirror cannot update metadata on disk da0s1 X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: octavian@hacknslash.org List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2005 09:21:00 -0000 This is a multi-part message in MIME format. --------------040408070302030509030706 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I have followed the instructions as per the document at http://people.freebsd.org/~rse/mirror/ to setup my geom mirror using FreeBSD 5.3-p5 and two 70 gig SCSI maxtor drives of identical size. I have tried both the whole partition gm0 and single slice gm0s1 alternatives to mirroring the drives and I have tried both hardcoding and without hardcoding and I still get cannot update metadata or cannot read metadata or cannot write metadata. The drive with metadata problems will change depending with the setup so sometimes da0 works fine and da1 is broken or vice versa. There does not seem to be a pattern to this. I have worked with vinum many times before and I'm not inexperience but I have reached the end of the road with gmirror. I've tried 8 times to mirror these disks now with different configurations and I've failed every time. I have even alternated the sizes of the slices and left room at the end of the drive, at the beginning of the drive, etc. Here are the appropriate informational dumps: Copyright (c) 1992-2004 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 5.3-RELEASE-p5 #0: Wed Feb 23 16:19:57 PST 2005 root@capone.bellevuechristian.org:/usr/obj/usr/src/sys/CAPONE Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.19-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 2147221504 (2047 MB) avail memory = 2095755264 (1998 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic1: WARNING: intbase 32 != expected base 24 ioapic2: Changing APIC ID to 10 ioapic2: WARNING: intbase 64 != expected base 56 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 32-55 on motherboard ioapic2 irqs 64-87 on motherboard netsmb_dev: loaded npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 pcib3: at device 0.2 on pci1 pci3: on pcib3 mpt0: port 0xec00-0xecff mem 0xdfde0000-0xdfdeffff,0xdfdf0000-0xdfdfffff irq 34 at device 5.0 on pci3 mpt0: [GIANT-LOCKED] em0: port 0xe8c0-0xe8ff mem 0xdfdc0000-0xdfddffff irq 39 at device 12.0 on pci3 em0: Ethernet address: 00:0e:0c:69:3a:44 em0: Speed:N/A Duplex:N/A pcib4: at device 4.0 on pci0 pci4: on pcib4 pcib5: at device 5.0 on pci0 pci5: on pcib5 pcib6: at device 0.0 on pci5 pci6: on pcib6 em1: port 0xdcc0-0xdcff mem 0xdfae0000-0xdfafffff irq 64 at device 7.0 on pci6 em1: Ethernet address: 00:11:43:d7:64:2e em1: Speed:N/A Duplex:N/A pcib7: at device 0.2 on pci5 pci7: on pcib7 em2: port 0xccc0-0xccff mem 0xdf8e0000-0xdf8fffff irq 65 at device 8.0 on pci7 em2: Ethernet address: 00:11:43:d7:64:2f em2: Speed:N/A Duplex:N/A pcib8: at device 6.0 on pci0 pci8: on pcib8 uhci0: port 0xace0-0xacff irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xacc0-0xacdf irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub2: Dell product 0xa001, class 9/0, rev 2.00/0.00, addr 2 uhub2: 2 ports with 2 removable, self powered uhci2: port 0xaca0-0xacbf irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ums0: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), rev 1.10/3.00, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. pci0: at device 29.7 (no driver attached) pcib9: at device 30.0 on pci0 pci9: on pcib9 pci9: at device 13.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A orm0: at iomem 0xec000-0xeffff,0xcb000-0xcefff,0xc0000-0xcafff on isa0 pmtimer0 on isa0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 10.000 msec acd0: CDROM at ata0-master UDMA33 Waiting 15 seconds for SCSI devices to settle ses0 at mpt0 bus 0 target 6 lun 0 ses0: Fixed Processor SCSI-2 device ses0: 3.300MB/s transfers ses0: SAF-TE Compliant Device da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing Enabled da0: 70007MB (143374650 512 byte sectors: 255H 63S/T 8924C) da1 at mpt0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing Enabled da1: 70007MB (143374650 512 byte sectors: 255H 63S/T 8924C) GEOM_MIRROR: Device gm0s1 created (id=1445021139). GEOM_MIRROR: Device gm0s1: provider da0s1 detected. GEOM_MIRROR: Device gm0s1: provider da1s1 detected. GEOM_MIRROR: Device gm0s1: provider da1s1 activated. GEOM_MIRROR: Cannot update metadata on disk da0s1 (error=1). GEOM_MIRROR: Device gm0s1: provider da0s1 activated. GEOM_MIRROR: Device gm0s1: provider mirror/gm0s1 launched. GEOM_MIRROR: Cannot update metadata on disk da0s1 (error=1). GEOM_MIRROR: Device gm0s1: provider da0s1 disconnected. SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! Mounting root from ufs:/dev/mirror/gm0s1a em0: Link is up 100 Mbps Full Duplex Metadata on /dev/da1s1: magic: GEOM::MIRROR version: 1 name: gm0s1 mid: 1445021139 did: 4266048836 all: 2 syncid: 3 priority: 0 slice: 4096 balance: round-robin mediasize: 73402365952 sectorsize: 512 syncoffset: 0 mflags: NONE dflags: DIRTY hcprovider: da1s1 MD5 hash: c082817f594eb795a95ebb547bb20f71 Metadata on /dev/da0s1: magic: GEOM::MIRROR version: 1 name: gm0s1 mid: 1445021139 did: 1764218562 all: 2 syncid: 3 priority: 0 slice: 4096 balance: round-robin mediasize: 73402365952 sectorsize: 512 syncoffset: 22164275200 mflags: NONE dflags: DIRTY SYNCHRONIZING hcprovider: da0s1 MD5 hash: 74f4f6b2cc14a5624539431c455cab81 Geom name: gm0s1 State: DEGRADED Components: 2 Balance: round-robin Slice: 4096 Flags: NONE SyncID: 5 ID: 1445021139 Providers: 1. Name: mirror/gm0s1 Mediasize: 73402365952 (68G) Sectorsize: 512 Mode: r6w6e1 Consumers: 1. Name: da1s1 Mediasize: 73402366464 (68G) Sectorsize: 512 Mode: r6w6e2 State: ACTIVE Priority: 0 Flags: DIRTY, HARDCODED SyncID: 5 ID: 4266048836 Geom name: gm0s1.sync ******* Working on device /dev/da1 ******* parameters extracted from in-core disklabel are: cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 143363997 (70001 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: # /dev/mirror/gm0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 1024000 0 4.2BSD 2048 16384 64008 b: 8388608 1024000 swap c: 143363996 0 unused 0 0 # "raw" part, don't ed$ d: 8388608 9412608 4.2BSD 2048 16384 28552 e: 4194304 17801216 4.2BSD 2048 16384 28552 f: 10240000 21995520 4.2BSD 2048 16384 28552 g: 110182400 32235520 4.2BSD 2048 16384 28552 Any help would be greatly appreciated! I am ready to pull my hair out and I'm already going bald so that would be bad! Octavian Hornoiu --------------040408070302030509030706-- From owner-freebsd-geom@FreeBSD.ORG Tue Mar 15 11:22:12 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59EF316A4CE for ; Tue, 15 Mar 2005 11:22:12 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC35743D1D for ; Tue, 15 Mar 2005 11:22:11 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id D7F5AACBF9; Tue, 15 Mar 2005 12:22:09 +0100 (CET) Date: Tue, 15 Mar 2005 12:22:09 +0100 From: Pawel Jakub Dawidek To: Octavian Hornoiu Message-ID: <20050315112209.GF9291@darkness.comp.waw.pl> References: <4236A8F3.8090105@hacknslash.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IZVch7VEbLLUX8Ok" Content-Disposition: inline In-Reply-To: <4236A8F3.8090105@hacknslash.org> User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 cc: freebsd-geom@freebsd.org Subject: Re: gmirror cannot update metadata on disk da0s1 X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2005 11:22:12 -0000 --IZVch7VEbLLUX8Ok Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 15, 2005 at 01:20:51AM -0800, Octavian Hornoiu wrote: +> I have followed the instructions as per the document at +> http://people.freebsd.org/~rse/mirror/ to setup my geom mirror using +> FreeBSD 5.3-p5 and two 70 gig SCSI maxtor drives of identical size. I +> have tried both the whole partition gm0 and single slice gm0s1 +> alternatives to mirroring the drives and I have tried both hardcoding +> and without hardcoding and I still get cannot update metadata or cannot +> read metadata or cannot write metadata. The drive with metadata +> problems will change depending with the setup so sometimes da0 works +> fine and da1 is broken or vice versa. There does not seem to be a +> pattern to this. I have worked with vinum many times before and I'm not +> inexperience but I have reached the end of the road with gmirror. I've +> tried 8 times to mirror these disks now with different configurations +> and I've failed every time. I have even alternated the sizes of the +> slices and left room at the end of the drive, at the beginning of the +> drive, etc. Here are the appropriate informational dumps: [...] +> FreeBSD 5.3-RELEASE-p5 #0: Wed Feb 23 16:19:57 PST 2005 [...] Could you try with 5-STABLE? +> GEOM_MIRROR: Device gm0s1 created (id=3D1445021139). +> GEOM_MIRROR: Device gm0s1: provider da0s1 detected. +> GEOM_MIRROR: Device gm0s1: provider da1s1 detected. +> GEOM_MIRROR: Device gm0s1: provider da1s1 activated. +> GEOM_MIRROR: Cannot update metadata on disk da0s1 (error=3D1). +> GEOM_MIRROR: Device gm0s1: provider da0s1 activated. +> GEOM_MIRROR: Device gm0s1: provider mirror/gm0s1 launched. +> GEOM_MIRROR: Cannot update metadata on disk da0s1 (error=3D1). +> GEOM_MIRROR: Device gm0s1: provider da0s1 disconnected. I remember this problem, but not sure when exaclty it was fixed. The best I can offer is to try 5-STABLE. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --IZVch7VEbLLUX8Ok Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFCNsVhForvXbEpPzQRAoBHAKDYa9AbGcMpkIVBEYex9JW+LNxeMgCgiX2a 3RgKhzCpqTYVW3bG6+KeGpc= =sOSv -----END PGP SIGNATURE----- --IZVch7VEbLLUX8Ok-- From owner-freebsd-geom@FreeBSD.ORG Tue Mar 15 13:23:44 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FA6316A4CE; Tue, 15 Mar 2005 13:23:44 +0000 (GMT) Received: from jupiter.datacompusa.com (host-64-179-57-99.gra.choiceone.net [64.179.57.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4B0243D54; Tue, 15 Mar 2005 13:23:42 +0000 (GMT) (envelope-from msb@datacompusa.com) Received: from [192.168.1.100] (msb.datacomp-intranet.com [192.168.1.100]) j2FDNggQ076594; Tue, 15 Mar 2005 08:23:42 -0500 (EST) (envelope-from msb@datacompusa.com) In-Reply-To: <20050314190650.GX9291@darkness.comp.waw.pl> References: <20050314190650.GX9291@darkness.comp.waw.pl> Mime-Version: 1.0 (Apple Message framework v619.2) Message-Id: <42cc591ca3faf6a5ab49fa7101e5945c@datacompusa.com> From: Michael Boers Date: Tue, 15 Mar 2005 08:22:51 -0500 To: Pawel Jakub Dawidek X-Mailer: Apple Mail (2.619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-geom@FreeBSD.org Subject: Re: gmirrored boot drives locks up during buildworld X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2005 13:23:44 -0000 Pawel, Thank-you for your quick response. In addition to enabling HTT in the bios, I have made the following changes to the kernel, options SMP options MPTABLE_FORCE_HTT options MP_WATCHDOG and set the following flags kern.geom.mirror.debug=1 debug.watchdog=1 I reran the "while (true) do make clean; make buildworld; done" test and the machine has locked up as before. I was monitoring the test with a terminal running top last pid: 57530; load averages: 3.79, 3.24, 2.93 up 0+07:18:14 23:31:10 148 processes: 6 running, 111 sleeping, 31 waiting CPU states: 31.3% user, 0.0% nice, 18.5% system, 0.2% interrupt, 50.0% idle Mem: 110M Active, 385M Inact, 89M Wired, 672K Cache, 112M Buf, 416M Free Swap: 512M Total, 512M Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 11 root 130 0 0K 12K CPU1 1 383:33 100.54% 100.54% mp_watchdog cpu 1 3 root -8 0 0K 12K - 0 21:40 29.74% 29.74% g_up 29 root -64 -183 0K 12K WAIT 0 2:42 5.22% 5.22% irq18: uhci2+ 4 root -8 0 0K 12K - 0 3:27 2.05% 2.05% g_down 12 root 96 0 0K 12K RUN 0 383:56 0.00% 0.00% idle: cpu0 576 mysql 20 0 56896K 34584K kserel 0 1:17 0.00% 0.00% mysqld 713 root 8 0 2000K 1456K nanslp 0 0:19 0.00% 0.00% gstat 25 root -64 -183 0K 12K WAIT 0 0:19 0.00% 0.00% irq14: ata0 50 root -8 0 0K 12K m:w1 0 0:18 0.00% 0.00% g_mirror boot 37 root -28 -147 0K 12K WAIT 0 0:15 0.00% 0.00% swi5: clock sio 53 root 171 52 0K 12K RUN 0 0:14 0.00% 0.00% pagezero 680 root 96 0 2440K 1728K CPU0 0 0:13 0.00% 0.00% top 579 mysql 20 0 132M 43196K kserel 0 0:09 0.00% 0.00% mysqld 577 mysql 20 0 56576K 24688K kserel 0 0:08 0.00% 0.00% mysqld 39 root 76 0 0K 12K - 0 0:06 0.00% 0.00% yarrow 594 msb 96 0 6216K 3020K select 0 0:05 0.00% 0.00% sshd 56 root 20 0 0K 12K syncer 0 0:03 0.00% 0.00% syncer and a terminal running gstat dT: 0.510 flag_I 500000us sizeof 240 i -1 L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name 0 0 0 0 0.0 0 0 0.0 0.0| ad0 0 0 0 0 0.0 0 0 0.0 0.0| mirror/boot 0 0 0 0 0.0 0 0 0.0 0.0| ad0a 0 0 0 0 0.0 0 0 0.0 0.0| ad0b 0 0 0 0 0.0 0 0 0.0 0.0| ad0c 0 0 0 0 0.0 0 0 0.0 0.0| ad0d 0 0 0 0 0.0 0 0 0.0 0.0| ad0e 0 0 0 0 0.0 0 0 0.0 0.0| ad0f 0 0 0 0 0.0 0 0 0.0 0.0| mirror/boota 0 0 0 0 0.0 0 0 0.0 0.0| mirror/bootb 0 0 0 0 0.0 0 0 0.0 0.0| mirror/bootc 0 0 0 0 0.0 0 0 0.0 0.0| mirror/bootd 0 0 0 0 0.0 0 0 0.0 0.0| mirror/boote 0 0 0 0 0.0 0 0 0.0 0.0| mirror/bootf 0 0 0 0 0.0 0 0 0.0 0.0| ad1 0 0 0 0 0.0 0 0 0.0 0.0| acd0 0 0 0 0 0.0 0 0 0.0 0.0| ad4 0 0 0 0 0.0 0 0 0.0 0.0| ad6 0 0 0 0 0.0 0 0 0.0 0.0| ad4c 0 0 0 0 0.0 0 0 0.0 0.0| ad4d 0 0 0 0 0.0 0 0 0.0 0.0| ad6c 0 0 0 0 0.0 0 0 0.0 0.0| ad6d I have not touched the machine yet. Is there any other info I can provide? -- Michael Boers Datacomp On Mar 14, 2005, at 2:06 PM, Pawel Jakub Dawidek wrote: > On Mon, Mar 14, 2005 at 01:46:15PM -0500, Michael Boers wrote: > +> I recently installed FreeBSD 5.3 on a machine to be my primary mysql > +> server. The machine failed after about 3 weeks of heavy use. The > +> machine did not panic, it just froze and some random characters > +> appeared on the console. A reboot restored the system for another > few > +> weeks. On the third failure I took it out of production. > +> > +> The machine consists of a Intel Pentium 4 EE HT with a pair of 80 > +> gigabyte IDE gmirrored boot drives and a pair of 250 gigabyte IDE > +> gmirror data drives. > +> > +> With the machine out of production, I used > +> > +> while (true) do make clean; make buildworld; done > +> > +> to exercise the machine until it failed. Usually within three > days. I > +> swapped video cards, memory, hard drives, and played with bios > settings > +> to no avail. Finally I determined that when I ran without using > +> gmirror, the machine would build indefinitely. > +> > +> Finally, I tried the buildworld test on a completely different (amd > vs > +> intel, scsi vs ide disks) machine and it failed in less than 3 > hours. > +> > +> Because the system freezes rather than panics, I have no diagnostic > +> information to provide. > +> > +> If this is a possible gmirror bug, please let me know if there is > any > +> other information I can provide. I am very interested in using > gmirror > +> but I want to make sure it is safe. Please feel free to call me at > the > +> below number if necessary. > > Could increase kern.geom.mirror.debug to 1? > Could you turn on HTT and compile your kernel with MP_WATCHDOG (you > should > also set debug.watchdog to 1)? > > -- > Pawel Jakub Dawidek http://www.wheel.pl > pjd@FreeBSD.org http://www.FreeBSD.org > FreeBSD committer Am I Evil? Yes, I Am! From owner-freebsd-geom@FreeBSD.ORG Tue Mar 15 13:30:56 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B61CE16A4CE for ; Tue, 15 Mar 2005 13:30:56 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B26943D39 for ; Tue, 15 Mar 2005 13:30:55 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id 6BAE5ACBCB; Tue, 15 Mar 2005 14:30:49 +0100 (CET) Date: Tue, 15 Mar 2005 14:30:49 +0100 From: Pawel Jakub Dawidek To: Michael Boers Message-ID: <20050315133049.GI9291@darkness.comp.waw.pl> References: <20050314190650.GX9291@darkness.comp.waw.pl> <42cc591ca3faf6a5ab49fa7101e5945c@datacompusa.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PWOvHMg+QlBd+AoO" Content-Disposition: inline In-Reply-To: <42cc591ca3faf6a5ab49fa7101e5945c@datacompusa.com> User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 cc: freebsd-geom@FreeBSD.org Subject: Re: gmirrored boot drives locks up during buildworld X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2005 13:30:56 -0000 --PWOvHMg+QlBd+AoO Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 15, 2005 at 08:22:51AM -0500, Michael Boers wrote: +> In addition to enabling HTT in the bios, I have made the following=20 +> changes to the kernel,=20 +>=20 +> options SMP=20 +> options MPTABLE_FORCE_HTT =20 +> options MP_WATCHDOG=20 +>=20 +> and set the following flags=20 +>=20 +> kern.geom.mirror.debug=3D1=20 +> debug.watchdog=3D1=20 +>=20 +> I reran the "while (true) do make clean; make buildworld; done" test=20 +> and the machine has locked up as before.=20 If it didn't enter to the debugger, it is not a hard lockup. +> I have not touched the machine yet. Is there any other info I can=20 +> provide?=20 Yes, can you enter to the debugger and: db> ps [find interesting processes like gmirror or processes which are sleeping on for example g_topology_lock] db> tr db> tr and send me the output? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --PWOvHMg+QlBd+AoO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFCNuOJForvXbEpPzQRAjMrAJ4oUwdbfEN9MmnxRORn1UChBCI/OACgvbZ5 Ie+s1wEwBUsPbJM54EA1FHU= =Kc38 -----END PGP SIGNATURE----- --PWOvHMg+QlBd+AoO-- From owner-freebsd-geom@FreeBSD.ORG Tue Mar 15 22:03:37 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4F3716A4CE for ; Tue, 15 Mar 2005 22:03:37 +0000 (GMT) Received: from gondolin.valar.ws (gondolin.valar.ws [66.216.68.225]) by mx1.FreeBSD.org (Postfix) with SMTP id D0F8043D3F for ; Tue, 15 Mar 2005 22:03:36 +0000 (GMT) (envelope-from daniel@zepeda.ws) Received: (qmail 14455 invoked by uid 89); 15 Mar 2005 22:03:40 -0000 Received: from cpe-66-25-73-29.satx.res.rr.com (HELO ?10.255.255.1?) (66.25.73.29) by gondolin.valar.ws with SMTP; 15 Mar 2005 22:03:40 -0000 Message-ID: <42375BB2.2080903@zepeda.ws> Date: Tue, 15 Mar 2005 16:03:30 -0600 From: "Daniel P. Zepeda" User-Agent: Mozilla Thunderbird 0.9 (X11/20041127) X-Accept-Language: en-us, en MIME-Version: 1.0 To: octavian@hacknslash.org References: <4236A8F3.8090105@hacknslash.org> In-Reply-To: <4236A8F3.8090105@hacknslash.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-geom@freebsd.org Subject: Re: gmirror cannot update metadata on disk da0s1 X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2005 22:03:37 -0000 What worked for me was the whole disk approach, not on-a-slice, ensured that 'swapoff="YES" was in /etc/rc.conf, changed the reboot and halt commands to shell scripts to ensure I always use 'shutdown - when rebooting, and the final nugget was to add: kern.geom.mirror.timeout=0 to /boot/loader.conf I think that was all, if I remember anything else, I'll let you know. Hope it helps. DZ Octavian Hornoiu wrote: >I have followed the instructions as per the document at >http://people.freebsd.org/~rse/mirror/ to setup my geom mirror using >FreeBSD 5.3-p5 and two 70 gig SCSI maxtor drives of identical size. I >have tried both the whole partition gm0 and single slice gm0s1 >alternatives to mirroring the drives and I have tried both hardcoding >and without hardcoding and I still get cannot update metadata or cannot >read metadata or cannot write metadata. The drive with metadata >problems will change depending with the setup so sometimes da0 works >fine and da1 is broken or vice versa. There does not seem to be a >pattern to this. I have worked with vinum many times before and I'm not >inexperience but I have reached the end of the road with gmirror. I've >tried 8 times to mirror these disks now with different configurations >and I've failed every time. I have even alternated the sizes of the >slices and left room at the end of the drive, at the beginning of the >drive, etc. Here are the appropriate informational dumps: > >Copyright (c) 1992-2004 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 5.3-RELEASE-p5 #0: Wed Feb 23 16:19:57 PST 2005 > root@capone.bellevuechristian.org:/usr/obj/usr/src/sys/CAPONE >Timecounter "i8254" frequency 1193182 Hz quality 0 >CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.19-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 > >Features=0xbfebfbff > Hyperthreading: 2 logical CPUs >real memory = 2147221504 (2047 MB) >avail memory = 2095755264 (1998 MB) >ACPI APIC Table: >FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 6 > cpu3 (AP): APIC ID: 7 >ioapic0: Changing APIC ID to 8 >ioapic1: Changing APIC ID to 9 >ioapic1: WARNING: intbase 32 != expected base 24 >ioapic2: Changing APIC ID to 10 >ioapic2: WARNING: intbase 64 != expected base 56 >ioapic0 irqs 0-23 on motherboard >ioapic1 irqs 32-55 on motherboard >ioapic2 irqs 64-87 on motherboard >netsmb_dev: loaded >npx0: [FAST] >npx0: on motherboard >npx0: INT 16 interface >acpi0: on motherboard >acpi0: Power Button (fixed) >Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 >acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 >cpu0: on acpi0 >cpu1: on acpi0 >cpu2: on acpi0 >cpu3: on acpi0 >pcib0: port 0xcf8-0xcff on acpi0 >pci0: on pcib0 >pcib1: at device 2.0 on pci0 >pci1: on pcib1 >pcib2: at device 0.0 on pci1 >pci2: on pcib2 >pcib3: at device 0.2 on pci1 >pci3: on pcib3 >mpt0: port 0xec00-0xecff mem >0xdfde0000-0xdfdeffff,0xdfdf0000-0xdfdfffff irq 34 at device 5.0 on pci3 >mpt0: [GIANT-LOCKED] >em0: port >0xe8c0-0xe8ff mem 0xdfdc0000-0xdfddffff irq 39 at device 12.0 on pci3 >em0: Ethernet address: 00:0e:0c:69:3a:44 >em0: Speed:N/A Duplex:N/A >pcib4: at device 4.0 on pci0 >pci4: on pcib4 >pcib5: at device 5.0 on pci0 >pci5: on pcib5 >pcib6: at device 0.0 on pci5 >pci6: on pcib6 >em1: port >0xdcc0-0xdcff mem 0xdfae0000-0xdfafffff irq 64 at device 7.0 on pci6 >em1: Ethernet address: 00:11:43:d7:64:2e >em1: Speed:N/A Duplex:N/A >pcib7: at device 0.2 on pci5 >pci7: on pcib7 >em2: port >0xccc0-0xccff mem 0xdf8e0000-0xdf8fffff irq 65 at device 8.0 on pci7 >em2: Ethernet address: 00:11:43:d7:64:2f >em2: Speed:N/A Duplex:N/A >pcib8: at device 6.0 on pci0 >pci8: on pcib8 >uhci0: port 0xace0-0xacff >irq 16 at device 29.0 on pci0 >uhci0: [GIANT-LOCKED] >usb0: on uhci0 >usb0: USB revision 1.0 >uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >uhub0: 2 ports with 2 removable, self powered >uhci1: port 0xacc0-0xacdf >irq 19 at device 29.1 on pci0 >uhci1: [GIANT-LOCKED] >usb1: on uhci1 >usb1: USB revision 1.0 >uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >uhub1: 2 ports with 2 removable, self powered >uhub2: Dell product 0xa001, class 9/0, rev 2.00/0.00, addr 2 >uhub2: 2 ports with 2 removable, self powered >uhci2: port 0xaca0-0xacbf >irq 18 at device 29.2 on pci0 >uhci2: [GIANT-LOCKED] >usb2: on uhci2 >usb2: USB revision 1.0 >uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >uhub3: 2 ports with 2 removable, self powered >ums0: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), rev >1.10/3.00, addr 2, iclass 3/1 >ums0: 5 buttons and Z dir. >pci0: at device 29.7 (no driver attached) >pcib9: at device 30.0 on pci0 >pci9: on pcib9 >pci9: at device 13.0 (no driver attached) >isab0: at device 31.0 on pci0 >isa0: on isab0 >atapci0: port >0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 >ata0: channel #0 on atapci0 >ata1: channel #1 on atapci0 >fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 >fdc0: [FAST] >fd0: <1440-KB 3.5" drive> on fdc0 drive 0 >atkbdc0: port 0x64,0x60 irq 1 on acpi0 >atkbd0: irq 1 on atkbdc0 >kbd0 at atkbd0 >atkbd0: [GIANT-LOCKED] >sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on >acpi0 >sio0: type 16550A >orm0: at iomem >0xec000-0xeffff,0xcb000-0xcefff,0xc0000-0xcafff on isa0 >pmtimer0 on isa0 >ppc0: parallel port not found. >sc0: at flags 0x100 on isa0 >sc0: VGA <16 virtual consoles, flags=0x300> >sio1: configured irq 3 not in bitmap of probed irqs 0 >sio1: port may not be enabled >vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 >Timecounters tick every 10.000 msec >acd0: CDROM at ata0-master UDMA33 >Waiting 15 seconds for SCSI devices to settle >ses0 at mpt0 bus 0 target 6 lun 0 >ses0: Fixed Processor SCSI-2 device >ses0: 3.300MB/s transfers >ses0: SAF-TE Compliant Device >da0 at mpt0 bus 0 target 0 lun 0 >da0: Fixed Direct Access SCSI-3 device >da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged >Queueing Enabled >da0: 70007MB (143374650 512 byte sectors: 255H 63S/T 8924C) >da1 at mpt0 bus 0 target 1 lun 0 >da1: Fixed Direct Access SCSI-3 device >da1: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged >Queueing Enabled >da1: 70007MB (143374650 512 byte sectors: 255H 63S/T 8924C) >GEOM_MIRROR: Device gm0s1 created (id=1445021139). >GEOM_MIRROR: Device gm0s1: provider da0s1 detected. >GEOM_MIRROR: Device gm0s1: provider da1s1 detected. >GEOM_MIRROR: Device gm0s1: provider da1s1 activated. >GEOM_MIRROR: Cannot update metadata on disk da0s1 (error=1). >GEOM_MIRROR: Device gm0s1: provider da0s1 activated. >GEOM_MIRROR: Device gm0s1: provider mirror/gm0s1 launched. >GEOM_MIRROR: Cannot update metadata on disk da0s1 (error=1). >GEOM_MIRROR: Device gm0s1: provider da0s1 disconnected. >SMP: AP CPU #3 Launched! >SMP: AP CPU #1 Launched! >SMP: AP CPU #2 Launched! >Mounting root from ufs:/dev/mirror/gm0s1a >em0: Link is up 100 Mbps Full Duplex > > >Metadata on /dev/da1s1: > magic: GEOM::MIRROR > version: 1 > name: gm0s1 > mid: 1445021139 > did: 4266048836 > all: 2 > syncid: 3 > priority: 0 > slice: 4096 > balance: round-robin > mediasize: 73402365952 >sectorsize: 512 >syncoffset: 0 > mflags: NONE > dflags: DIRTY >hcprovider: da1s1 > MD5 hash: c082817f594eb795a95ebb547bb20f71 > > >Metadata on /dev/da0s1: > magic: GEOM::MIRROR > version: 1 > name: gm0s1 > mid: 1445021139 > did: 1764218562 > all: 2 > syncid: 3 > priority: 0 > slice: 4096 > balance: round-robin > mediasize: 73402365952 >sectorsize: 512 >syncoffset: 22164275200 > mflags: NONE > dflags: DIRTY SYNCHRONIZING >hcprovider: da0s1 > MD5 hash: 74f4f6b2cc14a5624539431c455cab81 > > >Geom name: gm0s1 >State: DEGRADED >Components: 2 >Balance: round-robin >Slice: 4096 >Flags: NONE >SyncID: 5 >ID: 1445021139 >Providers: >1. Name: mirror/gm0s1 > Mediasize: 73402365952 (68G) > Sectorsize: 512 > Mode: r6w6e1 >Consumers: >1. Name: da1s1 > Mediasize: 73402366464 (68G) > Sectorsize: 512 > Mode: r6w6e2 > State: ACTIVE > Priority: 0 > Flags: DIRTY, HARDCODED > SyncID: 5 > ID: 4266048836 > >Geom name: gm0s1.sync > > > >******* Working on device /dev/da1 ******* >parameters extracted from in-core disklabel are: >cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) > >Figures below won't work with BIOS for partitions not in cyl 1 >parameters to be used for BIOS calculations are: >cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) > >Media sector size is 512 >Warning: BIOS sector numbering starts with sector 1 >Information from DOS bootblock is: >The data for partition 1 is: >sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 63, size 143363997 (70001 Meg), flag 80 (active) > beg: cyl 0/ head 1/ sector 1; > end: cyl 1023/ head 254/ sector 63 >The data for partition 2 is: > >The data for partition 3 is: > >The data for partition 4 is: > > > > > ># /dev/mirror/gm0s1: >8 partitions: ># size offset fstype [fsize bsize bps/cpg] > a: 1024000 0 4.2BSD 2048 16384 64008 > b: 8388608 1024000 swap > c: 143363996 0 unused 0 0 # "raw" part, >don't ed$ > d: 8388608 9412608 4.2BSD 2048 16384 28552 > e: 4194304 17801216 4.2BSD 2048 16384 28552 > f: 10240000 21995520 4.2BSD 2048 16384 28552 > g: 110182400 32235520 4.2BSD 2048 16384 28552 > > >Any help would be greatly appreciated! I am ready to pull my hair out >and I'm already going bald so that would be bad! > >Octavian Hornoiu > > >------------------------------------------------------------------------ > >_______________________________________________ >freebsd-geom@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-geom >To unsubscribe, send any mail to "freebsd-geom-unsubscribe@freebsd.org" > > From owner-freebsd-geom@FreeBSD.ORG Wed Mar 16 01:19:58 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A33AE16A4CE for ; Wed, 16 Mar 2005 01:19:58 +0000 (GMT) Received: from kozoru.com (katana.kozoru.com [207.218.144.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22EF643D41 for ; Wed, 16 Mar 2005 01:19:58 +0000 (GMT) (envelope-from randyb@kozoru.com) Received: from [172.27.60.196] (account randyb [172.27.60.196] verified) by kozoru.com (CommuniGate Pro SMTP 4.2.1) with ESMTP-TLS id 562162 for freebsd-geom@freebsd.org; Tue, 15 Mar 2005 19:19:45 -0600 Mime-Version: 1.0 (Apple Message framework v619.2) In-Reply-To: <20050315120131.6F96B16A4EE@hub.freebsd.org> References: <20050315120131.6F96B16A4EE@hub.freebsd.org> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Randy Bias Date: Tue, 15 Mar 2005 19:19:46 -0600 To: freebsd-geom@freebsd.org X-Mailer: Apple Mail (2.619.2) Subject: GEOM mirror automatic rebuilds X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Mar 2005 01:19:58 -0000 Folks, A, hopefully, quick question. I have GEOM running with a pair of SATA drives on an ICH6R intel controller. If I pull a drive while running and then reinsert it into the bay the GEOM mirror does not automatically rebuild. I have to run 'atacontrol reinit ata3' to reinitialize the drive before GEOM recognizes the provider and begins the rebuild. The drive after being re-inserted does not show up in 'atacontrol list' nor do I see any console messages that it was detected on insert. Is this a general problem? Is 'atacontrol reinit' required? Or is this a failing in the driver for the ICH6 controller? Thanks, --Randy | Randy L Bias www.kozoru.com randyb-at-kozoru-dot-com | Director, Product Management 913.831.2929x26 | Private: randyb-at-randybias.com From owner-freebsd-geom@FreeBSD.ORG Wed Mar 16 08:28:11 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BF9616A4CE; Wed, 16 Mar 2005 08:28:11 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id C706A43D1F; Wed, 16 Mar 2005 08:28:10 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id 5C431ACBCF; Wed, 16 Mar 2005 09:28:07 +0100 (CET) Date: Wed, 16 Mar 2005 09:28:07 +0100 From: Pawel Jakub Dawidek To: Randy Bias Message-ID: <20050316082807.GR9291@darkness.comp.waw.pl> References: <20050315120131.6F96B16A4EE@hub.freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LC6PSvEsRImd411h" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 cc: sos@FreeBSD.org cc: freebsd-geom@freebsd.org Subject: Re: GEOM mirror automatic rebuilds X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Mar 2005 08:28:11 -0000 --LC6PSvEsRImd411h Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 15, 2005 at 07:19:46PM -0600, Randy Bias wrote: +> Folks, +>=20 +> A, hopefully, quick question. I have GEOM running with a pair of=20 +> SATA drives on an ICH6R intel controller. If I pull a drive while runn= ing=20 +> and then reinsert it into the bay the GEOM mirror does not=20 +> automatically rebuild. I have to run 'atacontrol reinit ata3' to=20 +> reinitialize the drive before GEOM recognizes the provider and begins=20 +> the rebuild. The drive after being re-inserted does not show up in=20 +> 'atacontrol list' nor do I see any console messages that it was=20 +> detected on insert. +>=20 +> Is this a general problem? Is 'atacontrol reinit' required? Or is=20 +> this a failing in the driver for the ICH6 controller? I don't know hwere the problem is, but I'm sure it is not gmirror problem:) =46rom gmirror perspective I just need to get provider which I can taste and recognize. I'm CCing sos@, maybe he can tell more about this issue. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --LC6PSvEsRImd411h Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFCN+4XForvXbEpPzQRAjOkAJ0bArumxkvaSDloRJ+yC6UeK01fjgCgslPf YIW0+x5Urz4AkmPDJVR8NWE= =qjqt -----END PGP SIGNATURE----- --LC6PSvEsRImd411h-- From owner-freebsd-geom@FreeBSD.ORG Wed Mar 16 08:48:36 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2213816A4CE; Wed, 16 Mar 2005 08:48:36 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BD7743D2F; Wed, 16 Mar 2005 08:48:35 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id j2G8mVNT000429; Wed, 16 Mar 2005 09:48:33 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <4237F2C3.7080500@DeepCore.dk> Date: Wed, 16 Mar 2005 09:48:03 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 1.0 (X11/20050116) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20050315120131.6F96B16A4EE@hub.freebsd.org> <20050316082807.GR9291@darkness.comp.waw.pl> In-Reply-To: <20050316082807.GR9291@darkness.comp.waw.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.7 cc: Randy Bias cc: sos@FreeBSD.ORG cc: freebsd-geom@FreeBSD.ORG Subject: Re: GEOM mirror automatic rebuilds X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Mar 2005 08:48:36 -0000 Pawel Jakub Dawidek wrote: > On Tue, Mar 15, 2005 at 07:19:46PM -0600, Randy Bias wrote: > +> Folks, > +>=20 > +> A, hopefully, quick question. I have GEOM running with a pair of=20 > +> SATA drives on an ICH6R intel controller. If I pull a drive while = running=20 > +> and then reinsert it into the bay the GEOM mirror does not=20 > +> automatically rebuild. I have to run 'atacontrol reinit ata3' to=20 > +> reinitialize the drive before GEOM recognizes the provider and begin= s=20 > +> the rebuild. The drive after being re-inserted does not show up in = > +> 'atacontrol list' nor do I see any console messages that it was=20 > +> detected on insert. > +>=20 > +> Is this a general problem? Is 'atacontrol reinit' required? Or is= =20 > +> this a failing in the driver for the ICH6 controller? >=20 > I don't know hwere the problem is, but I'm sure it is not gmirror probl= em:) > From gmirror perspective I just need to get provider which I can taste = and > recognize. >=20 > I'm CCing sos@, maybe he can tell more about this issue. You will need the ATA mkIII patches to get hotplug support (ie auto=20 discovery of inserted devices). But beware only a few controllers=20 support that, and the ich6 (in the way we use it anyhow) is not amongst=20 those (currently only SiI and Promise IIRC). --=20 -S=F8ren From owner-freebsd-geom@FreeBSD.ORG Thu Mar 17 08:33:21 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4728316A4CF for ; Thu, 17 Mar 2005 08:33:21 +0000 (GMT) Received: from gondolin.valar.ws (gondolin.valar.ws [66.216.68.225]) by mx1.FreeBSD.org (Postfix) with SMTP id 7C6F643D1D for ; Thu, 17 Mar 2005 08:33:16 +0000 (GMT) (envelope-from daniel@zepeda.ws) Received: (qmail 85249 invoked by uid 89); 17 Mar 2005 08:33:14 -0000 Received: from nat-vlan0200.sat4.rackspace.com (HELO ?10.6.100.229?) (daniel@zepeda.ws@64.39.0.38) by gondolin.valar.ws with SMTP; 17 Mar 2005 08:33:14 -0000 Message-ID: <423940C4.6010807@zepeda.ws> Date: Thu, 17 Mar 2005 02:33:08 -0600 From: "Daniel P. Zepeda" User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Daniel P. Zepeda" References: <4236A8F3.8090105@hacknslash.org> <42375BB2.2080903@zepeda.ws> In-Reply-To: <42375BB2.2080903@zepeda.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: octavian@hacknslash.org cc: freebsd-geom@freebsd.org Subject: Re: gmirror cannot update metadata on disk da0s1 X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Mar 2005 08:33:21 -0000 Here's a link on osnews detailing my experience: http://www.osnews.com/comment.php?news_id=9378 Daniel P. Zepeda wrote: > What worked for me was the whole disk approach, not on-a-slice, > ensured that 'swapoff="YES" was in /etc/rc.conf, changed the reboot > and halt commands to shell scripts to ensure I always use 'shutdown > - when rebooting, and the final nugget was to add: > > kern.geom.mirror.timeout=0 > > to /boot/loader.conf > > I think that was all, if I remember anything else, I'll let you know. > Hope it helps. > > DZ > > Octavian Hornoiu wrote: > >> I have followed the instructions as per the document at >> http://people.freebsd.org/~rse/mirror/ to setup my geom mirror using >> FreeBSD 5.3-p5 and two 70 gig SCSI maxtor drives of identical size. I >> have tried both the whole partition gm0 and single slice gm0s1 >> alternatives to mirroring the drives and I have tried both hardcoding >> and without hardcoding and I still get cannot update metadata or cannot >> read metadata or cannot write metadata. The drive with metadata >> problems will change depending with the setup so sometimes da0 works >> fine and da1 is broken or vice versa. There does not seem to be a >> pattern to this. I have worked with vinum many times before and I'm not >> inexperience but I have reached the end of the road with gmirror. I've >> tried 8 times to mirror these disks now with different configurations >> and I've failed every time. I have even alternated the sizes of the >> slices and left room at the end of the drive, at the beginning of the >> drive, etc. Here are the appropriate informational dumps: >> >> Copyright (c) 1992-2004 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 5.3-RELEASE-p5 #0: Wed Feb 23 16:19:57 PST 2005 >> root@capone.bellevuechristian.org:/usr/obj/usr/src/sys/CAPONE >> Timecounter "i8254" frequency 1193182 Hz quality 0 >> CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.19-MHz 686-class CPU) >> Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 >> >> Features=0xbfebfbff >> >> Hyperthreading: 2 logical CPUs >> real memory = 2147221504 (2047 MB) >> avail memory = 2095755264 (1998 MB) >> ACPI APIC Table: >> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >> cpu0 (BSP): APIC ID: 0 >> cpu1 (AP): APIC ID: 1 >> cpu2 (AP): APIC ID: 6 >> cpu3 (AP): APIC ID: 7 >> ioapic0: Changing APIC ID to 8 >> ioapic1: Changing APIC ID to 9 >> ioapic1: WARNING: intbase 32 != expected base 24 >> ioapic2: Changing APIC ID to 10 >> ioapic2: WARNING: intbase 64 != expected base 56 >> ioapic0 irqs 0-23 on motherboard >> ioapic1 irqs 32-55 on motherboard >> ioapic2 irqs 64-87 on motherboard >> netsmb_dev: loaded >> npx0: [FAST] >> npx0: on motherboard >> npx0: INT 16 interface >> acpi0: on motherboard >> acpi0: Power Button (fixed) >> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 >> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 >> cpu0: on acpi0 >> cpu1: on acpi0 >> cpu2: on acpi0 >> cpu3: on acpi0 >> pcib0: port 0xcf8-0xcff on acpi0 >> pci0: on pcib0 >> pcib1: at device 2.0 on pci0 >> pci1: on pcib1 >> pcib2: at device 0.0 on pci1 >> pci2: on pcib2 >> pcib3: at device 0.2 on pci1 >> pci3: on pcib3 >> mpt0: port 0xec00-0xecff mem >> 0xdfde0000-0xdfdeffff,0xdfdf0000-0xdfdfffff irq 34 at device 5.0 on pci3 >> mpt0: [GIANT-LOCKED] >> em0: port >> 0xe8c0-0xe8ff mem 0xdfdc0000-0xdfddffff irq 39 at device 12.0 on pci3 >> em0: Ethernet address: 00:0e:0c:69:3a:44 >> em0: Speed:N/A Duplex:N/A >> pcib4: at device 4.0 on pci0 >> pci4: on pcib4 >> pcib5: at device 5.0 on pci0 >> pci5: on pcib5 >> pcib6: at device 0.0 on pci5 >> pci6: on pcib6 >> em1: port >> 0xdcc0-0xdcff mem 0xdfae0000-0xdfafffff irq 64 at device 7.0 on pci6 >> em1: Ethernet address: 00:11:43:d7:64:2e >> em1: Speed:N/A Duplex:N/A >> pcib7: at device 0.2 on pci5 >> pci7: on pcib7 >> em2: port >> 0xccc0-0xccff mem 0xdf8e0000-0xdf8fffff irq 65 at device 8.0 on pci7 >> em2: Ethernet address: 00:11:43:d7:64:2f >> em2: Speed:N/A Duplex:N/A >> pcib8: at device 6.0 on pci0 >> pci8: on pcib8 >> uhci0: port 0xace0-0xacff >> irq 16 at device 29.0 on pci0 >> uhci0: [GIANT-LOCKED] >> usb0: on uhci0 >> usb0: USB revision 1.0 >> uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >> uhub0: 2 ports with 2 removable, self powered >> uhci1: port 0xacc0-0xacdf >> irq 19 at device 29.1 on pci0 >> uhci1: [GIANT-LOCKED] >> usb1: on uhci1 >> usb1: USB revision 1.0 >> uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >> uhub1: 2 ports with 2 removable, self powered >> uhub2: Dell product 0xa001, class 9/0, rev 2.00/0.00, addr 2 >> uhub2: 2 ports with 2 removable, self powered >> uhci2: port 0xaca0-0xacbf >> irq 18 at device 29.2 on pci0 >> uhci2: [GIANT-LOCKED] >> usb2: on uhci2 >> usb2: USB revision 1.0 >> uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >> uhub3: 2 ports with 2 removable, self powered >> ums0: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), rev >> 1.10/3.00, addr 2, iclass 3/1 >> ums0: 5 buttons and Z dir. >> pci0: at device 29.7 (no driver attached) >> pcib9: at device 30.0 on pci0 >> pci9: on pcib9 >> pci9: at device 13.0 (no driver attached) >> isab0: at device 31.0 on pci0 >> isa0: on isab0 >> atapci0: port >> 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 >> ata0: channel #0 on atapci0 >> ata1: channel #1 on atapci0 >> fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on >> acpi0 >> fdc0: [FAST] >> fd0: <1440-KB 3.5" drive> on fdc0 drive 0 >> atkbdc0: port 0x64,0x60 irq 1 on acpi0 >> atkbd0: irq 1 on atkbdc0 >> kbd0 at atkbd0 >> atkbd0: [GIANT-LOCKED] >> sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on >> acpi0 >> sio0: type 16550A >> orm0: at iomem >> 0xec000-0xeffff,0xcb000-0xcefff,0xc0000-0xcafff on isa0 >> pmtimer0 on isa0 >> ppc0: parallel port not found. >> sc0: at flags 0x100 on isa0 >> sc0: VGA <16 virtual consoles, flags=0x300> >> sio1: configured irq 3 not in bitmap of probed irqs 0 >> sio1: port may not be enabled >> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on >> isa0 >> Timecounters tick every 10.000 msec >> acd0: CDROM at ata0-master UDMA33 >> Waiting 15 seconds for SCSI devices to settle >> ses0 at mpt0 bus 0 target 6 lun 0 >> ses0: Fixed Processor SCSI-2 device >> ses0: 3.300MB/s transfers >> ses0: SAF-TE Compliant Device >> da0 at mpt0 bus 0 target 0 lun 0 >> da0: Fixed Direct Access SCSI-3 device >> da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged >> Queueing Enabled >> da0: 70007MB (143374650 512 byte sectors: 255H 63S/T 8924C) >> da1 at mpt0 bus 0 target 1 lun 0 >> da1: Fixed Direct Access SCSI-3 device >> da1: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged >> Queueing Enabled >> da1: 70007MB (143374650 512 byte sectors: 255H 63S/T 8924C) >> GEOM_MIRROR: Device gm0s1 created (id=1445021139). >> GEOM_MIRROR: Device gm0s1: provider da0s1 detected. >> GEOM_MIRROR: Device gm0s1: provider da1s1 detected. >> GEOM_MIRROR: Device gm0s1: provider da1s1 activated. >> GEOM_MIRROR: Cannot update metadata on disk da0s1 (error=1). >> GEOM_MIRROR: Device gm0s1: provider da0s1 activated. >> GEOM_MIRROR: Device gm0s1: provider mirror/gm0s1 launched. >> GEOM_MIRROR: Cannot update metadata on disk da0s1 (error=1). >> GEOM_MIRROR: Device gm0s1: provider da0s1 disconnected. >> SMP: AP CPU #3 Launched! >> SMP: AP CPU #1 Launched! >> SMP: AP CPU #2 Launched! >> Mounting root from ufs:/dev/mirror/gm0s1a >> em0: Link is up 100 Mbps Full Duplex >> >> >> Metadata on /dev/da1s1: >> magic: GEOM::MIRROR >> version: 1 >> name: gm0s1 >> mid: 1445021139 >> did: 4266048836 >> all: 2 >> syncid: 3 >> priority: 0 >> slice: 4096 >> balance: round-robin >> mediasize: 73402365952 >> sectorsize: 512 >> syncoffset: 0 >> mflags: NONE >> dflags: DIRTY >> hcprovider: da1s1 >> MD5 hash: c082817f594eb795a95ebb547bb20f71 >> >> >> Metadata on /dev/da0s1: >> magic: GEOM::MIRROR >> version: 1 >> name: gm0s1 >> mid: 1445021139 >> did: 1764218562 >> all: 2 >> syncid: 3 >> priority: 0 >> slice: 4096 >> balance: round-robin >> mediasize: 73402365952 >> sectorsize: 512 >> syncoffset: 22164275200 >> mflags: NONE >> dflags: DIRTY SYNCHRONIZING >> hcprovider: da0s1 >> MD5 hash: 74f4f6b2cc14a5624539431c455cab81 >> >> >> Geom name: gm0s1 >> State: DEGRADED >> Components: 2 >> Balance: round-robin >> Slice: 4096 >> Flags: NONE >> SyncID: 5 >> ID: 1445021139 >> Providers: >> 1. Name: mirror/gm0s1 >> Mediasize: 73402365952 (68G) >> Sectorsize: 512 >> Mode: r6w6e1 >> Consumers: >> 1. Name: da1s1 >> Mediasize: 73402366464 (68G) >> Sectorsize: 512 >> Mode: r6w6e2 >> State: ACTIVE >> Priority: 0 >> Flags: DIRTY, HARDCODED >> SyncID: 5 >> ID: 4266048836 >> >> Geom name: gm0s1.sync >> >> >> >> ******* Working on device /dev/da1 ******* >> parameters extracted from in-core disklabel are: >> cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) >> >> Figures below won't work with BIOS for partitions not in cyl 1 >> parameters to be used for BIOS calculations are: >> cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) >> >> Media sector size is 512 >> Warning: BIOS sector numbering starts with sector 1 >> Information from DOS bootblock is: >> The data for partition 1 is: >> sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) >> start 63, size 143363997 (70001 Meg), flag 80 (active) >> beg: cyl 0/ head 1/ sector 1; >> end: cyl 1023/ head 254/ sector 63 >> The data for partition 2 is: >> >> The data for partition 3 is: >> >> The data for partition 4 is: >> >> >> >> >> >> # /dev/mirror/gm0s1: >> 8 partitions: >> # size offset fstype [fsize bsize bps/cpg] >> a: 1024000 0 4.2BSD 2048 16384 64008 >> b: 8388608 1024000 swap >> c: 143363996 0 unused 0 0 # "raw" part, >> don't ed$ >> d: 8388608 9412608 4.2BSD 2048 16384 28552 >> e: 4194304 17801216 4.2BSD 2048 16384 28552 >> f: 10240000 21995520 4.2BSD 2048 16384 28552 >> g: 110182400 32235520 4.2BSD 2048 16384 28552 >> >> >> Any help would be greatly appreciated! I am ready to pull my hair out >> and I'm already going bald so that would be bad! >> >> Octavian Hornoiu >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> freebsd-geom@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-geom >> To unsubscribe, send any mail to "freebsd-geom-unsubscribe@freebsd.org" >> >> > > _______________________________________________ > freebsd-geom@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-geom > To unsubscribe, send any mail to "freebsd-geom-unsubscribe@freebsd.org" From owner-freebsd-geom@FreeBSD.ORG Thu Mar 17 23:46:42 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFDF516A4CE for ; Thu, 17 Mar 2005 23:46:42 +0000 (GMT) Received: from mail.hacknslash.org (bdsl.66.14.131.218.gte.net [66.14.131.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2206843D48 for ; Thu, 17 Mar 2005 23:46:39 +0000 (GMT) (envelope-from octavian@hacknslash.org) Received: (qmail 42189 invoked from network); 17 Mar 2005 23:46:51 -0000 Received: from phobos.lexis.int (HELO ?10.0.0.15?) (10.0.0.15) by mail.hacknslash.org with AES256-SHA encrypted SMTP; 17 Mar 2005 23:46:51 -0000 Message-ID: <423A16DE.1080101@hacknslash.org> Date: Thu, 17 Mar 2005 15:46:38 -0800 From: Octavian Hornoiu User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: freebsd-geom@freebsd.org References: <4236A8F3.8090105@hacknslash.org> <42375BB2.2080903@zepeda.ws> <423940C4.6010807@zepeda.ws> In-Reply-To: <423940C4.6010807@zepeda.ws> X-Enigmail-Version: 0.90.1.1 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/mixed; boundary="------------060604090403020307020502" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Re: gmirror cannot update metadata on disk da0s1 X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: octavian@hacknslash.org List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Mar 2005 23:46:42 -0000 This is a multi-part message in MIME format. --------------060604090403020307020502 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Upgrading to 5-STABLE fixed the problem immediately. Thank you all for the fast feedback! :) octavian hornoiu Daniel P. Zepeda wrote: > Here's a link on osnews detailing my experience: > > http://www.osnews.com/comment.php?news_id=9378 > > Daniel P. Zepeda wrote: > >> What worked for me was the whole disk approach, not on-a-slice, >> ensured that 'swapoff="YES" was in /etc/rc.conf, changed the reboot >> and halt commands to shell scripts to ensure I always use 'shutdown >> - when rebooting, and the final nugget was to add: >> >> kern.geom.mirror.timeout=0 >> >> to /boot/loader.conf >> >> I think that was all, if I remember anything else, I'll let you know. >> Hope it helps. >> >> DZ >> >> Octavian Hornoiu wrote: >> >>> I have followed the instructions as per the document at >>> http://people.freebsd.org/~rse/mirror/ to setup my geom mirror using >>> FreeBSD 5.3-p5 and two 70 gig SCSI maxtor drives of identical size. I >>> have tried both the whole partition gm0 and single slice gm0s1 >>> alternatives to mirroring the drives and I have tried both hardcoding >>> and without hardcoding and I still get cannot update metadata or cannot >>> read metadata or cannot write metadata. The drive with metadata >>> problems will change depending with the setup so sometimes da0 works >>> fine and da1 is broken or vice versa. There does not seem to be a >>> pattern to this. I have worked with vinum many times before and I'm not >>> inexperience but I have reached the end of the road with gmirror. I've >>> tried 8 times to mirror these disks now with different configurations >>> and I've failed every time. I have even alternated the sizes of the >>> slices and left room at the end of the drive, at the beginning of the >>> drive, etc. Here are the appropriate informational dumps: >>> >>> Copyright (c) 1992-2004 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 5.3-RELEASE-p5 #0: Wed Feb 23 16:19:57 PST 2005 >>> root@capone.bellevuechristian.org:/usr/obj/usr/src/sys/CAPONE >>> Timecounter "i8254" frequency 1193182 Hz quality 0 >>> CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.19-MHz 686-class CPU) >>> Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 >>> >>> Features=0xbfebfbff >>> >>> Hyperthreading: 2 logical CPUs >>> real memory = 2147221504 (2047 MB) >>> avail memory = 2095755264 (1998 MB) >>> ACPI APIC Table: >>> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >>> cpu0 (BSP): APIC ID: 0 >>> cpu1 (AP): APIC ID: 1 >>> cpu2 (AP): APIC ID: 6 >>> cpu3 (AP): APIC ID: 7 >>> ioapic0: Changing APIC ID to 8 >>> ioapic1: Changing APIC ID to 9 >>> ioapic1: WARNING: intbase 32 != expected base 24 >>> ioapic2: Changing APIC ID to 10 >>> ioapic2: WARNING: intbase 64 != expected base 56 >>> ioapic0 irqs 0-23 on motherboard >>> ioapic1 irqs 32-55 on motherboard >>> ioapic2 irqs 64-87 on motherboard >>> netsmb_dev: loaded >>> npx0: [FAST] >>> npx0: on motherboard >>> npx0: INT 16 interface >>> acpi0: on motherboard >>> acpi0: Power Button (fixed) >>> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 >>> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 >>> cpu0: on acpi0 >>> cpu1: on acpi0 >>> cpu2: on acpi0 >>> cpu3: on acpi0 >>> pcib0: port 0xcf8-0xcff on acpi0 >>> pci0: on pcib0 >>> pcib1: at device 2.0 on pci0 >>> pci1: on pcib1 >>> pcib2: at device 0.0 on pci1 >>> pci2: on pcib2 >>> pcib3: at device 0.2 on pci1 >>> pci3: on pcib3 >>> mpt0: port 0xec00-0xecff mem >>> 0xdfde0000-0xdfdeffff,0xdfdf0000-0xdfdfffff irq 34 at device 5.0 on pci3 >>> mpt0: [GIANT-LOCKED] >>> em0: port >>> 0xe8c0-0xe8ff mem 0xdfdc0000-0xdfddffff irq 39 at device 12.0 on pci3 >>> em0: Ethernet address: 00:0e:0c:69:3a:44 >>> em0: Speed:N/A Duplex:N/A >>> pcib4: at device 4.0 on pci0 >>> pci4: on pcib4 >>> pcib5: at device 5.0 on pci0 >>> pci5: on pcib5 >>> pcib6: at device 0.0 on pci5 >>> pci6: on pcib6 >>> em1: port >>> 0xdcc0-0xdcff mem 0xdfae0000-0xdfafffff irq 64 at device 7.0 on pci6 >>> em1: Ethernet address: 00:11:43:d7:64:2e >>> em1: Speed:N/A Duplex:N/A >>> pcib7: at device 0.2 on pci5 >>> pci7: on pcib7 >>> em2: port >>> 0xccc0-0xccff mem 0xdf8e0000-0xdf8fffff irq 65 at device 8.0 on pci7 >>> em2: Ethernet address: 00:11:43:d7:64:2f >>> em2: Speed:N/A Duplex:N/A >>> pcib8: at device 6.0 on pci0 >>> pci8: on pcib8 >>> uhci0: port 0xace0-0xacff >>> irq 16 at device 29.0 on pci0 >>> uhci0: [GIANT-LOCKED] >>> usb0: on uhci0 >>> usb0: USB revision 1.0 >>> uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >>> uhub0: 2 ports with 2 removable, self powered >>> uhci1: port 0xacc0-0xacdf >>> irq 19 at device 29.1 on pci0 >>> uhci1: [GIANT-LOCKED] >>> usb1: on uhci1 >>> usb1: USB revision 1.0 >>> uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >>> uhub1: 2 ports with 2 removable, self powered >>> uhub2: Dell product 0xa001, class 9/0, rev 2.00/0.00, addr 2 >>> uhub2: 2 ports with 2 removable, self powered >>> uhci2: port 0xaca0-0xacbf >>> irq 18 at device 29.2 on pci0 >>> uhci2: [GIANT-LOCKED] >>> usb2: on uhci2 >>> usb2: USB revision 1.0 >>> uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >>> uhub3: 2 ports with 2 removable, self powered >>> ums0: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), rev >>> 1.10/3.00, addr 2, iclass 3/1 >>> ums0: 5 buttons and Z dir. >>> pci0: at device 29.7 (no driver attached) >>> pcib9: at device 30.0 on pci0 >>> pci9: on pcib9 >>> pci9: at device 13.0 (no driver attached) >>> isab0: at device 31.0 on pci0 >>> isa0: on isab0 >>> atapci0: port >>> 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 >>> ata0: channel #0 on atapci0 >>> ata1: channel #1 on atapci0 >>> fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on >>> acpi0 >>> fdc0: [FAST] >>> fd0: <1440-KB 3.5" drive> on fdc0 drive 0 >>> atkbdc0: port 0x64,0x60 irq 1 on acpi0 >>> atkbd0: irq 1 on atkbdc0 >>> kbd0 at atkbd0 >>> atkbd0: [GIANT-LOCKED] >>> sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on >>> acpi0 >>> sio0: type 16550A >>> orm0: at iomem >>> 0xec000-0xeffff,0xcb000-0xcefff,0xc0000-0xcafff on isa0 >>> pmtimer0 on isa0 >>> ppc0: parallel port not found. >>> sc0: at flags 0x100 on isa0 >>> sc0: VGA <16 virtual consoles, flags=0x300> >>> sio1: configured irq 3 not in bitmap of probed irqs 0 >>> sio1: port may not be enabled >>> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on >>> isa0 >>> Timecounters tick every 10.000 msec >>> acd0: CDROM at ata0-master UDMA33 >>> Waiting 15 seconds for SCSI devices to settle >>> ses0 at mpt0 bus 0 target 6 lun 0 >>> ses0: Fixed Processor SCSI-2 device >>> ses0: 3.300MB/s transfers >>> ses0: SAF-TE Compliant Device >>> da0 at mpt0 bus 0 target 0 lun 0 >>> da0: Fixed Direct Access SCSI-3 device >>> da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged >>> Queueing Enabled >>> da0: 70007MB (143374650 512 byte sectors: 255H 63S/T 8924C) >>> da1 at mpt0 bus 0 target 1 lun 0 >>> da1: Fixed Direct Access SCSI-3 device >>> da1: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged >>> Queueing Enabled >>> da1: 70007MB (143374650 512 byte sectors: 255H 63S/T 8924C) >>> GEOM_MIRROR: Device gm0s1 created (id=1445021139). >>> GEOM_MIRROR: Device gm0s1: provider da0s1 detected. >>> GEOM_MIRROR: Device gm0s1: provider da1s1 detected. >>> GEOM_MIRROR: Device gm0s1: provider da1s1 activated. >>> GEOM_MIRROR: Cannot update metadata on disk da0s1 (error=1). >>> GEOM_MIRROR: Device gm0s1: provider da0s1 activated. >>> GEOM_MIRROR: Device gm0s1: provider mirror/gm0s1 launched. >>> GEOM_MIRROR: Cannot update metadata on disk da0s1 (error=1). >>> GEOM_MIRROR: Device gm0s1: provider da0s1 disconnected. >>> SMP: AP CPU #3 Launched! >>> SMP: AP CPU #1 Launched! >>> SMP: AP CPU #2 Launched! >>> Mounting root from ufs:/dev/mirror/gm0s1a >>> em0: Link is up 100 Mbps Full Duplex >>> >>> >>> Metadata on /dev/da1s1: >>> magic: GEOM::MIRROR >>> version: 1 >>> name: gm0s1 >>> mid: 1445021139 >>> did: 4266048836 >>> all: 2 >>> syncid: 3 >>> priority: 0 >>> slice: 4096 >>> balance: round-robin >>> mediasize: 73402365952 >>> sectorsize: 512 >>> syncoffset: 0 >>> mflags: NONE >>> dflags: DIRTY >>> hcprovider: da1s1 >>> MD5 hash: c082817f594eb795a95ebb547bb20f71 >>> >>> >>> Metadata on /dev/da0s1: >>> magic: GEOM::MIRROR >>> version: 1 >>> name: gm0s1 >>> mid: 1445021139 >>> did: 1764218562 >>> all: 2 >>> syncid: 3 >>> priority: 0 >>> slice: 4096 >>> balance: round-robin >>> mediasize: 73402365952 >>> sectorsize: 512 >>> syncoffset: 22164275200 >>> mflags: NONE >>> dflags: DIRTY SYNCHRONIZING >>> hcprovider: da0s1 >>> MD5 hash: 74f4f6b2cc14a5624539431c455cab81 >>> >>> >>> Geom name: gm0s1 >>> State: DEGRADED >>> Components: 2 >>> Balance: round-robin >>> Slice: 4096 >>> Flags: NONE >>> SyncID: 5 >>> ID: 1445021139 >>> Providers: >>> 1. Name: mirror/gm0s1 >>> Mediasize: 73402365952 (68G) >>> Sectorsize: 512 >>> Mode: r6w6e1 >>> Consumers: >>> 1. Name: da1s1 >>> Mediasize: 73402366464 (68G) >>> Sectorsize: 512 >>> Mode: r6w6e2 >>> State: ACTIVE >>> Priority: 0 >>> Flags: DIRTY, HARDCODED >>> SyncID: 5 >>> ID: 4266048836 >>> >>> Geom name: gm0s1.sync >>> >>> >>> >>> ******* Working on device /dev/da1 ******* >>> parameters extracted from in-core disklabel are: >>> cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) >>> >>> Figures below won't work with BIOS for partitions not in cyl 1 >>> parameters to be used for BIOS calculations are: >>> cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) >>> >>> Media sector size is 512 >>> Warning: BIOS sector numbering starts with sector 1 >>> Information from DOS bootblock is: >>> The data for partition 1 is: >>> sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) >>> start 63, size 143363997 (70001 Meg), flag 80 (active) >>> beg: cyl 0/ head 1/ sector 1; >>> end: cyl 1023/ head 254/ sector 63 >>> The data for partition 2 is: >>> >>> The data for partition 3 is: >>> >>> The data for partition 4 is: >>> >>> >>> >>> >>> >>> # /dev/mirror/gm0s1: >>> 8 partitions: >>> # size offset fstype [fsize bsize bps/cpg] >>> a: 1024000 0 4.2BSD 2048 16384 64008 >>> b: 8388608 1024000 swap >>> c: 143363996 0 unused 0 0 # "raw" part, >>> don't ed$ >>> d: 8388608 9412608 4.2BSD 2048 16384 28552 >>> e: 4194304 17801216 4.2BSD 2048 16384 28552 >>> f: 10240000 21995520 4.2BSD 2048 16384 28552 >>> g: 110182400 32235520 4.2BSD 2048 16384 28552 >>> >>> >>> Any help would be greatly appreciated! I am ready to pull my hair out >>> and I'm already going bald so that would be bad! >>> >>> Octavian Hornoiu >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> freebsd-geom@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-geom >>> To unsubscribe, send any mail to "freebsd-geom-unsubscribe@freebsd.org" >>> >>> >> >> _______________________________________________ >> freebsd-geom@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-geom >> To unsubscribe, send any mail to "freebsd-geom-unsubscribe@freebsd.org" > > > > _______________________________________________ > freebsd-geom@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-geom > To unsubscribe, send any mail to "freebsd-geom-unsubscribe@freebsd.org" --------------060604090403020307020502--