Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I'm running a CentOS 4 server with a reiserFS partition mounted as /home/public (I've recompiled the kernel to include RFS support and can read/write as normal to that device).
My /etc/exports shows my client computer's subnet (192.168.1.0/255.255.255.0) and the fact that it should be exported '(rw)'. There is nothing in /etc/hosts.deny, and in /etc/hosts.allow portmap is set to accept from the same subnet. I have restarted the nfs and portmap daemons after adjusting all config files. I have included an iptables rule to accept anything coming from the server (based on source IP).
From the client, if I mount the device (192.168.1.103:/home/public), I get a 'cannot read superblock' error after some minutes. If I include the "-o nolock" option, it mounts up just fine. However, the device is mounted as read-only; definitely not the behavior I want nor expect.
Is there some fundamental aspect of NFS I'm missing? I've had wonderful success with these same settings on Slackware in the past, but for some reason I'm hitting a wall I can't see over.
I'm using Slackware 11 for the client computer -- I'm sure the UIDs don't match but the directory I was attempting to write to as a test has 1777 permission. I was just trying to create a 'Transfer' directory in which to put things to be sorted once I had more time.