Date: Thu, 11 Mar 2004 01:00:43 -0800 (PST) From: nils mccarthy <nils@shkoo.com> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/64091: nfs data corruption at end of file Message-ID: <200403110900.i2B90hFR052165@www.freebsd.org> Resent-Message-ID: <200403110910.i2B9ACYT057168@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 64091 >Category: kern >Synopsis: nfs data corruption at end of file >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Mar 11 01:10:12 PST 2004 >Closed-Date: >Last-Modified: >Originator: nils mccarthy >Release: 5.2.1-RELEASE >Organization: >Environment: FreeBSD fbsd5.whatzit.org 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0: Mon Feb 23 20:45:55 GMT 2004 root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC i386 >Description: Running tail -f or equivalent on nfs-mounted file that grows will occasionally result in corrupted data being returned. Specifically, NUL characters will show up. (problem also exists in 4.8-RELEASE) >How-To-Repeat: Download and compile readtest and writetest from http://www.llnw.com/fbsd-nfs-bug/. Run writetest on NFS server and readtest on NFS client, both in the same directory. After a while (under 5 minutes on my system), readtest will report that it received a bogus character that was not part of the pattern that writetest was writing. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403110900.i2B90hFR052165>