From owner-freebsd-current Sat Mar 1 10:44: 7 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17C3D37B401; Sat, 1 Mar 2003 10:43:21 -0800 (PST) Received: from MX1.estpak.ee (ld3.estpak.ee [194.126.101.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9330743FBD; Sat, 1 Mar 2003 10:43:18 -0800 (PST) (envelope-from kalts@estpak.ee) Received: from kevad.internal (80-235-42-86-dsl.mus.estpak.ee [80.235.42.86]) by MX1.estpak.ee (Postfix) with ESMTP id 6AD038884A; Sat, 1 Mar 2003 20:41:56 +0200 (EET) Received: (from vallo@localhost) by kevad.internal (8.12.6/8.12.6/Submit) id h21IhBis000704; Sat, 1 Mar 2003 20:43:11 +0200 (EET) (envelope-from vallo) Date: Sat, 1 Mar 2003 20:43:10 +0200 From: Vallo Kallaste To: "Greg 'groggy' Lehey" Cc: Darryl Okahata , current@FreeBSD.org Subject: Re: Vinum R5 [was: Re: background fsck deadlocks with ufs2 and big disk] Message-ID: <20030301184310.GA631@kevad.internal> Reply-To: kalts@estpak.ee References: <20030220200317.GA5136@kevad.internal> <200302202228.OAA03775@mina.soco.agilent.com> <20030221080046.GA1103@kevad.internal> <20030227012959.GA89235@wantadilla.lemis.com> <20030227095302.GA1183@kevad.internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030227095302.GA1183@kevad.internal> User-Agent: Mutt/1.5.1i-ja.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 27, 2003 at 11:53:02AM +0200, Vallo Kallaste wrote: > > > The vinum R5 and system as a whole were stable without > > > softupdates. Only one problem remained after disabling softupdates, > > > while being online and user I/O going on, rebuilding of failed disk > > > corrupt the R5 volume completely. > > > > Yes, we've fixed a bug in that area. It had nothing to do with soft > > updates, though. > > Oh, that's very good news, thank you! Yes, it had nothing to do with > soft updates at all and that's why I had the "remained after" in the > sentence. > > > > Don't know is it fixed or not as I don't have necessary hardware at > > > the moment. The only way around was to quiesce the volume before > > > rebuilding, umount it, and wait until rebuild finished. I'll suggest > > > extensive testing cycle for everyone who's going to work with vinum > > > R5. Concat, striping and mirroring has been a breeze but not so with > > > R5. > > > > IIRC the rebuild bug bit any striped configuration. > > Ok, I definitely had problems only with R5, but you certainly know > much better what it was exactly. I'll need to lend 50-pin SCSI cable > and test vinum again. Will it matter on what version of FreeBSD I'll > try on? My home system runs -current of Feb 5, but if you suggest > -stable for consistent results, I'll do it. So I did. Loaned two SCSI disks and 50-pin cable. Things haven't improved a bit, I'm very sorry to say it. The entire test session (script below) was done in single user. To be fair, I did tens of them, and the mode doesn't matter. Complete script: Script started on Sat Mar 1 19:54:45 2003 # pwd /root # dmesg Copyright (c) 1992-2003 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.0-CURRENT #0: Sun Feb 2 16:16:49 EET 2003 root@vallo.internal:/usr/home/vallo/Kevad-5.0 Preloaded elf kernel "/boot/kernel/kernel" at 0xc0516000. Preloaded elf module "/boot/kernel/vinum.ko" at 0xc05160b4. Preloaded elf module "/boot/kernel/ahc_pci.ko" at 0xc0516160. Preloaded elf module "/boot/kernel/ahc.ko" at 0xc051620c. Preloaded elf module "/boot/kernel/cam.ko" at 0xc05162b4. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 132955356 Hz CPU: Pentium/P54C (132.96-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping = 6 Features=0x1bf real memory = 67108864 (64 MB) avail memory = 59682816 (56 MB) Intel Pentium detected, installing workaround for F00F bug Initializing GEOMetry subsystem VESA: v2.0, 4096k memory, flags:0x0, mode table:0xc037dec2 (1000022) VESA: ATI MACH64 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xff90-0xff9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ahc0: port 0xf800-0xf8ff mem 0xffbee000-0xffbeefff irq 10 at device 13.0 on pci0 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs pci0: at device 14.0 (no driver attached) atapci1: port 0xff00-0xff3f,0xffe0-0xffe3,0xffa8-0xffaf,0xffe4-0xffe7,0xfff0-0xfff7 mem 0xffbc0000-0xffbdffff irq 11 at device 15.0 on pci0 ata2: at 0xfff0 on atapci1 ata3: at 0xffa8 on atapci1 orm0: