Red Hat Bugzilla – Bug 360551
Unable to mount 2 nfs shares at the same time from the same server - revert to kernel 2.6.20 fixes it
Last modified: 2014-06-18 03:36:55 EDT
Description of problem:
Unable to mount both of two mount points from one server.
Can mount either one.
Can unmount one, then mount the other, and then can't mount the first.
First noticed with autofs mounted shares, after doing an update.
Tested with settings in /etc/fstab and mounting manually.
Tested with the following STOPed: ypbind, yppasswd, autofs
Version-Release number of selected component (if applicable):
- Fedora Core (18.104.22.168-61.fc6)
- Every time
Steps to Reproduce:
1. Two mount points from one server: /path/home, /path/tc
2. mount one (either one) - OK
3. mount other one - fails "busy or already mounted"
4. unmount the one that is mounted
5. now able to mount the other
Server is FC3, kernel 2.6.12-1.1381_FC3smp
1) Revert to older kernel on the client system:
- Fedora Core (2.6.20-1.2962.fc6)
2) enable "exclude=kernel kernel-devel" in yum.conf
- shoulda done that ages ago...
Either use the "nosharecache" mount option or mount both shares with the same
This suggestion is relevant as one was mounted read-only and the other read-write.
However, I am unable to find this mount option in any of the man pages I looked at:
nfs (5), mount (5), fstab (5) and their info equivalents
I leave it to you guys to decide whether to move this bug to a documentation target.
Found it in "man nfs" when I actually looked on the correct machine...
(This is a mass-update to all current FC6 kernel bugs in NEW state)
I'm reviewing this bug list as part of the kernel bug triage project, an attempt
to isolate current bugs in the Fedora kernel.
I am CC'ing myself to this bug, however this version of Fedora is no longer
Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.
Thanks for using Fedora!
I *think* that with newer kernels, we spawn a new superblock on the fly when
necessary. So mounting with "nosharecache" is no longer necessary. I'm going to
close this bug as CURRENTRELEASE. Please reopen it if you're still having this