startproc /usr/sbin/cfsd || return=$rc_failed mount -o port=3049,intr localhost:/.cfsfs /crypt || return=$rc_failed After I accidently changed the port to 2049 this mount request worked, but /crypt is mounted with permissions 000, so this seems not to be the correct way. I think it has something to do with the Portmapper : When mounting
Maybe the stock kernel hasn't got support for NFS volumes?
# cd /usr/src/linux-2.2.xx(.SuSE) # vi .config and search for CONFIG_ROOT_NFS Why should this option be important? I never needed this option, and I don't intend to mount / over nfs. Maybe that's the problem. You can also try looking a few lines below in .config, at the Partition Types.
Have you tried inserting a '-t NFS' in the mount command? yes, and it makes no difference for me...and it neither works with
I got the same problems (and a report of a friend who had no problems at all with 6.4 and CFS...strange) this is syslogged : nfs: RPC call returned error 111 RPC: task of released request still queued! RPC: (task is on xprt_pending) nfs_read_super: get root fattr failed the Kernel NFSserver nor the userspace NFSserver. bye Roland -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Roland Pabel wrote:
I got the same problems (and a report of a friend who had no problems at all with 6.4 and CFS...strange)
startproc /usr/sbin/cfsd || return=$rc_failed mount -o port=3049,intr localhost:/.cfsfs /crypt || return=$rc_failed
After I accidently changed the port to 2049 this mount request worked, but /crypt is mounted with permissions 000, so this seems not to be the correct way. I think it has something to do with the Portmapper : When mounting this is syslogged : nfs: RPC call returned error 111 RPC: task of released request still queued! RPC: (task is on xprt_pending) nfs_read_super: get root fattr failed
Hey Roland, I think you're on to something. I see the same errors in my log, always prefaced by "mountd[136]: authenticated mountv1 request from localhost:1021 for /.cfsfs (/.cfsfs)" Anybody know what the "error 111" means? -- ======================================================= Glenn Holmer (ulthar@execpc.com) ------------------------------------------------------- Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn. (In his house at R'lyeh dead Cthulhu waits dreaming.) ------------------------------------------------------- H. P. Lovecraft, "The Call of Cthulhu", 1926 ======================================================= -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Hey Roland, I think you're on to something. I see the same errors in my log, always prefaced by
"mountd[136]: authenticated mountv1 request from localhost:1021 for /.cfsfs (/.cfsfs)"
Anybody know what the "error 111" means? It works again! I found this document : http://www.ltsp.org/download/lts/lts_tsguide.html There is a section about RPC error 111 in it. It points the source of the problem to the hosts.deny/allow files. For me it was not in
these files, but after looking at these file I looked around. First, portmapper is no longer specified in /etc/services. I added portmapper 111/udp portmapper 111/tcp again. (Maybe it's irrelevant, but I want to be comprehensive) Second, I noticed that tcpdmatch could not check for portmapper denials, because warning: host address ::ffff:127.0.0.1->name lookup failed That brought me to the /etc/hosts file. After commenting out the IPv6 lines (I think they were added by the new Yast, because I have never seen them before) CFS worked again ! (I rebooted to make sure all changed files were reread.) I hope this does the trick for you too, Glenn. bye Roland -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Roland Pabel wrote:
First, portmapper is no longer specified in /etc/services. I added portmapper 111/udp portmapper 111/tcp again. (Maybe it's irrelevant, but I want to be comprehensive) Second, I noticed that tcpdmatch could not check for portmapper denials, because warning: host address ::ffff:127.0.0.1->name lookup failed That brought me to the /etc/hosts file. After commenting out the IPv6 lines (I think they were added by the new Yast, because I have never seen them before) CFS worked again ! (I rebooted to make sure all changed files were reread.)
That worked for me, too, although it doesn't always come up the first time; sometimes I have to restart it and then it comes up the second time. Interestingly, I compared with my 6.3 (which I still have in a different partition), and it didn't have portmapper in /etc/services either, although both 6.3 and 6.4 have sunrpc on that port. Is it a bad thing to have two services listed for one port? I'm just glad it works; in any case, Matt Blaze posted on the CFS users mailing list recently and said he was going to release a 2.0 soon. -- ======================================================= Glenn Holmer (ulthar@execpc.com) ------------------------------------------------------- Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn. (In his house at R'lyeh dead Cthulhu waits dreaming.) ------------------------------------------------------- H. P. Lovecraft, "The Call of Cthulhu", 1926 ======================================================= -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (2)
-
pabel＠tabu.uni-bonn.de -
ulthar＠execpc.com