Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 14 Apr 1996 09:57:39 +0200 (MET DST)
From:      sos@FreeBSD.org
To:        scrappy@ki.net (Marc G. Fournier)
Cc:        current@FreeBSD.org
Subject:   Re: File System Corruption *sigh*
Message-ID:  <199604140757.JAA03788@DeepCore.dk>
In-Reply-To: <Pine.BSI.3.92.960414021128.5278A-100000@freebsd.ki.net> from "Marc G. Fournier" at Apr 14, 96 02:24:40 am

next in thread | previous in thread | raw e-mail | index | archive | help
In reply to Marc G. Fournier who wrote:
> 
> 
> 	I'm not having much luck with this -current machine, hardware
> or software yet to be determined... :(
----- 
> 	For warnings under /usr/src/sys/compile/freebsd.  Figuring them
> for mere warnings, I kind of ignored them, but then got curious, since I've
> never seen that warning before, so checked out the file, and found this
> at line 52:
> 
> #define _BSD_SIZE_T_    unsigned int            /* sizeof ) *
> #d`fin` _BSD_SSIZE_T_   int                     /* byte count or error */
> #define _BSD_TIME_T_    long                    /* time() */
> 
> 	Notice, as well, the corruption at the end of the BSD_SIZE_T
> define...
> 
> 	I am using nfs mounts for various things, but my /usr, /usr/src
> and /usr/include directories are all local, so I would presume that the
> nfs mounts wouldn't affect this.
> 
> 	Other then the memory being in question, this machine is a
> 486DX2-66 w/ 16Meg of RAM, an Adaptec 1542CF SCSI controller and a
> SCSI hard drive:
> 
> (aha0:0:0): "UNISYS U0531 ST3600N 8374" type 0 fixed SCSI 2
> sd0(aha0:0:0): Direct-Access 500MB (1025920 512 byte sectors)

I've seen this type of error MANY times over the last half year on
many different hw setups, the only common factor is that they all
uses SCSI disk, but I think that is coincidence.
A surefire way for me to reproduce this is to checkout a complete
src-tree while a kernel-build is running, that way I get 2-3 files
corrupted like this in the whole tree :(
Oh, and none of the systems I see failing uses nfs....

I have searched high and low for explanations to this, but havn't been
able to come up with any hard evidence. My gut feeling though is that
its VM related, some buffer mess up of sorts....


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt               (sos@FreeBSD.org)               FreeBSD Core Team
                Even more code to hack -- will it ever end
..



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604140757.JAA03788>