Bug#576405: linux-image-2.6.26: Deadlock during combined NFS3/NFS4 use
On 12/09/11 10:07, Jonathan Nieder wrote: Hi Anton, Anton Ivanov wrote: When an export is exported and mounted via autofs using BOTH NFSv3 and NFSv4 the NFSv4 one deadlocks. We ought to have put this in the hands of upstream about a year ago. Better late than never, so I will echo Ben: Ben Hutchings wrote: OK. Next, can you test whether the kernel version in unstable (linux-image-2.6.32-4-* version 2.6.32-10) or testing (linux-image-2.6.32-3-* version 2.6.32-9) also has this bug? I cannot reproduce it on 2.6.32 with autofs5 (squeeze). You can close it. In general 2.6.26/autofs4 (lenny) was quite fragile with automounted nfs4. nfs4 itself was OK, autofs itself was OK, together the combination was rather explosive. Squeeze fixed all of that. I have yet to observe a single problem with nfs4 + autofs on my squeeze systems. Can you reproduce this with a recent (3.x) kernel? (If so, upstream might care, and if not, we can try to find the fix and backport it.) Thanks for an interesting report, and sorry to have left it hanging. Jonathan -- Humans are allergic to change. They love to say, We've always done it this way. I try to fight that. That's why I have a clock on my wall that runs counter-clockwise. -- R.A. Grace Hopper A. R. Ivanov E-mail: anton.iva...@kot-begemot.co.uk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576405: linux-image-2.6.26: Deadlock during combined NFS3/NFS4 use
Hi Anton, Anton Ivanov wrote: When an export is exported and mounted via autofs using BOTH NFSv3 and NFSv4 the NFSv4 one deadlocks. We ought to have put this in the hands of upstream about a year ago. Better late than never, so I will echo Ben: Ben Hutchings wrote: OK. Next, can you test whether the kernel version in unstable (linux-image-2.6.32-4-* version 2.6.32-10) or testing (linux-image-2.6.32-3-* version 2.6.32-9) also has this bug? Can you reproduce this with a recent (3.x) kernel? (If so, upstream might care, and if not, we can try to find the fix and backport it.) Thanks for an interesting report, and sorry to have left it hanging. Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576405: linux-image-2.6.26: Deadlock during combined NFS3/NFS4 use
On 12/09/11 10:07, Jonathan Nieder wrote: Hi Anton, Anton Ivanov wrote: When an export is exported and mounted via autofs using BOTH NFSv3 and NFSv4 the NFSv4 one deadlocks. We ought to have put this in the hands of upstream about a year ago. Better late than never, so I will echo Ben: Ben Hutchings wrote: OK. Next, can you test whether the kernel version in unstable (linux-image-2.6.32-4-* version 2.6.32-10) or testing (linux-image-2.6.32-3-* version 2.6.32-9) also has this bug? Can you reproduce this with a recent (3.x) kernel? (If so, upstream might care, and if not, we can try to find the fix and backport it.) I will try to find some time to retest with current and 3.x this week. I do not recall seeing it on 2.6.32 lately. I have, however, changed back to v3 a lot of autofs entries so this is not indicative. Thanks for an interesting report, and sorry to have left it hanging. No worries. Jonathan -- Humans are allergic to change. They love to say, We've always done it this way. I try to fight that. That's why I have a clock on my wall that runs counter-clockwise. -- R.A. Grace Hopper A. R. Ivanov E-mail: anton.iva...@kot-begemot.co.uk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576405: linux-image-2.6.26: Deadlock during combined NFS3/NFS4 use
On Sun, 2010-04-04 at 21:20 +0100, Anton Ivanov wrote: On Sun, 2010-04-04 at 20:40 +0100, Ben Hutchings wrote: On Sun, 2010-04-04 at 09:44 +0100, Anton Ivanov wrote: Package: linux-image-2.6.26 Version: nfsfix.1 What does that version mean? Have you applied your own patches? Can you reproduce this with an official kernel package? That is a rather old official with only the NFS regression applied (the one I dug out a while back - bug 524199). It worked and I have not touched it since. That fix was applied in a stable update some time ago. You do not need to use your own patched kernel version, and if you continue with that version you will be missing security updates. That is just one machine on which I am observing it. I also see it on several other machines with: 1. Latest Official - 486, 686 [...] OK. Next, can you test whether the kernel version in unstable (linux-image-2.6.32-4-* version 2.6.32-10) or testing (linux-image-2.6.32-3-* version 2.6.32-9) also has this bug? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#576405: linux-image-2.6.26: Deadlock during combined NFS3/NFS4 use
Package: linux-image-2.6.26 Version: nfsfix.1 Severity: important When an export is exported and mounted via autofs using BOTH NFSv3 and NFSv4 the NFSv4 one deadlocks. Setup - transition from v3 to v4. System A is still perusing the old map: cat /etc/auto.local | grep iPodResolution iPodResolution -rsize=4096,wsize=4096,rw eden:/exports/md4/videoiPod System B is using the newever version of same map with a v4 mount: cat /var/yp/auto.local | grep iPodResolution iPodResolution -fstype=nfs4 eden:/md4/videoiPod If system B is writing to the mount and A is reading from it B starts getting I/O errors/BAD FDs. If B is running from disk lots of things fail. If B is running diskless - total lock up. Same setup with V3 only has been working flawlessly for 5+ years. Same setup with V4 only (when the v3 machines are off) seems to work OK as well. Fairly easy to reproduce. I am not sure at this point if autofs has any role in this and I will not be in a position to retest until 19th. Apologies. Tested with: stock debian, older version with just the nfs regression fix, stock recompiled with preempt, 686 and 486 versions. -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26 depends on: ii coreutils 6.10-6 The GNU core utilities ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy linux-image-2.6.26 recommends no packages. Versions of packages linux-image-2.6.26 suggests: ii fdutils 5.5-20060227-3 Linux floppy utilities pn ksymoops none (no description available) pn linux-doc-2.6.26 | linux- none (no description available) -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576405: linux-image-2.6.26: Deadlock during combined NFS3/NFS4 use
On Sun, 2010-04-04 at 09:44 +0100, Anton Ivanov wrote: Package: linux-image-2.6.26 Version: nfsfix.1 What does that version mean? Have you applied your own patches? Can you reproduce this with an official kernel package? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#576405: linux-image-2.6.26: Deadlock during combined NFS3/NFS4 use
On Sun, 2010-04-04 at 20:40 +0100, Ben Hutchings wrote: On Sun, 2010-04-04 at 09:44 +0100, Anton Ivanov wrote: Package: linux-image-2.6.26 Version: nfsfix.1 What does that version mean? Have you applied your own patches? Can you reproduce this with an official kernel package? That is a rather old official with only the NFS regression applied (the one I dug out a while back - bug 524199). It worked and I have not touched it since. That is just one machine on which I am observing it. I also see it on several other machines with: 1. Latest Official - 486, 686 2. Rebuilt with only preemption enabled 3. Official as released only with NFS regression applied (524199) I have not done a full matrix of all client/server options for these as there are quite a few possible combinations. I can reboot all of the machines in question into official and retest formally after I am back from holidays on the 19th. I would not expect to see anything particularly different though (even on the ones that do not run official the difference from official is marginal - a few option tweaks and/or official patches from debian-security applied by hand to older kernels). -- Understanding is a three-edged sword: your side, their side, and the truth. --Kosh Naranek A. R. Ivanov E-mail: anton.iva...@kot-begemot.co.uk WWW: http://www.kot-begemot.co.uk/ pub 1024D/DDE5E715 2002-03-03 Anton R. Ivanov ai...@sigsegv.cx Fingerprint: C824 CBD7 EE4B D7F8 5331 89D5 FCDA 572E DDE5 E715 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
