Bug 984676
Summary: | Command line cifs mount failing with "Unable to find suitable address." | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John William <jw2357> |
Component: | kernel | Assignee: | Jeff Layton <jlayton> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | gansalmon, itamar, jonathan, jw2357, kernel-maint, madhu.chinakonda, sprabhu, steved, whit |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-10-08 16:54:27 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
John William
2013-07-15 16:31:44 UTC
It looks like this is related to other Fedora changes in the distribution. Adding IP=xx.xx.xx.xx to the mount command line seems to allow the mount to proceed normally. Is this still a problem with more recent kernels? If so, can you retry the mount command with the '-v' flag and post the output here? This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. I'm seeing what looks like the same thing on Fedora 20. [root@fedora mnt]# mount -t cifs //192.168.1.27/XYZ /mnt/tmp -o user=someuser -v Password for someuser@//192.168.1.27/XYZ: ******* mount.cifs kernel mount options: ip=192.168.1.27,unc=\\192.168.1.27\XYZ,user=someuser,pass=******** Unable to find suitable address. This is a mount that works fine the same way on CentOS and Ubuntu systems. Also, it works elsewhere giving the domain name rather than the IP, but here: root@fedora mnt]# mount -t cifs //ZYZ-S05.abc.local/XYZ /mnt/tmp -o user=someuser -v mount error: could not resolve address for XYZ-S05.abc.local: Unknown error which is a strange error since the address resolves fine: [root@fedora mnt]# dig XYZ-S05.abc.local ... ;; ANSWER SECTION: XYZ-S05.abc.local. 3600 IN A 192.168.1.27 ... This is kernel 3.13.9-200.fc20.x86_64. What, by the way, is a "suitable address" in this context? Please open a new bug, but before you do please try the 3.14.4 update in F20 updates stable. |