[Expired for upstart (Ubuntu) because there has been no activity for 60
days.]
** Changed in: upstart (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/586022
Clint, thanks for the feedback. I've opened a new bug report at [1] and
subscribed you as you indicated.
Thanks,
Alex
[1]: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/765545
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
bwalex, its ok to try and fail at the mount, that shouldn't *break*
anything. If there's no route, there's no danger of a timeout or
anything, it will rapidly fail and move on. Rather than trying to
pinpoint the exact spot where the network is available, we should
instead strive to make these mount
Hi, same here with nfs4 mounts on a natty installed today.
Curiously, the nfs3 mounts are fine. Could that be related with rcp.idmapd,
which has to run before nfs4 can mount successfully ?
Yours,
Steffen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
So how is this bug "incomplete"? The issue is fairly obvious; dhclient
ISN'T being run before NFS mounts, as running it manually from the mount
recovery shell fixes the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Yes, I am aware that nobootwait is a different issue. My point is about bad
boot ordering, where nfs is tried before up'ing the network interfaces.
Note that it's just a plain wired dhcp setup without any auth, so it should
just work.
Regards,
Alex
On Apr 8, 2011 12:46 AM, "Clint Byrum" wrote:
>
Clint Byrum: Thanks for the explanation.
Could it be something as simple as network-interface.conf emits net-
device-up for loopback and in turn mountall-net.conf fires then fails
and then mountall (or plymouth??) enforces a boot wait?
--
You received this bug notification because you are a mem
bwalex: Are you saying that the boot is actually waiting for these
mounts to timeout with nobootwait? That would be a pretty serious
problem, and not related to this bug.
The error message is a result of the fact that mountall just tries to
mount *all* filesystems in fstab, similarly to 'mount -a'
I can't speak for Maverick but the lucid code comments in mountall-
net.conf states: "Send mountall the USR1 signal to inform it to try
network filesystems again." and it is told to do this on event "net-
device-up". Does that event always occur when the network is fully
configured (whether static
Sorry for the comment flood; but I forgot to mention that breaking to
manual mounting (by pressing M), starting dhclient manually and then
continuing the boot process is a workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Also note that this happens reliably on every boot, so a race is
unlikely. I also don't have /var as a separate mountpoint.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/586022
Title:
nfs mounts hap
Well, I got the same issue since about January on Maverick, now also on
Natty. 'nobootwait' doesn't change a thing, it still waits on the nfs
mounts
Regards,
Alex
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Barry, mountall shouldn't be mounting your nfs filesystem until after
mountall-net comes up. Can you try adding the option 'nobootwait' ?
If it does still fail to mount, it is most likely bug #525154 , which
causes mountall to race statd.
Marking Incomplete pending response from Barry.
** Change
Removing the upstream task, since this only refers to jobs provided by
Ubuntu
** Project changed: upstart => null
** Changed in: null
Status: New => Invalid
--
nfs mounts happen before network is up
https://bugs.launchpad.net/bugs/586022
You received this bug notification because you are
I had this issue on Lucid and had since reverted to noauto so I cannot
confirm that it still occurs today. I can't test this right now but you
might want to try this (assuming the Maverick file is similar): in
/etc/init/mountall-net.conf change "start on net-device-up" to "start on
started networ
** Also affects: upstart
Importance: Undecided
Status: New
--
nfs mounts happen before network is up
https://bugs.launchpad.net/bugs/586022
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
16 matches
Mail list logo
