*** This bug is a duplicate of bug 164231 ***
https://bugs.launchpad.net/bugs/164231
In 164231 there is a nfs.ko available but since then there hasn't been a
linux-image released - at least I didn't get one via adept.
--
Kernel Oops with nfs4 mount
https://bugs.launchpad.net/bugs/148600
*** This bug is a duplicate of bug 164231 ***
https://bugs.launchpad.net/bugs/164231
AZ wrote:
*** This bug is a duplicate of bug 164231 ***
https://bugs.launchpad.net/bugs/164231
In 164231 there is a nfs.ko available but since then there hasn't been a
linux-image released - at
*** This bug is a duplicate of bug 164231 ***
https://bugs.launchpad.net/bugs/164231
--
Kernel Oops with nfs4 mount
https://bugs.launchpad.net/bugs/148600
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
*** This bug is a duplicate of bug 164231 ***
https://bugs.launchpad.net/bugs/164231
Has a corrected package with this patch been deployed yet?
Thanks,
Jared
--
Kernel Oops with nfs4 mount
https://bugs.launchpad.net/bugs/148600
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 164231 ***
https://bugs.launchpad.net/bugs/164231
** This bug has been marked a duplicate of bug 164231
NFS regression causes subsequent mounts from same superblock to silently use
previous mount options
--
Kernel Oops with nfs4 mount
Hi,
I'm running a machine that mounts nfs4 over a openvpn tunnel automatically on
startup.
I am running gutsy I just updated to the 2.6.22-14 kernel, there was no problem
before.
Now the machine crashes each time I try to mount my nfs4 share.
What makes this bug even worse is that after the
I experience the same problem described above by AZ with the newest Gutsy
kernel (2.6.22-14.47, 18 dec 2007)
My setup (Dell Inspiron Desktop 531s) has been stable since I've upgraded from
Feisty last month.
I mount three nfs v4 shares from a Fedora 7 server (from my /etc/fstab), and
the kernel
Oops - forgot to repost to this bug when I found out what's going on.
Two bugs that gave me kerberized nfs problems have been fixed upstream.
To my usterstanding; one was kerberos attempting to negotiate an unsupported
enctype, which triggered a second kernel bug causing the kernel oops.
The
Thanks James.
However, I must say that I don't use kerberos with NFS4, so maybe the
problem lies elsewhere.
--
Kernel Oops with nfs4 mount
https://bugs.launchpad.net/bugs/148600
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Claude and AZ,
The problem you are experiencing is in fact (embarrassingly) caused by
my patch at https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/164231 which was included in the 2.6.22-14.47 kernel
as part of a security update. This problem is unrelated to the OOPS that
was
** Tags added: kernel-oops
--
Kernel Oops with nfs4 mount
https://bugs.launchpad.net/bugs/148600
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@lists.ubuntu.com
at least you guys get as far as getting a kernel oops :) on my gutsy box
i can't even succesfully mount my nfs shares served by a debian etch
server, i get a permission denied error, see this post here:
http://ubuntuforums.org/showthread.php?t=570320
works nicely on feisty though, i fear there's
same result with nfs3 and sec=krb5. mount worsk, but any access to the mount
crashes the caller with a similar call trace to above.
I also replicated the nfs4 crash.
In nfs3 the keytab is optional, and the I can get immediate segfaults without
the keytab in place.
My log output always seems to
13 matches
Mail list logo
