Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Jun 2000 09:57:58 +0100
From:      Brian Somers <brian@Awfulhak.org>
To:        Blaz Zupan <blaz@amis.net>
Cc:        Matthew Jacob <mjacob@feral.com>, Josef Karthauser <joe@pavilion.net>, mckusick@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, brian@hak.lan.Awfulhak.org
Subject:   Re: cvs commit: src/sys/contrib/softupdates softdep.h ffs_softdep.c 
Message-ID:  <200006280857.JAA01868@hak.lan.Awfulhak.org>
In-Reply-To: Message from Blaz Zupan <blaz@amis.net>  of "Wed, 28 Jun 2000 08:42:46 %2B0200." <Pine.BSF.4.21.0006280828200.65568-100000@titanic.medinet.si> 

next in thread | previous in thread | raw e-mail | index | archive | help
I have two development boxes - a home machine with 6 scsi disks and 
an ide disk and a laptop with one ide disk.

When these machines crash, I never see any fsck-failing errors on my 
laptop, however, on my home machine, /cvs and /usr (both SCSI) almost 
always fail the fsck, forcing a manual fsck and a bunch of files being 
introduced to lost+found.

From what I can tell however, the files are always recently updated 
files.

Perhaps there's an issue either with SCSI disks in general (unlikely) 
or with multiple disks - perhaps even mixing SCSI with IDE.

Or perhaps I just have two mis-behaving drives that don't write 
things in the order they say they do.  If this is the case, 
softupdates will need to be able to identify that sort of drive 
before going prime-time....

> > Your comments are a bit unfair. *You* haven't been running the currently
> > released product with Softupdates. You have excellent reasons to be concerned
> > because of your previous experience, but your statement of "A number of times
> > this year I've lost whole filesystems on an SMP..." is misleading at best.
> 
> How about
> 
> 	http://www.freebsd.org/cgi/query-pr.cgi?pr=17122
> 
> I remember hitting this on a couple of 3.4 boxes and had to turn off
> softupdates (those were production machines). It was not even a SMP machine.
> The PR is still open, and I guess still present in 4.0 (I vaguely remember
> hitting it on a 4.0 box as well, where I forgot to turn off softupdates). The
> PR is talking about the machine crashing every 1-3 days, mine was crashing
> more like twice per month. Since that time I don't turn on softupdates on any
> of my production boxes.
> 
> Unfortunetlly I cannot contribute anything to the PR itself, as:
> 1. All the machines that exhibited the problem where production machines.
> 2. My home work box (running 5.0-CURRENT) doesn't exhibit the problem,
>    probably because it is being turned off every day and there is no real load
>    on the machine.
> 3. When the machines crashed, I didn't have a debug kernel running so the
>    crashdumps would be mostly useless.
> 
> Blaz Zupan,  Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia
> E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325

-- 
Brian <brian@Awfulhak.org>                        <brian@[uk.]FreeBSD.org>
      <http://www.Awfulhak.org>;                   <brian@[uk.]OpenBSD.org>
Don't _EVER_ lose your sense of humour !




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?200006280857.JAA01868>