[opensuse-factory] NFSv4 broken?
Hi, I'm bumping into a NFSv4 bug that seems to be the same one as described in this thread: http://markmail.org/thread/lpgltrf5w7rsut7k#query:+page:1+mid:lpgltrf5w7rsut... However, I was running openSUSE 12.3 with the same kernel (from kernel.opensuse.org) so this seemed weird. After more googling and verifying that NFS3 worked fine, I found this: http://lists.opensuse.org/opensuse-bugs/2013-09/msg04062.html And indeed, adding the system on which NFS is running to /etc/hosts solves the problem. I know very little about networking so I'm happy it is working now - however, I can imagine others will bump into the same, upgrading their openSUSE 12.3 and discovering NFS4 won't work anymore in case they don't have the server in /etc/hosts or on their DNS. Should I file a new bug, or re-open https://bugzilla.novell.com/show_bug.cgi?id=842977 as this is on 'real' hardware and not on a VM... ? /J -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Montag, 28. Oktober 2013 schrieb Jos Poortvliet:
I'm bumping into a NFSv4 bug [...] After more googling and verifying that NFS3 worked fine, I found this: http://lists.opensuse.org/opensuse-bugs/2013-09/msg04062.html
And indeed, adding the system on which NFS is running to /etc/hosts solves the problem.
I know very little about networking so I'm happy it is working now - however, I can imagine others will bump into the same, upgrading their openSUSE 12.3 and discovering NFS4 won't work anymore in case they don't have the server in /etc/hosts or on their DNS.
Should I file a new bug, or re-open https://bugzilla.novell.com/show_bug.cgi?id=842977 as this is on 'real' hardware and not on a VM...
Now you probably know why I told you that you should point people to bugzilla instead of "first ask on the ML" [1] - asking on the ML means loosing time between discovery of the problem and getting it to the developer. *SCNR* To answer your question: Bug 842977 was closed by the reporter after he found a workaround. It never got any developer attention. In other words: forget about it - the only useful part is comment #1 (which was added by a different person, BTW). I'd say open a new bugreport (maybe with a reference to bug 842977 as a "I'm not alone" sign) - but please do it NOW ;-) OTOH, I wouldn't call reopening bug 842977 "wrong" - the only reason why I recommend a new bugreport is that bug 842977 contains too much noise. This sums up to: both ways work - the important thing is to do something[tm] in bugzilla. To speed this up a bit - Neil Brown, the bugowner of nfs-utils, should be a good assignee for your bugreport [2]. Oh, and you don't need to know anything about networking just because you want to report a bug on it ;-) Regards, Christian Boltz [1] for those who don't know what I'm talking about - this was while I reviewed the announcement for RC1 ;-) [2] If you can trick the bugzilla team to make the user lookup working for "external" people, I'll tell you the mail address directly next time *eg* Bonus points if you also force them to make the bugzilla API available again so that the "bugreporter" package/tool works for external people again. (Bugreport numbers for both fights on request.) -- Argh, ich wollte heute doch gar nicht mehr siggen! [Michael Hoffmann in dag°] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Christian Boltz -
Jos Poortvliet