*** This bug is a duplicate of bug 470776 ***
https://bugs.launchpad.net/bugs/470776
In my case, mountall mounted my nfsshares after establishing a network
connection in karmic. Now in lucid, mountall does not mount any
nfsshare. The shares are not needed at boottime.
/etc/fstab:
192.168.0.20
*** This bug is a duplicate of bug 470776 ***
https://bugs.launchpad.net/bugs/470776
The difference between static IP and DHCP is all down to timing, which
would strongly suggest you're all experiencing the bug described in
#470776 - that mountall gets told the network is up, but isn't ready t
I can't judge the importance of this bug for others, but should it not
be mentioned in ubuntu-release-notes?
--
karmic: nfs shares are not mounted at boot
https://bugs.launchpad.net/bugs/461133
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
So in a nut shell you can't have a DHCP server on karmic that mounts NFS
filesystems at startup.
This is biting me on three boxes. I could set fixed IP addresses in my
DHCP server for the nodes in questions but this is just a workaround.
--
karmic: nfs shares are not mounted at boot
https://bu
I just tried sending the SIGUSR1 when mountall was running, and then it
works:
r...@envy:~# mountall --debug --verbose
mount / [15647] exited normally
mount /proc [15648] exited normally
mount /sys [15649] exited normally
mount /sys/fs/fuse/connections [15650] exited normally
mount /sys/kernel/deb
I seem to have exactly the same problems. I first upgraded a server from
jaunty to karmic, and this morning decided to give the machine a clean
install (karmic server 32bits) - with only openssh, nfs-common and
portmap packages installed.
I have only put the following line in /etc/fstab:
172.16.1
This bug report is marked for expiration. What information is missing?
--
karmic: nfs shares are not mounted at boot
https://bugs.launchpad.net/bugs/461133
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
I use the setup described here:
http://www.staldal.nu/tech/2009/11/15/linux-with-mounted-read-only-2-0/
--
karmic: nfs shares are not mounted at boot
https://bugs.launchpad.net/bugs/461133
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also get this problem. However, it doesn't even work when setting to "noauto"
in /etc/fstab and then try to mount it from /etc/rc.local, I get this error
message:
mount.nfs: DNS resolution failed for myserver: Name or service not known
But it does work to mount it from /etc/gdm/PostLogin/Defau
... and my mythtv backend doesn't start automatically anymore.
DHCP => nfs mounts via fstab and mythtv backend works
static IP => nfs shares need to be mounted by hand and mythtv-backend has to be
started by hand
--
karmic: nfs shares are not mounted at boot
https://bugs.launchpad.net/bugs/4611
I ran into the same problem as I switched from DHCP to a static IP.
--
karmic: nfs shares are not mounted at boot
https://bugs.launchpad.net/bugs/461133
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Can confirm that setting the NFS clients to dhcp does solve this issue
for me as well.
--
karmic: nfs shares are not mounted at boot
https://bugs.launchpad.net/bugs/461133
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
The issue of the static ip address is bug #446031, so I'm using dhcp on the
servers now. I was also using a separate /boot that added to the confusion.
(bug #462961, now fixed.)
Setting the NFS clients to dhcp did solve this issue! I rechecked by setting a
static ip again.
I will use this as a
I wonder whether this and bug #470776 are the same, ie. SIGUSR1 is being
received but the device isn't ready due to underlying mountpoints - and
then when the underlying mountpoints are ready, there's no more SIGUSR1
--
karmic: nfs shares are not mounted at boot
https://bugs.launchpad.net/bugs/46
Scott, I did sent SIGUSR1 (using htop). Maybe I'm doing it wrong though.
Meanwhile, I'm seeing this problem all networks under my care and I'm using
Albrecht's workaround for them.
(I have now seen this problem on 5 different machines in 3 different networks.)
The big problem is: Sometimes /home
We also get this, if we wait for a while the system boots correctly with
the nfs mounts mounted, but it does take quite a while to do so.
--
karmic: nfs shares are not mounted at boot
https://bugs.launchpad.net/bugs/461133
You received this bug notification because you are a member of Ubuntu
Bugs
I have the same issue, nfs shares not mounted at boot.
Listing the /proc/filesystems does not show the nfs filesystem listed,
which might be the reason the nfs shares are not mounted?
After running sudo mount -a -t nfs the shares are mounted. And running
cat /proc/filesystems does now have nfs an
I think what's going on here is that the first mountall isn't omitting
network filesystems like it should be. I could be wrong - I don't know
how to monitor upstart in a way to debug which of the various mountalls
are being run when it hangs.
However if the network and portmap aren't up then this
The log doesn't show SIGUSR1 being received
** Changed in: mountall (Ubuntu)
Status: New => Incomplete
** Changed in: mountall (Ubuntu)
Importance: Undecided => Medium
--
karmic: nfs shares are not mounted at boot
https://bugs.launchpad.net/bugs/461133
You received this bug notificati
End of the log shows:
try_mount: /media/xyimages waiting for /media/xydata
One or more of the mounts listed in /etc/fstab cannot yet be mounted:
(ESC for recovery shell)
/media/archive: waiting for back:/archive
/media/backup: waiting for coolio:/backup
/home/roger/sh_home: waiting for coolio:/hom
Output of: sudo mountall --debug > mountall.log 2>&1
(mountpoints are in /media instead of /srv, as described in first /etc/fstab)
** Attachment added: "mountall --debug > mountall.log 2>&1"
http://launchpadlibrarian.net/34416599/mountall.log
--
karmic: nfs shares are not mounted at boot
http
Please supply output of "sudo mountall --debug" and send it SIGUSR1
** Package changed: mountall (Ubuntu) => nfs-utils (Ubuntu)
--
karmic: nfs shares are not mounted at boot
https://bugs.launchpad.net/bugs/461133
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Attachment added: "/etc/fstab of updated kubuntu"
http://launchpadlibrarian.net/34414174/fstab
--
karmic: nfs shares are not mounted at boot
https://bugs.launchpad.net/bugs/461133
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
23 matches
Mail list logo
