I wanted to add "cron" to the list of things that have a race condition
with NIS on startup, as I don't think cron has been mentioned in any of
the other postings on this issue. If a NIS user has installed a crontab
on a NIS client, and NIS has not started by the time cron starts, the
result is th
Tim - yes I was still doing it over the loopback interface. Thanks for
that link, I guess that all kind of makes sense.
Part of my problem also stems from the change to autofs5 from autofs4.
This has a separate bug
(https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/517139) filed
against it.
Tim - thanks I have tried upgrading my virtual machine to the
2.6.32-25.43 kernel as you suggested. I now believe I experience the
same failure that you observed on bare metal using the maverick 2.6.35
kernel - see the attached dmesg log from my latest test. So it is
definitely an improvement of
FYI. Looking at David McBride's comments to this bug report,
particularly #30, and checking the current kernel source package for
Ubuntu 10.04 it appears that patch identified in
https://bugzilla.kernel.org/show_bug.cgi?id=16056 (comments 17&18) has
not been back ported to the 2.6.32 kernel. I ha
Tim:
I managed to get your dd testcase to trigger the issue on a VM running
Ubuntu 10.04, Kernel 2.6.32-24.42, 8 CPUs, 512MB RAM, 8GB HDD. I've
attached the dmesg output from that test.
I downloaded the latest daily snapshot of Maverick Ubuntu 10.10 (kernel
2.6.35-19.28) and installed it onto an
TimGardner - From your dmesg output it appears your bare metal test was
running kernel version 2.6.35, is that correct? Also the stack trace
looks noticeable different. Is there an easy way I can test that kernel
version on my 10.04 LTS setup (i.e. is there a package I can install on
Lucid Lynx)?
Hi Tim,
After your post I retried my test case (see comment #23 above), except
this time using KVM instead of VMWare Server. All details of the
virtual machine, i.e. 2xCPU/512MB RAM/8GB HDD are the same - it's just
using KVM instead of VMWare.
I can confirm that under KVM and a vanilla install o
I believe we have also been affected by this issue. I've managed to
recreate it using a single virtual machine running on VMWare server and
only using the loopback interface.
First I created a 64-bit VM using VMWare Server with 2 CPUs, 512MB RAM
and 8GB disk. Into that I performed a fresh instal
