I am using 14.04 and looks like the problem is still there. Only one nfs
share listed in df, however on mount (what is valid) 8 shares listed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/4483
Note sure if it's the same bug, but running 14.04.
# cat /etc/os-release
NAME="Ubuntu"
VERSION="14.04, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/";
SUPPORT_URL="http://help.ubuntu.com/";
BUG_REPORT_URL="http://bugs.laun
Hi All, It would seem that this bug is still popping up.
I noticed this today, running 13.04.
/proc/mounts is fine.
/etc/mtab is missing nfs mounts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bug
History repeating - 3 years later and I'm seeing exactly this problem in
a new 12.04 install! I've got a glusterFS volume that mounts via NFS -
it shows in /proc/mounts but not df or mount output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I still have this problem in hardy. I'm running the latest patches.
mount -a will mount all missing NFS mounts after I'm logged in. I have
a Precision Workstation 690, so the race condition spoken about before
may still be happening with faster systems.
--
NFS mounts on clients don't appear in `
This bug was fixed in the package sysvinit - 2.86.ds1-14.1ubuntu37
---
sysvinit (2.86.ds1-14.1ubuntu37) hardy; urgency=low
* debian/initscripts/etc/init.d/mtab.sh:
Explicitly add mtab entries for networked file systems; race condition
exists where mtab can get overwritten *a
Per request from Kees Cook, explicit steps to reproduce this problem
* Fresh install of Hardy (VM is fine)
* apt-get install nfs-common
* Have a remote NFS server elsewhere running, and exporting a mount
* Add that mount to your fresh install's /etc/fstab, perhaps something like:
192.168.1.3:/
I have updated this debdiff with one that solves this problem, as well
as Bug #45842. In this version, however, I create a lock file,
/var/run/waitnfs.sh.pid, and check for that, rather than using the ps
aux | grep ... construct.
See:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/45842
Typo in debdiff s/Launnchpad/Launchpad/
** Attachment added: "patch to mountnfs script"
http://launchpadlibrarian.net/12134777/44836.diff
--
NFS mounts on clients don't appear in `mount` or `df` output
https://bugs.launchpad.net/bugs/44836
You received this bug notification because you
Better yet, a debdiff against gutsy's initscripts, with changelog entry
and version incrementing.
** Attachment added: "44836.diff"
http://launchpadlibrarian.net/12126861/44836.diff
--
NFS mounts on clients don't appear in `mount` or `df` output
https://bugs.launchpad.net/bugs/44836
You recei
I could not reproduce this problem in Hardy as of 2008-02-20.
I did reproduce the problem on Gutsy on 2008-02-02, and solved it by the
code suggested in Comment 14.
I'm attaching a unified diff patch.
** Attachment added: "1.patch"
http://launchpadlibrarian.net/12122542/1.patch
--
NFS mount
I think I found another problem related to this bug.
If the missing nfs mount uses quota, the quota command will not know it at all.
If I want to know my quota limits on that nfs mount I have no way unless I
manually remount it.
I was wondering if there are other programs that would be affected b
This bug is still present in hardy as of 20080124. I've got a kerberized nfs3
mount in fstab:
thayerfs.thayer.dartmouth.edu:/vol/apps /thayerfs/apps nfs
vers=3,sec=krb5,nosuid
It is accessible after boot, but only shows up in /proc/mounts - not in
/etc/mtab or via the mount command.
Adding
7.10: I noticed the same issue Jeffery Bond noticed. This also happened
with 6.06, probably because the NFS mounts did not show in /etc/mtab
(even though they did in /proc/mounts). However, with the patch Georg
Wulff supplied the NFS mounts show up in /etc/mtab again, and slocate's
updatedb skips t
The patch to mountnfs worked for me on ubuntu 7.10, but this bug has
another nasty effect:
When updatedb/slocate is running, it will scan NFS mounts, even if the
PRUNEFS string contains "nfs" in the /etc/updatedb.conf file. The
PRUNEPATHS option does seem to work however. This is pretty bad since
This patch works for me on feisty. Haven't tested on gutsy yet.
--
NFS mounts on clients don't appear in `mount` or `df` output
https://bugs.launchpad.net/bugs/44836
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
I have the same problem on Gutsy Gibbon and the patch worked for me as
well.
--
NFS mounts on clients don't appear in `mount` or `df` output
https://bugs.launchpad.net/bugs/44836
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-
I have the same problem with The Gutsy Gibbon and the patch works wery
well for me, thanks.
--
NFS mounts on clients don't appear in `mount` or `df` output
https://bugs.launchpad.net/bugs/44836
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscribe
An alternate solution - instead of waiting a fixed time - is to modify
/etc/network/if-up.d/mountnfs to include a runlevel-check:
RUNLEVEL=`runlevel`
while [ "${RUNLEVEL}" = "unknown" ]; do
if ps aux | grep -q " sh /etc/rcS.d/S45waitnfs.sh start$"
@Scott:
since this bug is now attached to sysvinit and sysvinit has been replaced since
edgy: will this bug be fixed anytime or shouldn't this happen, when upstart ist
used instead of sysvinit?
thanks
Andreas
--
NFS mounts on clients don't appear in `mount` or `df` output
https://bugs.launchpa
I am seeing this problem in recently installed Feisty (final) amd64.
NFS mounts made during boot do not appear in "mount" or "df" commands
but the mounts have occurred and show up in /proc/mounts.
NFS mounts made from command-line after boot do appear in "mount" and
"df" command.
--
NFS mounts
since this bug is open a long time now: is there a chance that this will
be fixed?
i just tried kde with kde free disk applet which lets you only choose
"partitions" mounted into the system. with this bug present, network
shares can't be checked.
so after sysvinit will be replaced, will this bug
22 matches
Mail list logo
