nfs-server silent data corruption
Mike Tancsa
mike at sentex.net
Mon Apr 21 16:06:33 UTC 2008
At 10:52 AM 4/21/2008, Arno J. Klaassen wrote:
>Device is :
>
>nfe0 at pci0:0:10:0: class=0x068000 card=0x289510f1
>chip=0x005710de rev=0xa3 hdr=0x00
> vendor = 'Nvidia Corp'
> device = 'nForce4 Ultra NVidia Network Bus Enumerator'
> class = bridge
> cap 01[44] = powerspec 2 supports D0 D1 D2 D3 current D0
>
>(this is with the default BIOS setting " LAN Bridge Enabled", disabling
> that setting makes pciconf say "class = network" but does not influence
> my problem)
>
>I will restart my tests now by populating all 4G to only CPU1 and
>say whether that matters.
Hi,
How long does it take for the problem to show up ? I have what
appears to be a very similar Tyan board (I have an Socket 939 X2 cpu)
with the same NIC, but this one is running RELENG_7 from April
17th. There have been a few fixes for the nfe driver since 7.0
I am running this small script below on a nfs client (em nic) against
the server (nfe) ( mount options on the client 192.168.245.1:/backup
/backup nfs rw,-r=32768,-w=32768,tcp,noauto )
#!/bin/sh
i=0
while true
do
i=`expr $i + 1`
dd if=/dev/urandom of=/tmp/junk.txt bs=1024 count=81920 > /dev/null 2>&1
cp -p /tmp/junk.txt /backup/
orig=`md5 -q /tmp/junk.txt`
umount /backup
sleep 2
mount /backup
copy=`md5 -q /backup/junk.txt`
echo "$orig and $copy on $i"
if [ $orig != $copy ]; then
echo "\a copy not ok on $i"
exit 255
fi
done
On the server, I have
nfe0 at pci0:0:10:0: class=0x068000 card=0x286510f1
chip=0x005710de rev=0xa3 hdr=0x00
vendor = 'Nvidia Corp'
device = 'nForce4 Ultra NVidia Network Bus Enumerator'
class = bridge
cap 01[44] = powerspec 2 supports D0 D1 D2 D3 current D0
# ifconfig nfe0
nfe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=10b<RXCSUM,TXCSUM,VLAN_MTU,TSO4>
ether 00:e0:81:58:91:6a
inet 192.168.245.1 netmask 0xffffff00 broadcast 192.168.245.255
media: Ethernet autoselect (1000baseTX <full-duplex,flag0,flag1>)
status: active
How long does it take for the problem to come up ?
---Mike
More information about the freebsd-stable
mailing list