On 11-Sep-2000 Dan Horth spoke something to the effect: > At 9:29 PM -0500 10/9/00, Uncle Meat wrote: >>At this point and the last few bits shown, you either messed something up >>in the transpositions, or it's obvious what the mistake is. Under the >>line >>above: >> >> when I try to set up exports: >> [[EMAIL PROTECTED] /root]....... >> >>you show that you are located on 192.168.2.1 and trying to export from >>192.168.2.2, which won't work. If thta's what you have in the exports >>file >>on 192.168.2.1 the problem is solved by fixing that conflict. > > pretty sure the config I sent originally is right - the server is > 192.168.2.1 and the client 192.168.2.2... so the entry in the config > file on 192.168.2.1 says "export this volume to a client at > 192.168.2.2" Well, according to what you posted: >> when I try to set up exports: >> [[EMAIL PROTECTED] /root]# exportfs -ar >> 192.168.2.2:/usr: Invalid argument >> 192.168.2.2:/: Invalid argument This says root is located on 192.168.2.1 and is trying to export/unexport (-a) some directories as well as reexport them (-r) that are located on 192.168.2.2. Root or anybody else can't do that. If the client is 2.2 and the server is 2.1 the exports file has to be wrong because it is clearly trying to export FROM the wrong place (2.2) to whoever is listening (presumably also 2.2). > actually that reminds me - I did screw up the original fstab > anaonymising - by accidentally sticking an extra space in there which > seems to cause problems - but it's not in my fstab file - just the > email - the fstab file actaully looks like this, with the client > address and brackets for options touching: > > [[EMAIL PROTECTED] /root]# cat /etc/exports > / 192.168.2.2(rw) > /usr 192.168.2.2(rw) > /usr/local/src/updates 192.168.2.2(ro,no_root_squash) > /mnt/cdrom 192.168.2.2(ro,no_root_squash) This would be correct. But, it somehow doesn't jibe with the stuff above, at least with SOMETHING associated with the above. By the by, I had to put the no_root_squash entry on all rw to get them to work, whether that's right or not. It still didn't make any difference until I started, stopped and restarted nfs the requisite number of times (whatever that magic number is). As a matter of fact, I didn't stumble on that until AFTER nfs finally decided to work. >>On mine I use something like: >> >>192.168.0.4:/ /server nfs noauto,rw,rsize=8192,wsize=8192,timeo=14,intr >> >>That works fine for everything. I also put "0 0" on the ends, since I >>don't >>want fstab to signal that those partitions should be fsck'd by the wrong >>system. > > those extra options look exciting - but they're on the client side > (/etc/fstab) and the errors I'm getting are when I try to start the > nfs server... > > >> > uhm... I'm confused because this setup worked fine for me prior to >> > 6.2 upgrade. I can't be 100% this is the exact config I was using as >> > I have gone through all sorts of permutations of /etc/fstab and >> > /etc/exports trying to work out what the problem is... it's weird >>> that certain exports work ok and others don't. I have 1 that hasn't worked for me yet. But, I blew it off because it's to a MAC and I just send it over via appletalk anyway. I just presumed that was the reason it didn't operate and didn't dig into it. Otherwise, all of the exports on 2 machines work fine (well, except for some unmounting issues I need to check into, but they mount perfectly). -- Buy land. They've stopped making it. _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
