amd64/71173: nfs writing problems on exported msdosfs

[Axel Gonzalez]

>Number:         71173
>Category:       amd64
>Synopsis:       nfs writing problems on exported msdosfs
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Aug 31 03:10:20 GMT 2004
>Closed-Date:
>Last-Modified:
>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 at 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:
>Unformatted: