Date: Sun, 3 Dec 1995 14:54:52 -0500 (EST) From: "Ron G. Minnich" <rminnich@Sarnoff.COM> To: hackers@freebsd.org Subject: HELP -- strange file system corruption under freebsd Message-ID: <Pine.SUN.3.91.951203145148.27774D-100000@terra>
next in thread | raw e-mail | index | archive | help
my friends at penn are having weird problems on their freebsd boxes. The machines load and run fine, then at some point the file system gets hosed and can't be repaired -- they have to reload. Windows 3.1 and linux do not have any problems (!?). Any ideas would be most appreciated. This has been seen under 2.05R and 2.10R. Ron Minnich |Like a knife through Daddy's heart: rminnich@sarnoff.com |"Don't make fun of Windows, daddy! It takes care (609)-734-3120 | of all my files and it's reliable and I like it". ---------- Forwarded message ---------- Date: Fri, 1 Dec 1995 18:55:54 -0500 (EST) From: Jeffrey D. Chung <jdchung@viper.cis.upenn.edu> Subject: Re: EXACT configuration of your machines > can you send me the: > motherboard type, motherboard bios, motherboard bios revision, cache > type, scsi controller type, disk type, display card type. And a succint > problem definitino. I'm going to put the question to freebsd-hackers as > to what the heck is going on. > ron Motherboard Type: Tyan S1466 Motherboard Motherboard Revision: 1.1 Cache Type: 8ns SyncBurst (note the 8ns time. This is very new.) SCSI Controller: Adaptec 2940 Disk Type: Conner & HP SCSI II (If you need the exact type, let me know -- but the problems occur with both Conner & HP disks) Display Card: ATI Mach 64 card (I already checked with ATI. There are no known problems with our version of the card and the Triton chipset/Adaptec 2940 -- unlike previous versions) Periodically, the filesystems will corrupt themselves and cannot be fixed by a simple fsck. It seems to happen under low loads -- we cannot reproduce the effect using any disk-thrashing program, but nonetheless depending configuration - it appears to happen once every two weeks or so... (when we're not looking of course) It is unclear what actually happens to the filesystem... It just becomes corrupted. Next time it happens, we'll examine the inode structures... -Jeff.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.91.951203145148.27774D-100000>