Bug 6517 - nfs server default install won't cross file systems
nfs server default install won't cross file systems
Product: Red Hat Linux
Classification: Retired
Component: nfs-server (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-10-29 17:20 EDT by maxfield
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-10-30 09:09:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description maxfield 1999-10-29 17:20:14 EDT
/home is mounted on a separate partition from /

 export / to a machine, with no root squash

 on the machine to be mounting the directory under /remote,
do this:

 mount -t nfs exportmachine:/ /remote
 cp -av /home/* /remote/home

 you will get a list of files. you can
cd /remote/home

 and the files will be there.

  telnet into the exportmachine, then
cd /home

  the files are not there.  They are on the root file
system somewhere "underneath the [directory] rug." <grin>
Comment 1 Jeff Johnson 1999-10-30 09:09:59 EDT
Knfsd does not cross partitions, unlike the older user-space
nfs-server. Each partition on the server needs to be exported
separately, and clients must mount each partition.

FWIW, the new behavior of knfsd is more typical of NFS implementations
than the older nfs-server was.

Note You need to log in before you can comment on or make changes to this bug.