From nobody@FreeBSD.org  Tue Aug 31 03:00:47 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 02C8C16A4D0
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 31 Aug 2004 03:00:22 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0651743D46
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 31 Aug 2004 03:00:22 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i7V30LV2026277
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 31 Aug 2004 03:00:21 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i7V30LAp026276;
	Tue, 31 Aug 2004 03:00:21 GMT
	(envelope-from nobody)
Message-Id: <200408310300.i7V30LAp026276@www.freebsd.org>
Date: Tue, 31 Aug 2004 03:00:21 GMT
From: Axel Gonzalez <loox@e-shell.net>
To: freebsd-gnats-submit@FreeBSD.org
Subject: nfs writing problems on exported msdosfs
X-Send-Pr-Version: www-2.3

>Number:         71173
>Category:       amd64
>Synopsis:       nfs writing problems on exported msdosfs
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-amd64
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Aug 31 03:10:20 GMT 2004
>Closed-Date:    Sat Sep 11 03:24:02 GMT 2004
>Last-Modified:  Sat Sep 11 03:24:02 GMT 2004
>Originator:     Axel Gonzalez
>Release:        6.0-CURRENT
>Organization:
>Environment:
FreeBSD moonlight.e-shell.net 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Sat Aug 28 12:43:02 CDT 2004 root@moonlight.e-shell.net:/usr/obj/usr/src/sys/LXAMD64 amd64       
>Description:
When using NFS to export a msdosfs dir (on amd64 as server), there are problems when a client tries to write on the exported dir.

Clients can read directories and files without a problem (checksums are ok).

When client tries to write a file, result is 0 sized files on the server, name is correct. On large files, it takes some time to copy the file (like its actually sending data over network). No errror messages on server or client.


Client also sees some strange things (this commands on client):

# cp file /share/
# ls /share | grep file
(shows file)

# ls /share/file
(no such file or directory)

# md5 /share/file
(no such file or directory)


Rebooting the client has no effect (same behavior).


Tried with 5.2.1 and 6-current (i386) clients. Can't tell if this problem is for i386 as server too.


Writing works fine on UFS exports.

>How-To-Repeat:
Export a msdosfs dir on amd64
Access from a client

(from client):
cp file /share/
ls /share/file
>Fix:
Use UFS for exports
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->patched 
State-Changed-By: tjr 
State-Changed-When: Wed Sep 8 13:07:08 GMT 2004 
State-Changed-Why:  
Should be fixed in -CURRENT now. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=71173 
State-Changed-From-To: patched->closed 
State-Changed-By: tjr 
State-Changed-When: Sat Sep 11 03:23:13 GMT 2004 
State-Changed-Why:  
Now fixed in RELENG_5. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=71173 
>Unformatted:
