| Summary: | [RESOLVED] Mageia client won't connect to two NFS servers at the same time | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | William Kenney <wilcal.int> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | Normal | CC: | davidwhodgins, rwobben |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakx-net | CVE: | |
| Status comment: | |||
|
Description
William Kenney
2012-05-17 21:40:55 CEST
mounting with the drakxtools ? another gui ? or only with mount ? drakxtools then I go into /etc/fstab and manually change things. The fstab line looks like this: 192.168.1.2:/home/wilcal/databank /home/wilcal/shares/sherman nfs rsize=8192,wsize=8192,nosuid,soft 0 0 So if I started another NFS share on the LAN and added 192.168.1.4:/home/wilcal/databank /home/wilcal/shares/sherman nfs rsize=8192,wsize=8192,nosuid,soft 0 0 192.168.1.2 would mount 192.168.1.4 would not. The drakxtool saw both servers. If both comments are in /etc/fstab just commenting out one or the other will make the uncommented NFS server mount. The name "sherman" is the host name of the server. 192.168.1.2 is server sherman. 192.168.1.4 is a test box and printer server. FWIW it's hostname is "madison". I name all my boxes after American Presidents, including grant ( who was a drunk ). Here's my menu for setting up a NFS share:
MCC: Network Sharing -> Share drives and directories using NFS
install nfs-utils
MCC: Share drives and directories using NFS
Add -> Directory: /home/wilcal/databank
Access: *
User ID: No user UID mapping
Anonymous user ID: (blank)
Anonymous Group ID: (blank)
Advanced: all no
Feel free to comment.
If comment 2 is accurate, I'd expect both to be able to mount, but only the second to be visible, as they are both using the same directory for the mountpoint. CC:
(none) =>
davidwhodgins (In reply to comment #4) > If comment 2 is accurate, I'd expect both to be able to mount, > but only the second to be visible, as they are both using the > same directory for the mountpoint. Sorry in the test I did separate the two targets. They were: /home/wilcal/shares/sherman /home/wilcal/shares/truman Gimme some time on this one. I don't think this is gonna be a major problem. I more wanted to report this as a record in case someone else runs across it. I'll post more testing result as I go along. Thanks
Manuel Hiebel
2012-05-25 10:45:26 CEST
Component:
Installer =>
RPM Packages Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja Keywords:
(none) =>
NEEDINFO Still valid as a bug for 2. More testing on my part is needed. @William : Have you done the testing and is this bugs still valid ? Roelof CC:
(none) =>
r.wobben (In reply to comment #8) > @William : Have you done the testing and is this bugs still valid ? I'll give it some testing in the next days. I have re-run this test using two Mageia 2 NFS Servers and a single Mageia 3 Beta 1 Client. I was successful to mount the two NFS servers. The code in the Client /etc/fstab is as follows: 192.168.1.2:/home/wilcal/databank /mnt/sherman nfs rsize=8192,wsize=8192,nosuid,soft 0 0 192.168.1.5:/home/wilcal/databank /mnt/madison nfs rsize=8192,wsize=8192,nosuid,soft 0 0 My last testing I had the mount point(s) within user space. Do note that two significant NFS bugs remain. They are: https://bugs.mageia.org/show_bug.cgi?id=6541 systemd seems to have problems with NFS mounts and you still have to manually edit the /etc/fstab file replacing the server name with the IP. See above. I've changed the status of this bug to RESOLVED. Thanks Status:
NEW =>
RESOLVED |