Bug 140053
Summary: | NFS Buggy Server Error upon reboot | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Paul J Sidoti <psidoti> |
Component: | nfs-utils | Assignee: | Jeff Layton <jlayton> |
Status: | CLOSED WONTFIX | QA Contact: | Ben Levenson <benl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | shillman, staubach, steved |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-19 19:21:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Paul J Sidoti
2004-11-19 15:08:15 UTC
In order for root to see an NFS mounted file system, it needs to have been exported no_root_squash. Did you do this? Nope. Never had the problem before. the nfs drives are mounted via the /etc/fstab file. nas-head:/u27 /u27 nfs defaults 1 2 How would I modify the file? Like this? nas-head:/u27 /u27 nfs no_root_sqash 1 2 That looks about right (not sure if you need to include defaults as well or not), although you've spelled 'no_root_squash' incorrectly. You're missing the 'u'. Have you tried that? AS2.1 is now in maintenance mode. If a problem isn't catastrophic then it probably won't be addressed. That said, this error usually indicates a server-side problem. What sort of server is this? no_root_squash is also an export option, not a mount option. root will still be able to see the NFS filesystem without that export option, it's just that uid=0 will be translated to an unprivileged user (usu nobody or nfsnobody). This bug is filed against RHEL2.1, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |