Bug 45525 - NFS can not export a FAT partition
Summary: NFS can not export a FAT partition
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: nfs-server (Show other bugs)
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Steve Dickson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-06-22 15:15 UTC by Christian Lepine
Modified: 2007-04-18 16:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-08-11 10:40:57 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Christian Lepine 2001-06-22 15:15:57 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

Description of problem:
When I try to export a FAT partition, I get a Invalid argument when I 
restart NFS.

How reproducible:
Always

Steps to Reproduce:
1.Export a FAT partition in /etc/exports in rw mode
2.Restart NFS

	

Actual Results:  Invalid argument

Expected Results:  The NFS export is available in the client computer

Additional info:
Comment 1 Arjan van de Ven 2001-06-22 15:38:47 UTC 
FAT cannot be NFS exported. NFS requires inode-numbers to be consistent,
while FAT doesn't have inode numbers so the kernel can only make numbers up,
which as a result aren't consistent (across reboots)
Comment 2 Christian Lepine 2001-06-22 16:51:43 UTC 
It was working with RedHat 7.0 !
Comment 3 Patrice Guay 2003-11-19 16:58:20 UTC 
I exported a VFAT filesystem via NFS with read-write permissions.
When I try to copy files to this disk (cp -auf ...), the first files
are copied correctly then it starts complaining about the NFS file
handle (French message : "panne d'accès au fichier NFS") and skips all
the remaining files with the same error message.
Note You need to log in before you can comment on or make changes to this bug.