Re: filesystem corruption with kernel built on Friday.

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:Another question though. Why would an executable, residing on an nfs mounted
:disk, suddenly appear to be corrupt and segv every time I run it.
:
:One minute it works, next it doesn't. Reboot and the problem goes away.
:
:Last time I saw something similar, it looked like the first 4k of the=20
:executable had been replaced with 0's. This time the corruption must be
:somewhere in the middle of the executable, or else it wouldn't even try
:to start, right ?
:
:Andrew.

    That sounds like corruption in the VM page cache, and is suspiciously
    similar to an issue David Rhodus had yesterday.   And if its an NFS
    based binary then it isn't filesystem corruption that is the cause.

    I would say there is definitely something still going on here, but I'm
    having trouble reproducing it.  I'm running three different filesystem
    tester and a buildworld -j 8 loop simultaniously on my test box and
    it's working perfectly with mmxopt turned on.

    I'll go over all the commits in the last two weeks and try to find the
    cause.

    Are you running anything on your system that might be using posix locks?
    Like Samba or smbfs?  Maybe I am looking in the wrong place.

					-Matt