We use initrd.img-2.6.24-19-openvz with bunch of Linux clients without any
problems.
Recently I tried to add Mac OS X client and immediately noticed that the
nfs-kernel-server on Linux started locking up for several seconds (thus
stalling NFS access for every other client) every minute with foll
Hi!
We're experiencing the bug on hardy here, too:
- snip -
Sep 3 11:22:57 recovery1 kernel: [68409.731835] rpcbind: server
s03.hallopizza.org not responding, timed out
Sep 3 11:22:57 recovery1 kernel: [68409.731876] lockd: server
s03.hallopizza.org not responding, timed out
Sep 3 11:22:57 r
(Storm)
I was using the nolock option since then - that means work with locking
disabled,
wich - of course - worked.
On 10.02. I enabled locking again to give it a try. No problems since then.
Kernels are 2.6.24-23-generic on both client and server
nfs-kernel-server and nfs-common are 1:1.1.2-2ub
I have exactly the same problem on a Hardy server (Should I open a new bug
report ?):
* linux-image-server 2.6.24.23.25
* nfs-kernel-server 1:1.1.2-2ubuntu2.2
* nfs-common 1:1.1.2-2ubuntu2.2
If I reboot the server, it works for only a few minutes.
--
NFS server: lockd: server not respo
I tried the generic kernel (as opposed to server). Worked for a couple of days,
then same again.
Until about 4 weeks ago, the problem appeared sporadically, then almost every
day - without
any change to the server (no automatic updates). It might depend on
configuratin or certain
packages on t
Same here: do not agree with Eckart: we use the hardy kernel on an
otherwise Gutsy installation and the problem stays away.
When booting the Gutsy kernel, it promptly pops up again (within a day).
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received thi
Can't agree with you there, Eckart. I upgraded to Hardy and all my
problems with NFS disappeared.
[EMAIL PROTECTED]:~$ uname -a
Linux kirby 2.6.24-19-generic #1 SMP Wed Aug 20 22:56:21 UTC 2008 i686 GNU/Linux
...and hasn't hung once in months. Used to hang at least once a day
under Gibbon.
--
Upgrading to hardy won't help, still the same;
client:
2.6.24-19-generic #1 SMP Wed Aug 20 22:56:21 UTC 2008 i686 GNU/Linux
says:
Oct 7 10:54:15 lagaffe kernel: [ 3099.897267] lockd: server tide not
responding, still trying
Oct 7 10:54:16 lagaffe kernel: [ 3101.624752] lockd: server tide not
I've come to the same conclusion as Vincent in
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/181996/comments/35 : the 2.6.22-15 kernel seems not
to have those patches applied ... any chance it will in the near future
?
I've looked at the sources in linux-source-2.6.22_2.6.22-
After getting the same problem last week ("lockd: server ... not
responding, timed out" on client; unkillable lockd on server) I had a
look at the source of the linux-image-2.6.22-15-generic package that
we're using. To my surprise, I couldn't confirm that the patches
mentioned in https://bugs.laun
Released in 2.6.22-14.53
** Changed in: linux-source-2.6.22 (Ubuntu Gutsy)
Assignee: Tim Gardner (timg-tpi) => (unassigned)
Status: Fix Committed => Fix Released
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification beca
Released in 2.6.22-14.53
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Fix Committed => Fix Released
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Any update on this? Has it been released yet??
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Triaged => Fix Committed
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
There are a series of NFS patches pending on the SRU process. Any day
now...
** Changed in: linux-source-2.6.22 (Ubuntu Gutsy)
Assignee: Colin King (colin-king) => Tim Gardner (timg-tpi)
Status: Triaged => Fix Committed
--
NFS server: lockd: server not responding
https://bugs.launchp
** Changed in: linux-source-2.6.22 (Ubuntu Gutsy)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => Colin King
(colin-king)
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which
Well.. since the problem only is present on a gutsy kernel.. it is quite
obvious that you can reproduce on the hardy kernel. The patch above is
from the patch-stream between gutsy and hardy.
Jesper
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received th
I am now running Hardy with kernel 2.6.24-16-server and have not seen
this problem for 8 days now. Is it the case that the kernel was patched
and this is a patched kernel? If it is I am very happy and thankful to
those who did the debugging and the patching. If not, then has the
problem been cir
I'd just like to add that I have this problem too and thank all those
who have provided debugging info. This bug has been crippling my system
for some time, and confusing me greatly.
I would like to tentatively ask if there is any further progress with
adding the patch into a release update? I sha
Hi Jesper,
Thanks so much for testing and the feedback. I've reopened the Gutsy
nomination and have reassigned to the kernel team.
For anyone wanting more information about the Stable Release Policy also
refer to: https://wiki.ubuntu.com/StableReleaseUpdates .
Thanks again for the testing and
Changing to Confirmed.. as Described by Leann Ogasawara when the
patches are confirmed to work on a gutsy system.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Won't Fix => Confirmed
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received thi
SRU is a StableReleaseUpdate .. thats described in the links above. The
process to get fixes pushed to a "stable release".
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
What's an SRU? I'd love to know more about the process for getting
fixes into Ubuntu. Please explain!
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Leann Ogasawara: Should we provide more to get a SRU for this bug in
gutsy?
Jesper
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
I can confirm that the above 2 patches solves the problem.
The problem is really grave.. making the NFS-server in gutsy rarely
usable. The locking problem occoured about every second day here.. I
applied the patch over a week ago and hasn't seen the problem since.
Jesper
--
NFS server: lockd:
>From the comments here it seems this is resolved for the Hardy kernel so
marking "Fix Released" against the Hardy 'linux' kernel source package.
The kernel stable release update policy if fairly strict:
https://wiki.ubuntu.com/KernelUpdates . If someone could confirm the
two patches mentioned in
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
I've been seeing it for a while now, but only when I run an application
on the nfs client that intensively uses file locking.
The only fix is to reboot the server.
When it occurs, the following hangs on the client(in the flock):
time flock ~/junk echo ok; rm ~/junk
[note: flock is in the
No,
The failure is very regular. It happens whenever the garbage
collection is performed as a result of a lock request.
J.
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
B
I would have thought that the Ubuntu Kernel Team would have looked at
this problem -- especially as there is a putative fix. However, it
seems it may not yet have even been triaged by them. The problem, at
least as I see it, is that there is no regularity to the failure. This
must make it hard t
Yeah,
I know how to fix the problem, but I have no idea how to get a patch
into Gutsy. Any ideas who I would contact?
J.
Russel Winder wrote:
> I am running fully up to date Gutsy server and am getting what I think
> is the same problem as is reported here. After an indetermin
I am running fully up to date Gutsy server and am getting what I think
is the same problem as is reported here. After an indeterminate amount
of time and/or activity, the [lockd] process on the server goes from S
state to D state and all queries from clients result in messages such
as:
Feb 28 07:
Second part is easy. Fix yaird as above, download the .deb files, and
"dpkg install" them both. I had no hassles with that.
J. Bruce Fields suggested the following two patches, but I didn't use
those.
http://git.linux-nfs.org/?p=trondmy/nfs-2.6.git;a=commitdiff;h=255129d1e9ca0ed3d69d5517fae3e03
Any progress on a patch? I'm running into the same problem. If not,
would you mind providing a bit more info describing the necessary steps
to get the 2.6.24 kernel installed on a Gutsy server?
Thanks...
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You rec
This is fixed in the 2.6.24 kernel series.
I installed:
linux-image-2.6.24-5-generic_2.6.24-5.8_i386.deb
linux-ubuntu-modules-2.6.24-5-generic_2.6.24-5.9_i386.deb
from:
http://packages.ubuntu.com/hardy/base/
(After making the changes to yaird required to install it)
vi /usr/lib/yaird/perl/Inpu
I went with the nlm_gc_hosts_if_needed () approach. Stable so far.
Debug shows completion of GC.
[ 6879.405447] lockd: request from 192.168.1.211, port=729
[ 6879.405454] lockd: LOCK called
[ 6879.405458] lockd: nlm_lookup_host(192.168.1.211, p=6, v=4, my role=server,
name=ditko)
[ 6879
Hmm... one quick-fix approach would seem to be to pass LOCK_RECURSIVE to
mutex_init.
On that note, it's not clear to me yet why we're even using mutexes
here. Isn't there only a single lockd process? And in that case, all
these mutexes are private, no? Or is it possible to start two lockd's
for
OK, let's follow the request and see what is performing a file mutex
lock.
[ 5845.725268] lockd: request from 192.168.1.210, port=860
This is from the main lockd kernel thread function.
static void lockd (...) in svc.c. It invokes svc_process().
[ 5845.725272] lockd: LOCK called
Via some xdr mag
Right, this appears (unsurprisingly) to be a mutex contention issue, on
the file-specific mutex.
See the attached trace: server-kirby-v3.dmsg
Key parts are:
[ 5845.725268] lockd: request from 192.168.1.210, port=860
[ 5845.725272] lockd: LOCK called
[ 5845.725274] lockd: nlm_lookup_host
It's getting lost in nlm_inspect_file ().
[ 693.679373] lockd: mutex acquired, checking 128 file hash entries
[ 693.679375] lockd: got entry in list 58
[ 693.679376] lockd: inspecting file
dprintk("lockd: mutex acquired, checking %d file hash entries\n",
FILE_NRHASH);
for (i =
OK, I added more debug to /usr/src/linux/fs/lockd/host.c and installed a
new lockd module. Seems like it's getting lost somewhere in
nlmsvc_mark_resources(). I'll keep digging.
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification
** Attachment added: "Output from client's dmesg."
http://launchpadlibrarian.net/11447299/client-romita.dmsg
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Attachment added: "Output from server's dmsg."
http://launchpadlibrarian.net/11447297/server-kirby.dmsg
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact fo
OK, I turned on debug with:
echo "65535" > /proc/sys/sunrpc/nlm_debug
There seems to be a problem when lockd enters garbage collection.
Here's the last of the debug seen from lockd on the server side.
[ 2277.091005] lockd: request from 192.168.1.210, port=864
[ 2277.091018] lockd: LOCK
Feel free to contact me if I can offer help debugging this.
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
I can confirm the same on a brand new Gutsy install with 2.6.22-14.
Within 24 hours usually, this will occur. When it happens, Skype,
Amarok and other apps will hang first, but eventually all apps will
hang. Client reboot does nothing. nfs-kernel-server doesn't help (it
doesn't clear the broken
Since I have downgraded kernel to 2.6.20 (a week ago), the error does not show
up anymore.
It appears to be a bug in kernel, 'cause I used to find a similar issue
reported for Fedora Core 7, running 2.6.22.
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You r
** Description changed:
- Running NFS server on Ubuntu Server 7.10 on x86 machine (Pentium-3, 1G RAM).
+ Running NFS server on Ubuntu Server 7.10 x86 (Pentium-3, 1G RAM).
- linux-image-2.6.22-14-server (2.6.22-14.47)
- nfs-kernel-server (1:1.1.1~git-20070709-3ubuntu1)
- nfs-common (1:1.1.1~g
48 matches
Mail list logo
