Hi Christian,
thanks for the suggestion, but we did not use names for NFS mounts but IPs (see
fstab in #10).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1118447
Title:
Race condition
Maybe it doesn't help much here. It just *could* be that it doesn't have to do
anything with the network being up, but with DNS resolution?
I have had the problem on one computer (don't know why), and spotted the
following line in /var/log/syslog:
mount[859]: mount.nfs: Failed to resolve ser
Hey,
here in our institute we use VMware ESXi to deploy Ubuntu 14.04 machines
running:
Linux hostname 3.13.0-98-generic
#145-Ubuntu SMP Sat Oct 8 20:13:07 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
And we experiencing the same bug with the NFS race condition. Is there
already a bugfix after 2 years
I'm right now approx 300 kms away from my server and I notice, that the
machine fails to boot.
Symptoms are:
Open ports on the server:
Not shown: 997 closed ports
PORTSTATE SERVICE
111/tcp open rpcbind
139/tcp open netbios-ssn
445/tcp open microsoft-ds
MAC Address: 50:E5:49:92:FB:3F (Giga-
On Wed, Jan 08, 2014 at 06:47:03PM -, Christopher M. Penalver wrote:
> Steve Langasek, thank you for your comment. While it is always appreciated
> when a developer steps in and advises to a bug report, a portion of your
> comments don't make sense (which I'm happy to take off report, but they
On Sat, Jan 04, 2014 at 07:28:12AM -, Andrew Radke wrote:
> In the past we have also been asked to update our kernels and at no
> stage has this improved the situation. Is there anything to indicate
> that it is likely to help on this occasion or that it is a kernel bug
> and not a problem some
** Tags added: bios-outdated-1903
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1118447
Title:
Race condition with network and NFS mounts causes boottime hang
Status in “linux” package
Steve Langasek, thank you for your comment. While it is always appreciated when
a developer steps in and advises to a bug report, a portion of your comments
don't make sense (which I'm happy to take off report, but they are relevant
here). Regarding your comments:
>"This bug very clearly has no
This bug very clearly has nothing at all to do with the BIOS.
Christopher, it is inappropriate to ask bug submitters to test with a
new BIOS for bugs like this - the BIOS is entirely unrelated to the
network filesystem layer, and if upgrading the BIOS did have any effect,
it would be *irrelevant* t
Christopher, thank you for your comment on the outdated BIOS version. I
completely see your point about good quality of bug reports.
It may be some time until I can update our BIOSes, however. These are LTSP
servers powering a whole school with 700 every-day users, it's elementary they
are stabl
Unfortunately I'm not going to be able to test as requested in the short
term as the systems involved are in production. I will see if I can
replicate it on some virtual machines but again it could be a while
until this is possible.
While I also understand the preference for up to date BIOS it sho
Andrew Radke, thank you for your comments. Regarding them
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1118447/comments/21 :
>"I can confirm this bug on different hardware with completely up to date BIOS
>and firmware. The race condition we are seeing is being reported from varied
>sourc
A cleaner way of mounting the nfs shares than Josep provided is
something like what I have below. It looks for whether the nfs server
responds to a ping rather than the default route and will retry 3 times
with a 3 second timeout each time. It also checks all nfs mount points
listed in /etc/fstab w
I can confirm this bug on different hardware with completely up to date
BIOS and firmware.
The race condition we are seeing is being reported from varied sources
on different hardware over a significant period of time so I think it is
very unlikely to be effected by BIOS of firmware versions. I be
** Tags removed: bios-outdated-1903
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1118447
Title:
Race condition with network and NFS mounts causes boottime hang
Status in “linux” packa
Rüdiger Kupper, as per your
https://launchpadlibrarian.net/130634701/BootDmesg.txt :
[0.00] Your BIOS doesn't leave a aperture memory hole
[0.00] Please enable the IOMMU option in the BIOS setup
...
13.747117] EDAC amd64: DRAM ECC disabled.
[ 13.747128] EDAC amd64: ECC disable
I found what's going on, it looks to me like there is another race
condition between upstart and systemd scripts, sometimes rc.local gets
to mount some of my NFS shares but other times it doesn't. The first
thing I tried was doing a loop until ifconfig was showing a valid
address but it didn't work
The workaround of mounting the NFS shares through rc.local doesn't work
for me, sometimes it mounts them and sometimes not. Could it get
executed at the end of systemd scripts but not at the end of upstart
jobs?
--
You received this bug notification because you are a member of Kernel
Packages, wh
This bug has been around for years and we have worked around it by
mounting NFS from rc.local. It's not pretty, but it gets pretty old to
reboot your system and find it hanging. For some reason the NFS mounts
won't wait until networking has completed (i.e. bringing up the
interface).
I doubt it is
Hey. I seem to experience this bug as well. It definitely feels like a
race condition somewhere. I have to reboot my machine 2-5 times each
morning to finally get it to boot. I don't have any issues mounting
stuff after bootup is done, it certainly feels like a bug around
upstart/mountall to me. Th
** Description changed:
I seem to experience a race condition during boot of my ubuntu 12.04 server:
In approx. one of seven boots, the server hangs during bootup.
This is what I see on the screen:
After the line
- * Starting configure network device
+ * Starting configure network d
21 matches
Mail list logo
