Date: Wed, 28 Jun 2000 08:55:05 +0200 From: Sameh Ghane <sw@anthologeek.net> To: Josef Karthauser <joe@pavilion.net> Cc: Matthew Jacob <mjacob@feral.com>, Akinori -Aki- MUSHA <knu@idaemons.org>, andrews@technologist.com, mckusick@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/contrib/softupdates softdep.h ffs_softdep.c Message-ID: <20000628085505.A31310@anthologeek.net> In-Reply-To: <20000628012956.B19558@pavilion.net>; from joe@pavilion.net on Wed, Jun 28, 2000 at 01:29:56AM %2B0100 References: <20000627172831.G32373@pavilion.net> <Pine.BSF.4.05.10006270929120.25569-100000@semuta.feral.com> <20000628012956.B19558@pavilion.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Le Wed, Jun 28, 2000 at 01:29:56AM +0100, Josef Karthauser ecrivit: > On Tue, Jun 27, 2000 at 09:29:24AM -0700, Matthew Jacob wrote: > > > > > > I'm not sure.... I have a feeling that there are softupdate problems > > > running under SMP. A number of times this year I've lost whole filesystems > > > on an SMP machines. :( > > > > Really? Have you told Kirk? > > > > No because I've not had a chance to test it - it's on a production > webserver. It's running 3.4 currently, and I've had a couple of > crashes over the last year. The first one produced a lot of > 'SOFTUPDATE INCONSISTANCY' errors and lost a lot of files - we had > to recover from tape and diff to see which files had been lost. > More recently a friend of mine was having crashes doing a make > world under 4.0 with SMP and softupdate. Switching softupdates > off caused the crashes to go away. > > The thing that worries me is that softupdates is supposed to render > the filesystem safe so that if a crash occurs we only loose recent > data. In both my cases we lost data that hadn't been touched for > years - i.e. ports tree data that hasn't ever been touched. It > definitely wasn't in the buffer cache before the crash. ! > > Is anyone else here using softupdates in an SMP environment? Yes, without any problem (80 days uptime, and so on) on a 4.0-STABLE server. Last time I had a softupdate inconsistancy during a fsck was because of poor RAM. It was not a SMP server, but the machine crashed every 2 days, but other problems (SIG11) were already present. I changed the RAM, and from this time the machine is up. We also never had any problem with sofupdates activated on mono-processor production servers. From the game server to the mail server. Using ccd or not, from 3.4 to 5.0 servers. Except the inconsistency caused by defficient RAM, we never met a problem with sofupdates, with about 30 production servers, and not less than 4 different versions of FreeBSD. Sameh. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000628085505.A31310>