** Changed in: linux
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/306016
Title:
nfs client broken since 2.6.28-2-generic upgrade
--
ubuntu-bugs mailing list
ubunt
First - Thanks for fixing this. Second I've found the work around for
the bug. If you install nfs-kernel-server you can mount/unmount nfs
shares without a problem. It seems whatever is missing from kernel
2.6.28-15 is in the nfs-kernel-server package.
Hope this helps someone trying to solve an
Sorry, posted on wrong bug.
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
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
https://list
Oh. I just noticed this --
nepomukservices[4039]: segfault at 8 ip 7fcbbf332cfe sp
7fffc7935b50 error 4 in libQtCore.so.4.5.0[7fcbbf2c9000+24]
And that does happen every boot, but I guess thats yet another bug to
follow up on with Jaunty..
Anyway, I have googled up on this nfs issue
I'm using the latest Intrepid packages of everything. NFS seems to work
great on everything but one box and one box only, still. Using the
"nolock" mount flag workaround appeared to fix it at first, but wound up
freezing up again after a while.
I had to go back to using 2.6.24-16-server on that on
On Thu, Mar 26, 2009 at 07:38:36PM -, mike503 wrote:
> This has been an issue for me for a long time using intrepid too.
You're the only one hitting this on Intrepid. Unless you're using a
Jaunty kernel on your Intrepid system. It's been fixed in Jaunty for
months. The only way you could b
This has been an issue for me for a long time using intrepid too.
I have not upgraded to jaunty yet.
Kernel versions on only *one* machine seem to not start nlockmgr.
broken machine:
[r...@lvs01 etc]# rpcinfo -p
program vers proto port
102 tcp111 portmapper
100024
This has been an issue for me for a long time using intrepid too.
I have not upgraded to jaunty yet.
Kernel versions on only *one* machine seem to not start nlockmgr.
broken machine:
[r...@lvs01 etc]# rpcinfo -p
program vers proto port
102 tcp111 portmapper
100024
This has been an issue for me for a long time using intrepid too.
I have not upgraded to jaunty yet.
Kernel versions on only *one* machine seem to not start nlockmgr.
broken machine:
[r...@lvs01 etc]# rpcinfo -p
program vers proto port
102 tcp111 portmapper
100024
Andy, that bug I reported is present in the released kernel. I have
initiated Bug 311732 for it.
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package linux - 2.6.28-4.5
---
linux (2.6.28-4.5) jaunty; urgency=low
[ Andy Whitcroft ]
* clean up module dependancy information on package removal/purge
- LP: #300773
[ Tim Gardner ]
* Update iscsitarget to 0.4.17
* Build in ext{234}
* Bu
worked wonderfully, thank you very much :D.
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
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.
Andy, I also booted the test kernel, and can report that all of:
mount -t nfs -o nolock noel-ubuntu.local:/ /tmp/nfsshare/
mount -t nfs noel-ubuntu.local:/ /tmp/nfsshare/
mount -t nfs4 -orsize=32768,wsize=32768 noel-ubuntu.local:/ /tmp/nfsshare/
work just fine. So that's all good news, and
I booted the test kernel and they fixed the problem for me. Thanks very
much!
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
I have built some test kernels with this config change applied. These
are based of the current jaunty kernel. If you could test these kernels
and report back here that would be great. These kernels are available
at the URL below:
http://people.ubuntu.com/~apw/lp306016/
--
nfs client broke
The new mode is still marked experimental (depending on
CONFIG_EXPERIMENTAL) so its not deemed ready for mainstream use. We
should have it disabled for the Jaunty cycle at least. It is likely
something to be considered for the K cycle.
--
nfs client broken since 2.6.28-2-generic upgrade
https:/
Thanks, Andy and Kees. Question: having read the discussion at the
upstream bug, I'll ask the obvious --: why is Jaunty using the "legacy
Linux portmapper daemon" instead of rpcbind?
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
You received this bug
The upstream maintainer indicate that this is a missmatch between our
kernel and userspace. Specificially we are using portmapper in
userspace but have the kernel side of rpcbind enabled. Spun a patch to
disable CONFIG_SUNRPC_REGISTER_V4 and submitted it. Building some test
kernels now.
--
nf
** Changed in: linux
Status: Confirmed => Invalid
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
** Changed in: nfs-utils (Ubuntu)
Status: Confirmed => Invalid
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andy Whitcroft (apw)
Status: Confirmed => In Progress
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I confirm both the bug and the "-o nolock" workaround on a "fresh"
Jaunty installation (as far as jaunty can be fresh installed...)
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
You received this bug notification because you are a member of Ubuntu
Bugs
I can concur: The volume I now see the problem is not NTFS either.
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
Peter,
Bug 308537 is solely about an install problem where both Thomas and I
encountered errors when simply installing nfs-common on Jaunty. I
agree with you that I don't see any reason why NTFS would have any
effect on NFS, and my volumes are either ext3 or xfs.
Thomas, what mount command(s) a
On Sat, Dec 20, 2008 at 04:16:55AM -, tdflanders wrote:
>
> Hi there,
>
> It works fine for me now. Can you try:
>
> root# apt-get install libntfs-3g-dev libntfs-3g31 libntfs-dev libntfs10
Are you confusing NFS with NTFS? They're completely different
things... If you aren't, then the NFS
see:
Bug #308537:
This report is public
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
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.co
Hi there,
It works fine for me now. Can you try:
root# apt-get install libntfs-3g-dev libntfs-3g31 libntfs-dev libntfs10
; apt-get build-dep libntfs-3g-dev libntfs-3g31 libntfs-dev libntfs10 ;
dpkg-reconfigure libntfs-3g-dev libntfs-3g31 libntfs-dev libntfs10 ;
apt-get install nfs-common ; apt-g
** Changed in: linux
Status: Unknown => Confirmed
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
** Bug watch added: Linux Kernel Bug Tracker #12256
http://bugzilla.kernel.org/show_bug.cgi?id=12256
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=12256
Importance: Unknown
Status: Unknown
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.la
2008/12/19 Kees Cook :
> Why is this certain to be an nfs-utils bug? There is no newer upstream
> version, and if "nolock" works, that seems like the kernel broke
> something to me.
>
that's a very good point ;). i think you're right too, tbh.
--
nfs client broken since 2.6.28-2-generic upgrade
Why is this certain to be an nfs-utils bug? There is no newer upstream
version, and if "nolock" works, that seems like the kernel broke
something to me.
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
nfs clien
Hi,
I've been seeing this in Ubuntu, but not Debian (I triple-boot between
Debian and Ubuntu almost evenly, and the unnamed obsolete OS rarely). In
Debian, they mount instantly with the same exact mount options in fstab,
whereas in Jaunty they don't, and I see the same errors as the original
repor
Invalidating for linux, already marked for nfs-utils
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Thanks for marking it as a duplicate. As seen in the other thread,
which does have some additional info, this can be circumvented by using
the nolock option, but is still a serious bug.
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
You received this b
This does look the as same bug 306343 I reported. I didn't see this one
because I was only searching in linux, not nfs-common.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
You received th
** Changed in: nfs-utils (Ubuntu)
Importance: Undecided => High
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Confirming - this is a serious bug.
** Changed in: nfs-utils (Ubuntu)
Status: New => Confirmed
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
37 matches
Mail list logo
