From owner-freebsd-current Thu Feb 27 1:53:11 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 AAB6B37B401; Thu, 27 Feb 2003 01:53:09 -0800 (PST) Received: from MX4.estpak.ee (ld1.estpak.ee [194.126.101.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CA1543FAF; Thu, 27 Feb 2003 01:53:08 -0800 (PST) (envelope-from kalts@estpak.ee) Received: from kevad.internal (80-235-41-151-dsl.mus.estpak.ee [80.235.41.151]) by MX4.estpak.ee (Postfix) with ESMTP id 66CA21D001D; Thu, 27 Feb 2003 11:53:06 +0200 (EET) Received: (from vallo@localhost) by kevad.internal (8.12.6/8.12.6/Submit) id h1R9r30Z001313; Thu, 27 Feb 2003 11:53:03 +0200 (EET) (envelope-from vallo) Date: Thu, 27 Feb 2003 11:53:02 +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: <20030227095302.GA1183@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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030227012959.GA89235@wantadilla.lemis.com> 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:59:59AM +1030, Greg 'groggy' Lehey wrote: > > The crashes and anomalies with filesystem residing on R5 volume were > > related to vinum(R5)/softupdates combo. > > Well, at one point we suspected that. But the cases I have seen were > based on a misassumption. Do you have any concrete evidence that > points to that particular combination? Don't have any other evidence than the case I was describing. After changing my employer I hadn't had much time or motivation to try again. > > 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. Thanks -- Vallo Kallaste To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message