OK. I decided to "replicate" what I think is your environment and what I
"think" you want
I have 2 systems
f17x = Server
f17 = Client
Sorry about the similar host names. These are VMs and that is the way I set
them up.
* SERVER ***
[root@f17x etc]#
On 03/12/12 19:58, Ed Greshko wrote:
Please note
/home != /home/home ( != means Not Equal )
If you "grep bobg /etc/passwd" you'd probably see something like
bobg:x:1000:1000:Bob Goodwin:/home/bobg:/bin/bash
Both box7 and box9 see;
[bobg@box7 ~]$ grep bobg /etc/passwd
On 03/12/12 18:35, Ed Greshko wrote:
Please humor me and leave it as "nfs4 defaults 0 0".
Ok,now I have made the same change to /etc/fstab on box9 and it does
not have the extra home directory that I see here in box7? The
system is usable ...
--
http://www.qrz.com/db/W2BOD
On 12/04/2012 08:40 AM, Bob Goodwin - Zuni, Virginia, USA wrote:
> On 03/12/12 18:35, Ed Greshko wrote:
>> Please humor me and leave it as "nfs4 defaults 0 0".
>
># 192.168.1.8:/nfs4exports/ /mnt/BOX8 nfs4 defaults 0 0
>192.168.1.8:/home/ /mnt/HOME1/ nfs4defaults
On 03/12/12 18:35, Ed Greshko wrote:
Please humor me and leave it as "nfs4 defaults 0 0".
# 192.168.1.8:/nfs4exports/ /mnt/BOX8 nfs4 defaults 0 0
192.168.1.8:/home/ /mnt/HOME1/ nfs4defaults 0 0
192.168.1.8:/data/ /mnt/DATA1nfs4defaults 0 0
On 12/03/2012 03:35 PM, Ed Greshko wrote:
When you use the "mount" command manually as you do not all the information contained in
fstab is used. If you were to type "mount -a" then, I believe it would. It may not be
the cause of the boot time issue, but it is probably reason behind seeing
On 12/04/2012 06:12 AM, Bob Goodwin - Zuni, Virginia, USA wrote:
> On 03/12/12 15:46, Bob Goodwin - Zuni, Virginia, USA wrote:
>> On 03/12/12 15:27, Ed Greshko wrote:
>>> Why do you have "bind" listed in the options for a remote mount? It should
>>> be defaults,rw,user just like you have for 192.
On 03/12/12 15:46, Bob Goodwin - Zuni, Virginia, USA wrote:
On 03/12/12 15:27, Ed Greshko wrote:
Why do you have "bind" listed in the options for a remote mount? It
should be defaults,rw,user just like you have for 192.168.1.48.
Confusion I'm sure. I did try "defaults,rw,user" it had no ef
On 03/12/12 15:27, Ed Greshko wrote:
Why do you have "bind" listed in the options for a remote mount? It should be
defaults,rw,user just like you have for 192.168.1.48.
Confusion I'm sure.
Just to make sure I am understanding what you've done
On 192.168.1.8 (the server) show the
On 12/04/2012 12:56 AM, Bob Goodwin - Zuni, Virginia, USA wrote:
cat time again.
>
>[root@box7 bobg]# cat /etc/fstab
This is the CLIENT Yes?
>#
># /etc/fstab
># Created by anaconda on Tue Aug 7 08:37:16 2012
>#
># Accessible filesystems, by reference, are main
On 01/12/12 08:34, Ed Greshko wrote:
Yep, you've pretty much misunderstood the information which was being conveyed
in the link I originally sent you. You placed actual data under /nfsexports.
I would.
unmount the exported file system from all clients. (umount on box7 for example)
Then
On 12/01/2012 08:51 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
> On 01/12/12 07:39, Ed Greshko wrote:
>> On 12/01/2012 08:25 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
>>> > On 01/12/12 05:04, Ed Greshko wrote:
>> This is becoming a bit confusing. Everything that I've included in
>>>
On 01/12/12 07:39, Ed Greshko wrote:
On 12/01/2012 08:25 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
> On 01/12/12 05:04, Ed Greshko wrote:
>> This is becoming a bit confusing. Everything that I've included in this
message has been
>> information on my "SERVER". While it appears that yo
On 12/01/2012 08:25 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
> On 01/12/12 05:04, Ed Greshko wrote:
>> This is becoming a bit confusing. Everything that I've included in this
>> message has been
>> information on my "SERVER". While it appears that you've included
>> information from a "
On 01/12/12 05:04, Ed Greshko wrote:
This is becoming a bit confusing. Everything that I've included in this
message has been
information on my "SERVER". While it appears that you've included information from a
"SERVER"
as well as "CLIENT". I think.
BOX8 = SERVER
BOX7 = CLIENT
Yes?
On 12/01/2012 05:16 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
This is becoming a bit confusing. Everything that I've included in this
message has been
information on my "SERVER". While it appears that you've included information
from a "SERVER"
as well as "CLIENT". I think.
BO
On 30/11/12 21:02, Ed Greshko wrote:
Well First of all /nfs4exports doesn't take up any space. They are bind
mounts which is analogous to symbolic links. I'll illustrate using my nfs
server.
My problem is that saving to /mnt/nfs4exports/home stores the data
in the 50G root space.
On 12/01/2012 07:21 AM, Bob Goodwin - Zuni, Virginia, USA wrote:
> On 30/11/12 13:07, Ed Greshko wrote:
>> I don't know that that is the "proper" way to "fix" the problem. 2AM, so not
>> very clear on the implications of making that change. What I think you
>> really should do is change the fstab
On 30/11/12 13:07, Ed Greshko wrote:
I don't know that that is the "proper" way to "fix" the problem. 2AM,
so not very clear on the implications of making that change. What I
think you really should do is change the fstab entries to
192.168.1.8:/home /mnt/HOME1 nfs4 defaults,rw,user 0 0
19
On 12/01/2012 12:17 AM, Bob Goodwin - Zuni, Virginia, USA wrote:
> On 30/11/12 10:50, Ed Greshko wrote:
>> I think what you're going to find is that on box8 you have this line
>>
>> /nfs4exports
>> 192.168.0.0/24(ro,wdelay,insecure,root_squash,no_subtree_check,fsid=0)
>>
>> And since you've
On 30/11/12 10:50, Ed Greshko wrote:
I think what you're going to find is that on box8 you have this line
/nfs4exports
192.168.0.0/24(ro,wdelay,insecure,root_squash,no_subtree_check,fsid=0)
And since you've specified 192.168.1.8:/nfs4exports/home in your fstab it is as
it says read
On 11/30/2012 11:15 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
No real idea yet. But
>
>I have a problem writing to one nfs4 server from this F-17/64
>computer, /etc/fstab is as follows:
>
>[bobg@box7 ~]$ cat /etc/fstab
>
>
>192.168.1.8:/nfs4exports/home/ /mnt/HO
I have a problem writing to one nfs4 server from this F-17/64
computer, /etc/fstab is as follows:
[bobg@box7 ~]$ cat /etc/fstab
#
# /etc/fstab
# Created by anaconda on Tue Aug 7 08:37:16 2012
#
# Accessible filesystems, by reference, are maintain
23 matches
Mail list logo
