On Mon, 2019-08-26 at 11:28 -0400, Bob Goodwin wrote:
> Yes, /etc/exports is what I have been using. You suggested it should
> be subordinate to something, /home or /home/bobg perhaps. I can't
> find that.
Your exports file is missing the filepath(s) you want to export. You
list the directories t
On 8/27/19 6:15 AM, Tom Horsley wrote:
> On Tue, 27 Aug 2019 05:58:59 +0800
> Ed Greshko wrote:
>
>> host
>> The host or network to which the export is being shared
> I'd point out that the host names need to be able to
> be found by a gethostbyname() call at the time the NFS
> server starts. It ha
On 26Aug2019 11:28, Bob Goodwin wrote:
On 8/26/19 11:21 AM, Ed Greshko wrote:
What have you been editing up until now?
/etc/exports is the file you should be concerned with.
.
Yes, /etc/exports is what I have been using. You suggested it should
be subordinate to something, /home or /home/bob
On Tue, 27 Aug 2019 05:58:59 +0800
Ed Greshko wrote:
> host
> The host or network to which the export is being shared
I'd point out that the host names need to be able to
be found by a gethostbyname() call at the time the NFS
server starts. It has been my experience that the slightest
error in ev
On 8/26/19 11:53 PM, Bob Goodwin wrote:
>
> i have been using the Fedora document
> https://fedoraproject.org/wiki/Administration_Guide_Draft/NFS in trying to
> set this up. It does not seem to be what I have used in the past but it is
> what I found searching with Google. Next I will replace th
i have been using the Fedora document
https://fedoraproject.org/wiki/Administration_Guide_Draft/NFS in trying
to set this up. It does not seem to be what I have used in the past but
it is what I found searching with Google. Next I will replace the NFS
hard drive and start over with a new one,
On 8/26/19 11:21 AM, Ed Greshko wrote:
What have you been editing up until now?
/etc/exports is the file you should be concerned with.
.
Yes, /etc/exports is what I have been using. You suggested it should be
subordinate to something, /home or /home/bobg perhaps. I can't find that.
--
Bob
On 8/26/19 11:18 PM, Bob Goodwin wrote:
>
>
> On 8/26/19 10:46 AM, Ed Greshko wrote:
>> You need to specify the directory path to be exported!!
>>
>> /home
>> 192.168.2.0/24(rw,async,no_wdelay,no_root_squash,insecure_locks,sec=sys)
>>
>> Would be an example of a valid entry.
> .
> Well this is wha
On 8/26/19 10:46 AM, Ed Greshko wrote:
You need to specify the directory path to be exported!!
/home 192.168.2.0/24(rw,async,no_wdelay,no_root_squash,insecure_locks,sec=sys)
Would be an example of a valid entry.
.
Well this is what I see, dunno which one I need to use, .etc looked like
it t
On 8/26/19 10:43 PM, Bob Goodwin wrote:
>
>
> On 8/26/19 10:25 AM, Ed Greshko wrote:
>> Again
>>
>> What is your /etc/exports file now on the server? If it is not in the
>> proper format you can't expect
>> anything to work properly.
> .
> [root@NFS bobg]# cat /etc/exports
>
On 8/26/19 10:25 AM, Ed Greshko wrote:
Again
What is your /etc/exports file now on the server? If it is not in the proper
format you can't expect
anything to work properly.
.
[root@NFS bobg]# cat /etc/exports
# 192.168.2.0/24(rw,no_root_squash)
192.168.2.0/24(rw,async,no_wdelay,no_ro
On 8/26/19 10:01 PM, Bob Goodwin wrote:
>
>
> On 8/26/19 6:30 AM, Ed Greshko wrote:
>> Your server isn't running properly. There is no mountd.
> .
> [root@box83 bobg]# showmount -e 192.168.2.128
> clnt_create: RPC: Program not registered
>
> [root@NFS bobg]# systemctl start nfs-mountd
>
> And it s
Am 2019-08-26 16:01, schrieb Bob Goodwin:
On 8/26/19 6:30 AM, Ed Greshko wrote:
Your server isn't running properly. There is no mountd.
.
[root@box83 bobg]# showmount -e 192.168.2.128
clnt_create: RPC: Program not registered
[root@NFS bobg]# systemctl start nfs-mountd
And it still shows Dead
On 8/26/19 6:30 AM, Ed Greshko wrote:
Your server isn't running properly. There is no mountd.
.
[root@box83 bobg]# showmount -e 192.168.2.128
clnt_create: RPC: Program not registered
[root@NFS bobg]# systemctl start nfs-mountd
And it still shows Dead:
[root@NFS bobg]# systemctl status nfs-
On 8/26/19 6:47 PM, Ed Greshko wrote:
> [root@f30-k etc]# cat exports
> /home/egreshko
> 2001:B030:112F:::/56(rw,async,no_wdelay,no_root_squash,insecure_locks,sec=sys)
FYI, this output of the cat should have shown on one line. I think my email
client is
warping too soon.
--
If simple qu
On 8/26/19 5:34 PM, Bob Goodwin wrote:
> [root@NFS bobg]# cat /etc/exports
>
> 192.168.2.0/24(rw,soft,intr,fg,comment=systemd.automount)
Here is a sample of a good/working exports file on a test nfs server here. I'm
testing
IPv6 only at the moment but the format is identical when using IPv4 addr
On 8/26/19 6:11 PM, Bob Goodwin wrote:
>
>
> On 8/26/19 5:49 AM, Alexander Dalloz wrote:
>>> at mean and how do I fix it?
>>
>> First fix the exports file. Then make sure the NFS server runs the required
>> RPC
>> services: portmapper, nfs and mountd. You can check that by
>>
>> rpcinfo -p
>>
>>
On 8/26/19 5:49 PM, Alexander Dalloz wrote:
> Am 2019-08-26 11:34, schrieb Bob Goodwin:
>
> [ ... ]
>
>> I edited to remove the "/home ". I believe that was a mistype when
>> configuring /etc/exports ...
>>
>> presently it is:
>>
>> [root@NFS bobg]# cat /etc/exports
>>
>> 192.168.2.0/24(rw,soft,
On 8/26/19 5:49 AM, Alexander Dalloz wrote:
at mean and how do I fix it?
First fix the exports file. Then make sure the NFS server runs the
required RPC services: portmapper, nfs and mountd. You can check that by
rpcinfo -p
Alexander
.
Before fixing exports -
[root@NFS bobg]# rpcinfo
Am 2019-08-26 11:34, schrieb Bob Goodwin:
[ ... ]
I edited to remove the "/home ". I believe that was a mistype when
configuring /etc/exports ...
presently it is:
[root@NFS bobg]# cat /etc/exports
192.168.2.0/24(rw,soft,intr,fg,comment=systemd.automount)
No, that's wrong now. Please see
On 8/26/19 12:02 AM, Ed Greshko wrote:
On 8/26/19 11:36 AM, Samuel Sieb wrote:
On 8/25/19 7:06 PM, Ed Greshko wrote:
On 8/26/19 6:57 AM, Cameron Simpson wrote:
mount shows:
192.168.2.128:/home on /mnt/testb type nfs4
(rw,relatime,vers=4.2,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,
On 8/26/19 11:36 AM, Samuel Sieb wrote:
> On 8/25/19 7:06 PM, Ed Greshko wrote:
>> On 8/26/19 6:57 AM, Cameron Simpson wrote:
mount shows:
192.168.2.128:/home on /mnt/testb type nfs4
(rw,relatime,vers=4.2,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sy
On 8/25/19 7:06 PM, Ed Greshko wrote:
On 8/26/19 6:57 AM, Cameron Simpson wrote:
mount shows:
192.168.2.128:/home on /mnt/testb type nfs4
(rw,relatime,vers=4.2,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.2.6,local_lock=none,addr=192.168.2.1
On 26Aug2019 10:06, Ed Greshko wrote:
On 8/26/19 6:57 AM, Cameron Simpson wrote:
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
Looks normal, matches what was in your "mount" command above.
I would say it looks sorta normal yet a
On 8/26/19 6:57 AM, Cameron Simpson wrote:
>> mount shows:
>> 192.168.2.128:/home on /mnt/testb type nfs4
>> (rw,relatime,vers=4.2,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.2.6,local_lock=none,addr=192.168.2.128)
>>
>> gvfsd-fuse on /run/use
On 25Aug2019 12:28, Bob Goodwin wrote:
On 8/23/19 7:07 PM, Cameron Simpson wrote:
Also, you can check from the client what a server is prepared to
export to you:
showmount -e 192.168.2.128
.
[root@box6 bobg]# mount 192.168.2.128:/home /mnt/testb
[root@box6 bobg]# showmount -e 192.168.2.1
On 8/23/19 7:07 PM, Cameron Simpson wrote:
Also, you can check from the client what a server is prepared to
export to you:
showmount -e 192.168.2.128
.
[root@box6 bobg]# mount 192.168.2.128:/home /mnt/testb
[root@box6 bobg]# showmount -e 192.168.2.128
Export list for 192.168.2.128:
/
On 23Aug2019 17:53, Bob Goodwin wrote:
On 8/23/19 1:31 PM, Samuel Sieb wrote:
Assuming you are trying to mount an external /home and the server is
192.168.2.128, the command on the client would be:
mount 192.168.2.128:/home /home
Also, you can check from the client what a server is prepared
On 8/23/19 1:31 PM, Samuel Sieb wrote:
On 8/23/19 8:13 AM, Bob Goodwin wrote:
[bobg@localhost-live ~]$ cat /etc/exports
/home 192.168.2.0/24(rw,no_root_squash)
but now I am wondering where is that "/home " coming from? I
didn't notice that before ...
It has to be there. That tells the
On 8/23/19 8:13 AM, Bob Goodwin wrote:
[bobg@localhost-live ~]$ cat /etc/exports
/home 192.168.2.0/24(rw,no_root_squash)
but now I am wondering where is that "/home " coming from? I didn't
notice that before ...
It has to be there. That tells the nfs server what it should be sharing
a
On 8/21/19 7:19 AM, Tom H wrote:
[root@bobg bobg]# mount 192.168.2.128 /mnt/testb
mount: /mnt/testb: special device 192.168.2.128 does not exist.
You need to run "mount 192.168.2.128:/path/2/exported/fs /mnt/testb"
.
If I understand. I think the "path" is complete?
-rw-r--r--. 1 root root 41
On Wed, Aug 21, 2019 at 12:47 PM Bob Goodwin wrote:
>
> After what appears to be an equipment failure I am having trouble
> getting a new server connected to a client. After trying whatever I can
> think of the client still does:
>
> [root@bobg bobg]# mount 192.168.2.128 /mnt/testb
> mount: /mnt/t
On 8/21/19 6:36 PM, Bob Goodwin wrote:
> After what appears to be an equipment failure I am having trouble getting a
> new server
> connected to a client. After trying whatever I can think of the client still
> does:
>
> [root@bobg bobg]# mount 192.168.2.128 /mnt/testb
> mount: /mnt/testb: specia
After what appears to be an equipment failure I am having trouble
getting a new server connected to a client. After trying whatever I can
think of the client still does:
[root@bobg bobg]# mount 192.168.2.128 /mnt/testb
mount: /mnt/testb: special device 192.168.2.128 does not exist.
While ssh s
On 10.5.2012 20:44, Bill Davidsen wrote:
Veli-Pekka Kestilä wrote:
On 10.5.2012 0.40, Bill Davidsen wrote:
Ed Greshko wrote:
On 05/09/2012 10:26 PM, Bill Davidsen wrote:
I get a message "rpc.idmapd appears not to be running" when it is
running,
and I'm
This is the only machine which stopp
Veli-Pekka Kestilä wrote:
On 10.5.2012 0.40, Bill Davidsen wrote:
Ed Greshko wrote:
On 05/09/2012 10:26 PM, Bill Davidsen wrote:
I get a message "rpc.idmapd appears not to be running" when it is running,
and I'm
mount is "rw,soft,intr -t nfs4" and the idmap process is running on host and
clie
On 10.5.2012 0.40, Bill Davidsen wrote:
Ed Greshko wrote:
On 05/09/2012 10:26 PM, Bill Davidsen wrote:
I get a message "rpc.idmapd appears not to be running" when it is
running, and I'm
mount is "rw,soft,intr -t nfs4" and the idmap process is running on
host and
client, remounts from other
On 05/10/2012 01:54 PM, Ed Greshko wrote:
> The good news isI was able to duplicate your problem. The bad news
> is...I'm
> unable to find a solution
>
> The "good" news is *everyone* seems to have the problem
>
> http://bugs.centos.org/view.php?id=5579
Oh. But one thing.
E
On 05/10/2012 05:40 AM, Bill Davidsen wrote:
> Ed Greshko wrote:
>> On 05/09/2012 10:26 PM, Bill Davidsen wrote:
>>> I get a message "rpc.idmapd appears not to be running" when it is running,
>>> and I'm
>>> using the same setup I have on my other clients from FC9 to fc17, including
>>> both
>>>
it would be nice and useful if you can show /etc/sysconfig/iptables,
/etc/sysconfig/nfs from both machines and showmount -e $server from
client side and exports from server side.
On 9 May 2012 23:40, Bill Davidsen wrote:
> Ed Greshko wrote:
>>
>> On 05/09/2012 10:26 PM, Bill Davidsen wrote:
>>>
On 05/09/2012 02:40 PM, Bill Davidsen wrote:
Sorry, I intended the subject to make that clear, the client is CentOS-5
the server FC16. The message appears on the CentOS5 client. The same
server and data works on clients running FC9, FC10, FC13, RHEL-6, and I
believe (ie. I'm told but haven't pe
Ed Greshko wrote:
On 05/09/2012 10:26 PM, Bill Davidsen wrote:
I get a message "rpc.idmapd appears not to be running" when it is running, and
I'm
using the same setup I have on my other clients from FC9 to fc17, including both
32/64 bit RHEL. Checked DNS to be sure the IP reverse maps properly,
On 05/09/2012 10:26 PM, Bill Davidsen wrote:
> I get a message "rpc.idmapd appears not to be running" when it is running,
> and I'm
> using the same setup I have on my other clients from FC9 to fc17, including
> both
> 32/64 bit RHEL. Checked DNS to be sure the IP reverse maps properly, etc,
> e
I get a message "rpc.idmapd appears not to be running" when it is running, and
I'm using the same setup I have on my other clients from FC9 to fc17, including
both 32/64 bit RHEL. Checked DNS to be sure the IP reverse maps properly, etc,
etc. I do this on a real bunch of other machines, so I'm r
44 matches
Mail list logo
