File system stange behavior

[David Yucht]

Does sound like a hardware issue. I'd highly recommend checking your
memory first. Download a program called Memtest86 from memtest86.com; it's
a GPLed app that fits on a floppy and tests every bit of memory several
times. If there's a problem, it will find it. Occasionally it's found
problems with memory other diagnostic apps have missed. Just be warned a
good check run may take all day (several loops through the 11 tests).

Now, if it does detect a problem, don't flip out, just play with your
memory settings in bios first and slow things down, then retest. If it
still says there's an issue, try juggling slots and retest. If there's
_still_ an issue, well, you've got a bad module. Being the curious type,
that usually means to me that the module should be isolated and placed in
another system just to be sure it's not some goofy incompatibility with
the motherboard. Oh, and before I forget, subsequent tests after you find
an error don't need to be run all day, a good half hour or hour for one
pass of all tests is plenty.

Provided memory tests out fine, get the correct diagnostics tools from WD
and check you disks. I've got a feeling it is memory, though.

David Yucht

On Wed, 9 Jul 2003, daniel wrote:

> My hardware
> 
>  Pentium(R) 4 CPU 1.90GHz
>  RAM 1048560K bytes DDR PC2100
>  ad0: 76319MB <WDC WD800BB-00CAA0> [155061/16/63] at ata0-master UDMA100
>  motherboard ASUS PAB266-E
> 
>  I have it with a 4.5 stable upgraded to 4.7 stable with cvsup
>  After I discover the problem of which I talk below, I reinstalled all the 
> computer with 4.8 stable, but this was not a solution to my problem.
>  There are some weird behavior on the file system.
>  I discover it with the security run output and his heading setuid diffs:
>  Some files cannot be accessed by the find of the command.
>  there are some directory corruption on the file system.
> 
>  for example a exit of it:
> 
>  find: /usr/ports/security/libfwbuilder/Makefilÿ: No such file or directory
> 
> the file exist but the directory is corrupted
> if I do an odd -t a on the directory I've got the character FF instead off E
> When I am in this situation I can't do anything with theses files , rm find 
> etc ... cannot find them. There are always an error when I try to access 
> the files referenced in the directory.
> But this behavior is not permanent. I can have it for 15 days and after 
> that I find again my directory and files ok, without doing anything
> 
> Another thing : one time I 've got some rights on files who has been 
> modified too. In this case it was possible to put the right rights on them.
> 
> At last the system reboot frequently ( every month in average ) with 
> inconsistency in the file system. I must run fsck to repair. Since I am in 
> 4.8 the system always reboot but without inconsistency in the file system.
> 
> two error different for the reboot I found in dmesg.boot
>     panic: ufsdirhash_findfree: free mismatch
> and
>     Fatal trap 12: page fault while in kernel mode
> 
>  I must say that I have the same configuration on another computer who work 
> well for years ago.
> 
>  I don't know what part of hardware is in charge of this problem. If 
> someone have a clue for me Thanks
> 
>  Daniel Madaoui daniel at hackywhacky.com
>  
> _______________________________________________
> freebsd-hardware at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
> To unsubscribe, send any mail to "freebsd-hardware-unsubscribe at freebsd.org"
>