Bug 71173

Summary: nfs writing problems on exported msdosfs
Product: Base System Reporter: Axel Gonzalez <loox>
Component: amd64Assignee: freebsd-amd64 (Nobody) <amd64>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 6.0-CURRENT   
Hardware: Any   
OS: Any   

Description Axel Gonzalez 2004-08-31 04:10:20 UTC 
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.

Fix: 

Use UFS for exports
How-To-Repeat: Export a msdosfs dir on amd64
Access from a client

(from client):
cp file /share/
ls /share/file
Comment 1 Tim Robbins freebsd_committer freebsd_triage 2004-09-08 14:07:08 UTC 
State Changed
From-To: open->patched

Should be fixed in -CURRENT now.
Comment 2 Tim Robbins freebsd_committer freebsd_triage 2004-09-11 04:23:13 UTC 
State Changed
From-To: patched->closed

Now fixed in RELENG_5.