From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 31 03:10:21 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5881616A4CF for ; Tue, 31 Aug 2004 03:10:21 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3149843D53 for ; Tue, 31 Aug 2004 03:10:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i7V3ALwc068496 for ; Tue, 31 Aug 2004 03:10:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i7V3ALBX068495; Tue, 31 Aug 2004 03:10:21 GMT (envelope-from gnats) Resent-Date: Tue, 31 Aug 2004 03:10:21 GMT Resent-Message-Id: <200408310310.i7V3ALBX068495@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Axel Gonzalez Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02C8C16A4D0 for ; 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 ; 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 ; 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 To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/71173: nfs writing problems on exported msdosfs X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2004 03:10:21 -0000 >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@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: