Date: Thu, 27 Feb 2003 11:59:59 +1030 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Vallo Kallaste <kalts@estpak.ee> Cc: Darryl Okahata <darrylo@soco.agilent.com>, current@FreeBSD.ORG Subject: Re: Vinum R5 [was: Re: background fsck deadlocks with ufs2 and big disk] Message-ID: <20030227012959.GA89235@wantadilla.lemis.com> In-Reply-To: <20030221080046.GA1103@kevad.internal> References: <20030220200317.GA5136@kevad.internal> <200302202228.OAA03775@mina.soco.agilent.com> <20030221080046.GA1103@kevad.internal>
next in thread | previous in thread | raw e-mail | index | archive | help
--bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Friday, 21 February 2003 at 10:00:46 +0200, Vallo Kallaste wrote: > On Thu, Feb 20, 2003 at 02:28:45PM -0800, Darryl Okahata > <darrylo@soco.agilent.com> wrote: > >> Vallo Kallaste <kalts@estpak.ee> wrote: >> >>> I'll second Brad's statement about vinum and softupdates >>> interactions. My last experiments with vinum were more than half a >>> year ago, but I guess it still holds. BTW, the interactions showed >>> up _only_ on R5 volumes. I had 6 disk (SCSI) R5 volume in Compaq >>> Proliant 3000 and the system was very stable before I enabled >>> softupdates.. and of course after I disabled softupdates. In between >>> there were crashes and nasty problems with filesystem. Unfortunately >>> it was production system and I hadn't chanche to play. >> >> Did you believe that the crashes were caused by enabling softupdates on >> an R5 vinum volume, or were the crashes unrelated to vinum/softupdates? >> I can see how crashes unrelated to vinum/softupdates might trash vinum >> filesystems. > > 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? > 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. > 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. Greg -- See complete headers for address and phone numbers Please note: we block mail from major spammers, notably yahoo.com. See http://www.lemis.com/yahoospam.html for further details. --bp/iNruPH9dso1Pn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE+XWoXIubykFB6QiMRAhoBAJ9f7Ub1jCMWrUHMyf4xHFTPXGRpsQCcDWeG FQN0K/QaxoIv9GcylDqmZFM= =F622 -----END PGP SIGNATURE----- --bp/iNruPH9dso1Pn-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030227012959.GA89235>