Bug 200312
Summary: | fstab mounting of different nfs servers broken | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Josko Plazonic <plazonic> | ||||
Component: | util-linux | Assignee: | Steve Dickson <steved> | ||||
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3.0 | CC: | coughlan, kzak, olle, tao | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | RHBA-2006-0657 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-08-28 14:23:08 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 190430 | ||||||
Attachments: |
|
Description
Josko Plazonic
2006-07-26 19:55:35 UTC
Fixed in mount-2.11y-31.19 *** Bug 200529 has been marked as a duplicate of this bug. *** Created attachment 133254 [details]
strace of failing mount
I just tried the package in 3.0E-errata-candidate and am still seeing the same
problem. Here's an strace from a failed "mount -t nfs -a". The first mount that
it attempts is successful, but subsequent mounts still fail.
It looks like the problem is that it consults the portmapper for the first
server to get the mountd port, and then assumes that all other servers are
using the same port.
That's exactly what is happening - maybe I didn't explain it clearly enough but read above. I also included a fix above that is confirmed to work even though it is not very elegant. BTW this is probably a significant enough regression that you should probably consider pushing this fix earlier rather than later - but don't mind me... Oops, the patch that went into -31.19 *does* seem to correct the problem. I had updated the wrong package when testing before. *** Bug 203117 has been marked as a duplicate of this bug. *** An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2006-0657.html |