http://bugzilla.novell.com/show_bug.cgi?id=556448 http://bugzilla.novell.com/show_bug.cgi?id=556448#c3 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |nfbrown@novell.com Resolution| |INVALID --- Comment #3 from Neil Brown <nfbrown@novell.com> 2009-11-22 22:39:19 UTC --- I was actually after /proc/mounts on the server - the same machine as holds /etc/exports, but it probably doesn't matter. So they question is "How did you end up with every line containing fsid=0?". I presume that when you configure NFS export with yast it might put fsid=0 on one of the lines as that makes it the root export for NFSv4, but the other lines don't need fsid= at all. So having multiple lines with "fsid=0" is definitely a wrong configuration. It is conceivable that 11.1 handled this differently to 11.2, and allowed it to work even though it shouldn't have done. I suggest that you simply remove all the "fsid=" entries unless you want to export one of those directories via NFSv4, in which case put "fsid=0" just for that entry. If you are certain that you didn't put all the "fsid=0" in there, then I can only imagine that YaST did it. In that case I recommend you re-open this bug as a bug against Yast / Installation. for now I'll close it as 'invalid' as NFS is doing the right thing giving the content of the configutation file, and nfs-utils never changes that configuration file. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.