Bug 179188 - unable to use hostname in /etc/exports
unable to use hostname in /etc/exports
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: nfs-utils (Show other bugs)
4.0
i686 Linux
medium Severity low
: ---
: ---
Assigned To: Steve Dickson
Red Hat Kernel QE team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-01-27 17:52 EST by Don Buchholz
Modified: 2012-06-20 12:18 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 12:18:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Don Buchholz 2006-01-27 17:52:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050921 Red Hat/1.0.7-1.4.1 Firefox/1.0.7

Description of problem:

Desire is to grant most hosts read-only NFS access.  However, one specific system is to be allowed read-write access.

  Non-working /etc/exportfs
  -------------------------
  /export/d0/iSSSp/build wozniak.corp.imoveinc.com/32(rw,no_root_squash,sync)
  /export/d0/iSSSp/build 192.168.5.0/24(ro,root_squash,sync) 192.168.15.0/24(ro,root_squash,sync) *.4sensor.imoveinc.com(ro,root_squash,sync) *.swflant.imoveinc.com(ro,root_squash,sync) *.g4.imoveinc.com(ro,root_squash,sync)

Users on host 'wozniak' who attempt to write to the NFS-mounted filesystem are told the file system is mounted read-only.  To fix the problem, remove the hostname, and replace it with an IP address.

  Working /etc/exportfs
  ---------------------
  /export/d0/iSSSp/build 192.168.5.40/32(rw,no_root_squash,sync)
  /export/d0/iSSSp/build 192.168.5.0/24(ro,root_squash,sync) 192.168.15.0/24(ro,root_squash,sync) *.4sensor.imoveinc.com(ro,root_squash,sync) *.swflant.imoveinc.com(ro,root_squash,sync) *.g4.imoveinc.com(ro,root_squash,sync)



Version-Release number of selected component (if applicable):
nfs-utils-1.0.6-65.EL4.i386.rpm

How reproducible:
Always

Steps to Reproduce:
1. Use "wozniak.corp.imoveinc.com" in the /etc/exports file.
2. Reboot both NFS-server (dirac) and NFS-client (wozniak).
3. Login as (non-root) user w/ [alleged] write access to the exported directory.  Try to "touch foo".  It won't work.
4. Go to NFS server, and substitute "192.168.5.40" for the hostname in the exportfs file.  
5. Reboot both NFS-server (dirac) and NFS-client (wozniak).
6. Login as (non-root) user w/ [alleged] write access to the exported directory -- "touch foo".  Now it works.

  

Actual Results:  Export w/ hostname causes client to see a "read-only" filesystem.  User cannot modify data on exported filesystem.

Expected Results:  Users should be able to update their data.

Additional info:

Using the "mount" command, the client reports:
  automount(pid544) on /net/iSSSp type autofs (rw,fd=5,pgrp=544,minproto=2,maxproto=3)
[note the "rw"] even when attempts to write via NFS fail.

<whine> Our network team is including a global re-addressing of all hosts when our company moves to a new facility later this quarter.  Having to specify IP addresses in configuration files (rather than hostnames) is only going to make the changes more difficult.  </whine>  :-)
Comment 1 Jiri Pallich 2012-06-20 12:18:51 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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