[Expired for nfs-utils (Ubuntu) because there has been no activity for
60 days.]
** Changed in: nfs-utils (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Steve,
I'm really sorry, that server has been took out from production a while
ago, and I completely forgotten about this.
last week we had some disk space issue in our multi-porpouse virtual
machine manager and I get rid of old unused VMs, the one with this issue
was one of them: it's gone.
mastro, were you ever able to run the requested tests after this server
was taken offline?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933575
Title:
NFS not being mounted at boot time - rpc.statd
Hi Steve,
the server is now being used with a very dirty workaround I've written:
crontab -e
@reboot /usr/bin/my-mount-script.sh
the script is really stupid, it just keep trying mount -a every 5 seconds until
it found a file .checked that is present in the root directory of the NFS
On Fri, Feb 17, 2012 at 09:09:13AM -, mastro wrote:
This is to say that I can't test on that server anymore. If you can wait
I'll be able to do tests after 22/02/2012 when this server will be taken
off-line.
Ok, that would be fine.
but I doubt that second try is performed by the
Accordingly to TeTeT on the freenode #ubuntu-server IRC channel this bug
is probably related to mountall
** Package changed: ubuntu = mountall (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected natty
** Description changed:
Version: Ubuntu SERVER 11.04
installed nfs-commons
added this to /etc/fstab:
192.168.88.252:/repo /mnt/repos nfs rw,hard,intr 0 0
but I also tried
192.168.88.252:/repo
so to debug the issue I added this to /etc/rc.local (before exit 0)
mount /mnt/repos /tmp/mounting.$$ 21
rebooted and I got this in that file:
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
Don't doubt that...
but NFS is not mounted and the problem is real..
Here the /var/log/boot.log
fsck from util-linux-ng 2.17.2
fsck from util-linux-ng 2.17.2
/dev/sda1: clean, 235/124496 files, 65983/248832 blocks
/dev/mapper/git-root: clean, 57793/474208 files, 334796/1895424 blocks
mount.nfs:
Not disputing that it's a real problem, just saying that rc.local
doesn't get us closer to understanding it :)
Apparently id doesn't resolve 192.168.88.252 (?)
This just means that mountall first tried to mount the share before the
network was fully up. This is perfectly normal; and as you can
10 matches
Mail list logo
