I want to share some files between my two computers at home... I try to set up NFS share with YAST2 but can't get it right. The "server-side" i configured with YAST2 and under NFS server. I have dir /public right in the root of my filesystem, that need to be shared. I selected that directory to be shared and in Hostwild cards I have * (options are empty...) Client-side then... Again under YAST2 but now with NFS client I configured the server IP, I even managed to see the other box in my LAN, so the IP is now set.. The filesystem is set to /public and mountpoint is /free (which I created to the root of this machines filesystem. Options I left to default. Then I click 'Finish' and get message 'unable to mount NFS entries from /etc/fstab'. What to do? this is what I got in /etc/fstab conserning this case: 192.168.0.100:/public /free nfs defaults 0 0 PS. sorry if this same thing is posted twice, mail server in our office is doing strange things today...
I selected that directory to be shared and in Hostwild cards I have * (options are empty...)
What's the IP of the client? Try, in this order: Specify ro for the options on the server in Yast2. rcnfs restart (on the client) I don't think it's a good idea to introduce new directories to / Maybe use /home/somewhere/in/your/directory instead? Steve.
fsanta wrote:
I selected that directory to be shared and in Hostwild cards I have * (options are empty...)
What's the IP of the client?
Try, in this order: Specify ro for the options on the server in Yast2. rcnfs restart (on the client)
I don't think it's a good idea to introduce new directories to / Maybe use /home/somewhere/in/your/directory instead?
Steve.
clients IP is 192.168.0.101 rcnfs restart failes... reason given by server: permission denied P_s
On Friday 31 January 2003 18:17, p_s wrote:
fsanta wrote:
I selected that directory to be shared and in Hostwild cards I have * (options are empty...)
What's the IP of the client?
Try, in this order: Specify ro for the options on the server in Yast2. rcnfs restart (on the client)
I don't think it's a good idea to introduce new directories to / Maybe use /home/somewhere/in/your/directory instead?
Steve.
clients IP is 192.168.0.101
rcnfs restart failes... reason given by server: permission denied
P_s
What are the permissions on /public
fsanta wrote:
On Friday 31 January 2003 18:17, p_s wrote:
fsanta wrote:
I selected that directory to be shared and in Hostwild cards I have * (options are empty...)
What's the IP of the client?
Try, in this order: Specify ro for the options on the server in Yast2. rcnfs restart (on the client)
I don't think it's a good idea to introduce new directories to / Maybe use /home/somewhere/in/your/directory instead?
Steve.
clients IP is 192.168.0.101
rcnfs restart failes... reason given by server: permission denied
P_s
What are the permissions on /public
I am user ps so the rights are user: ps and group: users I even tried to chmod 777 it, but that didn't solve this case. P_s
On Friday 31 January 2003 18:35, p_s wrote:
fsanta wrote:
On Friday 31 January 2003 18:17, p_s wrote:
fsanta wrote:
I selected that directory to be shared and in Hostwild cards I have * (options are empty...)
What's the IP of the client?
Try, in this order: Specify ro for the options on the server in Yast2. rcnfs restart (on the client)
I don't think it's a good idea to introduce new directories to / Maybe use /home/somewhere/in/your/directory instead?
Steve.
clients IP is 192.168.0.101
rcnfs restart failes... reason given by server: permission denied
P_s
What are the permissions on /public
I am user ps so the rights are user: ps and group: users
I even tried to chmod 777 it, but that didn't solve this case.
P_s
Can you mount it manually anywhere else? mount -t nfs 192.168.0.100:/public /mnt What does /var/log/messages say? Steve.
fsanta wrote:
On Friday 31 January 2003 18:35, p_s wrote:
fsanta wrote:
On Friday 31 January 2003 18:17, p_s wrote:
fsanta wrote:
I selected that directory to be shared and in Hostwild cards I have * (options are empty...)
What's the IP of the client?
Try, in this order: Specify ro for the options on the server in Yast2. rcnfs restart (on the client)
I don't think it's a good idea to introduce new directories to / Maybe use /home/somewhere/in/your/directory instead?
Steve.
clients IP is 192.168.0.101
rcnfs restart failes... reason given by server: permission denied
P_s
What are the permissions on /public
I am user ps so the rights are user: ps and group: users
I even tried to chmod 777 it, but that didn't solve this case.
P_s
Can you mount it manually anywhere else?
mount -t nfs 192.168.0.100:/public /mnt
No luck... same problem: permission denied.
What does /var/log/messages say?
Nothing that relates to this. P_S
On Friday 31 January 2003 18:47, p_s wrote:
fsanta wrote:
On Friday 31 January 2003 18:35, p_s wrote:
fsanta wrote:
On Friday 31 January 2003 18:17, p_s wrote:
fsanta wrote:
I selected that directory to be shared and in Hostwild cards I have * (options are empty...)
What's the IP of the client?
Try, in this order: Specify ro for the options on the server in Yast2. rcnfs restart (on the client)
I don't think it's a good idea to introduce new directories to / Maybe use /home/somewhere/in/your/directory instead?
Steve.
clients IP is 192.168.0.101
rcnfs restart failes... reason given by server: permission denied
P_s
What are the permissions on /public
I am user ps so the rights are user: ps and group: users
I even tried to chmod 777 it, but that didn't solve this case.
P_s
Can you mount it manually anywhere else?
mount -t nfs 192.168.0.100:/public /mnt
No luck... same problem: permission denied.
What does /var/log/messages say?
Nothing that relates to this.
P_S
Are you using reiserfs? Steve
Hi, This problem is exactly the same problem I have had setting up NFS in 8.1 using YAST2; and I AM using Reiserfs. Still no resolution ......................... PeterB On Friday 31 January 2003 01:51 pm, fsanta wrote:
Can you mount it manually anywhere else?
mount -t nfs 192.168.0.100:/public /mnt
No luck... same problem: permission denied.
What does /var/log/messages say?
Nothing that relates to this.
P_S
Are you using reiserfs? Steve
-- -- Proud to be a SuSE Linux User since 5.2 --
On Friday 31 January 2003 19:22, p_s wrote:
Peter B Van Campen wrote:
Hi,
This problem is exactly the same problem I have had setting up NFS in 8.1 using YAST2; and I AM using Reiserfs. Still no resolution ......................... PeterB
Bloody marvelous :-)
P_s
Seriously, there appears to be a major interraction between nfs and reiser (at least, lots of people report similar problems which are apparently 'cured' by using ext3 instead. Dylan -- "Sweet moderation Heart of this nation Desert us not We are between the wars" Billy Bragg
Dylan wrote:
On Friday 31 January 2003 19:22, p_s wrote:
Peter B Van Campen wrote:
Hi,
This problem is exactly the same problem I have had setting up NFS in 8.1 using YAST2; and I AM using Reiserfs. Still no resolution ......................... PeterB
Bloody marvelous :-)
P_s
Seriously, there appears to be a major interraction between nfs and reiser (at least, lots of people report similar problems which are apparently 'cured' by using ext3 instead.
Dylan
This then leads me to next minor issue.. how to convert from reiserfs to ext3 without need to format whole partition.. that is not possible at the moment.... P_s
->This then leads me to next minor issue.. how to convert from reiserfs to ->ext3 without need to format whole partition.. that is not possible at ->the moment.... -> You can't. They have completely different structures. - Herman
On Friday 31 January 2003 19:35, p_s wrote:
Dylan wrote:
On Friday 31 January 2003 19:22, p_s wrote:
Peter B Van Campen wrote:
Hi,
This problem is exactly the same problem I have had setting up NFS in 8.1 using YAST2; and I AM using Reiserfs. Still no resolution ......................... PeterB
Bloody marvelous :-)
P_s
Seriously, there appears to be a major interraction between nfs and reiser (at least, lots of people report similar problems which are apparently 'cured' by using ext3 instead.
Dylan
This then leads me to next minor issue.. how to convert from reiserfs to ext3 without need to format whole partition.. that is not possible at the moment....
P_s
No. You can't do that. We ended up setting up vsftpd on the server so we could transfer the stuff we needed for it to the client using ftp for a backup and then doing a fresh reinstall of SuSE to the server afterwards. We then used nfs to get it all back again ;) BTW ftp between the two boxes maybe a workaround for you. Steve
Dylan wrote:
On Friday 31 January 2003 19:22, p_s wrote:
Peter B Van Campen wrote:
Hi,
This problem is exactly the same problem I have had setting up NFS in 8.1 using YAST2; and I AM using Reiserfs. Still no resolution ......................... PeterB
Bloody marvelous :-)
P_s
Seriously, there appears to be a major interraction between nfs and reiser (at least, lots of people report similar problems which are apparently 'cured' by using ext3 instead.
Dylan
-- "Sweet moderation Heart of this nation Desert us not We are between the wars" Billy Bragg
We have been running SuSE8.0 with a non SuSE kernel (2.4.20) and NFS with no problem after replacing a 10M/100M hub with a switch which supports 100M speeds better. All machines are running reiser also. Prior to the change we would get a RPC time out problem error at bootup. -- 73 de Donn Washburn __ " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB / / __ __ __ __ __ __ __ 307 Savoy St. / /__ / / / \/ / / /_/ / \ \/ / Sugar Land, TX 77478 /_____/ /_/ /_/\__/ /_____/ /_/\_\ LL# 1.281.242.3256 a MSDOS Virus "Free Zone" OS Email: n5xwb@hal-pc.org Info: http://www.knoppix.com
On Friday 31 January 2003 19:10, fsanta wrote:
I selected that directory to be shared and in Hostwild cards I have * (options are empty...)
What's the IP of the client?
Try, in this order: Specify ro for the options on the server in Yast2. rcnfs restart (on the client)
I don't think it's a good idea to introduce new directories to /
Does the fhs say anything about this?
Maybe use /home/somewhere/in/your/directory instead?
And if another user needs to use it...? Dylan -- "Sweet moderation Heart of this nation Desert us not We are between the wars" Billy Bragg
<snip> Completely disregarding the permissions issue, but:
I don't think it's a good idea to introduce new directories to /
Does the fhs say anything about this?
I'm not sure, but how about using /srv ? I guess that's what its there for... ? MHO Jon Clausen
Jon Clausen wrote:
<snip>
Completely disregarding the permissions issue, but:
I don't think it's a good idea to introduce new directories to /
Does the fhs say anything about this?
I'm not sure, but how about using /srv ?
I guess that's what its there for... ?
I would say that my main concern is not where / what to call the mount point but fix this so that I at least can mount NFS... MHO P_s
On Friday 31 January 2003 19:06, p_s wrote:
I would say that my main concern is not where / what to call the mount point but fix this so that I at least can mount NFS...
One of the best things about these lists is the talk around the issue, it's sometimes where the solution comes from (although definitely not in this case) £0.02 Dylan -- "Sweet moderation Heart of this nation Desert us not We are between the wars" Billy Bragg
On Friday 31 January 2003 19:28, Dylan wrote:
On Friday 31 January 2003 19:06, p_s wrote:
I would say that my main concern is not where / what to call the mount point but fix this so that I at least can mount NFS...
One of the best things about these lists is the talk around the issue, it's sometimes where the solution comes from (although definitely not in this case)
£0.02
Dylan
C'mon guys. Lets help him out like you helped me out. Sidelines when the problem is there staring at us help no one. I really wished I'd never mentioned it in the replying post. So doesn't this point to my solution (which works) of making a decent backup and going ext3? Steve.
Reiser works fine with NFS. Question is, from the client can you do a shwomount -e <server name>? Does it actuallt see the volume being exported? - Herman On Fri, 31 Jan 2003, fsanta wrote: ->On Friday 31 January 2003 19:28, Dylan wrote: ->> On Friday 31 January 2003 19:06, p_s wrote: ->> > I would say that my main concern is not where / what to call the mount ->> > point but fix this so that I at least can mount NFS... ->> ->> One of the best things about these lists is the talk around the issue, it's ->> sometimes where the solution comes from (although definitely not in this ->> case) ->> ->> £0.02 ->> ->> Dylan -> ->C'mon guys. Lets help him out like you helped me out. Sidelines when the ->problem is there staring at us help no one. I really wished I'd never ->mentioned it in the replying post. -> ->So doesn't this point to my solution (which works) of making a decent backup ->and going ext3? -> ->Steve. -> -> ->-- ->Check the headers for your unsubscription address ->For additional commands send e-mail to suse-linux-e-help@suse.com ->Also check the archives at http://lists.suse.com ->Please read the FAQs: suse-linux-e-faq@suse.com -> -> ->
Herman L. Knief wrote:
Reiser works fine with NFS. Question is, from the client can you do a shwomount -e <server name>? Does it actuallt see the volume being exported?
No... /usr/sbin/showmount -e 192.168.0.100 I get only: Export list for 192.168.0.100: Any ideas how to continue. P_s
On Fri, 31 Jan 2003, p_s wrote: ->Herman L. Knief wrote: ->> Reiser works fine with NFS. Question is, from the client can you do a ->> shwomount -e <server name>? Does it actuallt see the volume being ->> exported? ->> -> ->No... -> ->/usr/sbin/showmount -e 192.168.0.100 -> ->I get only: -> ->Export list for 192.168.0.100: -> ->Any ideas how to continue. -> ->P_s -> OK - So it's likely not the client, but the server. Verify your /etc/exports file and then try to restart the NFS server by typing "rcnfs.server restart". Then run the showmount -e <server> from the client again. - Herman
On Friday 31 January 2003 19:50, Herman L. Knief wrote:
Verify your /etc/exports file and then try to restart the NFS server by typing "rcnfs.server restart".
That should be rcnfsserver restart Dylan -- "Sweet moderation Heart of this nation Desert us not We are between the wars" Billy Bragg
* p_s (tuxnduke@welho.com) [030131 12:00]:
Got the server shutdown and up again with this, but no progress.. still only
Export list for 192.168.0.100:
Please ignore the people who are suggesting that you change filesystems or do other drastic things. Wildcards don't work with IP addresses. You need to either use hostnames or the network plus netmask (e.g., 192.68.0.0/24). Also, the IPs need PTR records as well as A records (i.e., the forward and reverse lookups should work). If you aren't using dns it's enough to fill out /etc/hosts on both the server and clients. -- -ckm
Christopher Mahmood wrote:
* p_s (tuxnduke@welho.com) [030131 12:00]:
Got the server shutdown and up again with this, but no progress.. still only
Export list for 192.168.0.100:
Please ignore the people who are suggesting that you change filesystems or do other drastic things.
Wildcards don't work with IP addresses. You need to either use hostnames or the network plus netmask (e.g., 192.68.0.0/24). Also, the IPs need PTR records as well as A records (i.e., the forward and reverse lookups should work). If you aren't using dns it's enough to fill out /etc/hosts on both the server and clients.
This solved the case... I simlply added each other to /etc/hosts and then restarted 'rcnfsserver restart' and right away I was able to see exports wtih showmount -e <server> got them mounted and sharing works like charm. Thanks to all participant. This was one long thread :-) have a pleasant weekend, spend it well, spend it tinkering an hacking ! P_s
Sorry... I always get Solaris and Linux crossed. On Fri, 31 Jan 2003, Dylan wrote: ->On Friday 31 January 2003 19:50, Herman L. Knief wrote: ->> ->> Verify your /etc/exports file and then try to restart the NFS server by ->> typing "rcnfs.server restart". -> ->That should be -> ->rcnfsserver restart -> ->Dylan ->
Herman L. Knief wrote:
On Fri, 31 Jan 2003, p_s wrote:
->Herman L. Knief wrote: ->> Reiser works fine with NFS. Question is, from the client can you do a ->> shwomount -e <server name>? Does it actuallt see the volume being ->> exported? ->> -> ->No... -> ->/usr/sbin/showmount -e 192.168.0.100 -> ->I get only: -> ->Export list for 192.168.0.100: -> ->Any ideas how to continue. -> ->P_s ->
OK - So it's likely not the client, but the server.
Verify your /etc/exports file and then try to restart the NFS server by typing "rcnfs.server restart". Then run the showmount -e <server> from the client again.
- Herman
The other thing to verify is that the portmapper is running. You can check this by running rcportmap status. If it is running, then run rpcinfo -p and see if nfs is listed in the output. NFS relies on RPC and if the RPC services are not running properly it will fail. Regards, Paul
The other thing to verify is that the portmapper is running. You can check this by running rcportmap status.
rcportmap status: Checking for RPC portmap daemon: running
If it is running, then run rpcinfo -p and see if nfs is listed in the output. NFS relies on RPC and if the RPC services are not running properly it will fail.
rpcinfo -p: program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100021 1 udp 32831 nlockmgr 100021 3 udp 32831 nlockmgr 100021 4 udp 32831 nlockmgr 100005 1 udp 32832 mountd 100005 1 tcp 33909 mountd 100005 2 udp 32832 mountd 100005 2 tcp 33909 mountd 100005 3 udp 32832 mountd 100005 3 tcp 33909 mountd 100024 1 udp 32834 status 100024 1 tcp 33910 status P_s
Can you post the /etc/exports file from the server? The file should look like this: /public 192.168.0.0/24(rw,squash_uids=0-100,squash_gids=0-100) The command, /usr/sbin/exportfs, run in the server, should tell you what file systems are exported. There is no problem between NFS and ReiserFS in the SuSE distribution, we've used reiserfs for years now and have had no problems. -- Rafael
What's the date on that FAQ. I run three Linux NFS servers all with ReiserFS just fine. On Fri, 31 Jan 2003, fsanta wrote: ->On Friday 31 January 2003 19:50, Herman L. Knief wrote: ->> On Fri, 31 Jan 2003, p_s wrote: ->> ->> ->Herman L. Knief wrote: ->> ->> Reiser works fine with NFS. -> ->No. www.namesys.com ->The faq. ->Steve -> -> -> ->-- ->Check the headers for your unsubscription address ->For additional commands send e-mail to suse-linux-e-help@suse.com ->Also check the archives at http://lists.suse.com ->Please read the FAQs: suse-linux-e-faq@suse.com -> -> ->
participants (11)
-
Christopher Mahmood -
Donn aka N5XWB -
Dylan -
fsanta -
Herman L. Knief -
Jon Clausen -
p s -
p_s
-
Paul Varner -
Peter B Van Campen -
Rafael E. Herrera