Do a "df /nfs4exports/home" an "ls -ld /"  a "ls -ld /nfs4exports/home" and
a "ls -ld /nfs4exports/" and a "ls -l /nfs4exports".

On the client you can tell which device it is using by what df shows for
it, if / it will show the size of / and if correct it will show the sizes
of the correct fs.



On Sun, Sep 13, 2020, 1:16 PM Bob Goodwin <[email protected]> wrote:

>
>
> On 2020-09-12 20:44, Roger Heflin wrote:
> > If bob did the exportfs -r prior to mounting /home/whatever that is to
> > be exported then it would have exported the directory on / and not
> > what was later mounted.
> >
> > He needs to umount the nfs clients, and run exportfs -r on the server
> > and remount on the clients.   And make sure that if the directory
> > fails to mount on a reboot then the exportfs -r will need to be rerun.
> >
> > The showmount -e will not show if it is the dir on / or the dir on the
> mount.
> °
> I tried this several times and ways and finally rebooted the computer
> and ssh in to the server to do the exportfs -r. However as soon as the
> computer is booted I found /media /nfs was mounted. I unmounted that,
> checked to verify the umount was effective and then did the "exportfs
> -r" command on the nfs server. I also did showmount -e:
>
> [root@nfs bobg]# showmount -e
> Export list for nfs:
> /nfs4exports/home 192.168.50.0/24
>
> I also did:
>
> [root@nfs bobg]# ll /
> ls: unparsable value for LS_COLORS environment variable
> total 72
> lrwxrwxrwx.   1 root root     7 Jul 24  2019 bin -> usr/bin
> dr-xr-xr-x.   7 root root  4096 Dec  8  2019 boot
> drwxr-xr-x.   2 root root  4096 Dec  6  2019 data
> drwxr-xr-x.  20 root root  4200 Sep 13 11:36 dev
> drwxr-xr-x. 134 root root 12288 Sep 11 22:38 etc
> drwxr-xr-x.   4 root root  4096 Dec  5  2019 home
> lrwxrwxrwx.   1 root root     7 Jul 24  2019 lib -> usr/lib
> lrwxrwxrwx.   1 root root     9 Jul 24  2019 lib64 -> usr/lib64
> drwx------.   2 root root 16384 Oct 23  2019 lost+found
> drwxr-xr-x.   2 root root  4096 Mar 14  2020 media
> drwxr-xr-x.   5 root root  4096 Mar  7  2020 mnt
> drwxrwxr-x.   3 bobg bobg  4096 Dec  8  2019 nfs4exports
> drwxr-xr-x.   2 root root  4096 Jul 24  2019 opt
> dr-xr-xr-x. 162 root root     0 Sep 11 22:38 proc
> dr-xr-x---.   8 root root  4096 Sep 13 10:44 root
> drwxr-xr-x.  43 root root  1320 Sep 13 11:36 run
> lrwxrwxrwx.   1 root root     8 Jul 24  2019 sbin -> usr/sbin
> drwxr-xr-x.   2 root root  4096 Jul 24  2019 srv
> dr-xr-xr-x.  13 root root     0 Sep 11 22:38 sys
> drwxrwxrwt.  12 root root   260 Sep 13 11:36 tmp
> drwxr-xr-x.  12 root root  4096 Oct 23  2019 usr
> drwxr-xr-x.  20 root root  4096 Oct 23  2019 var
> > My data to be stored is bsing put in /nfs4exports/home/ which is
> different than /home, but they are all under root. Is "/home" on the 3.4 TB
> partition or is it still in the 69GB root partition? How do I know? Am I
> exporting the wrong file?
> gparted shows:
> /dev/sda2    ext4 /boot   1.00 GiB   ...etc...
> /dev/sda3    lvm2 pv fedora_localhost...  3.64 TiB
>
> The more I look at this the more confused I get.     Bob
>
>
>
>
> > On Sat, Sep 12, 2020 at 6:31 PM Ed Greshko <[email protected]>
> wrote:
> >> On 2020-09-13 07:21, Jonathan Billings wrote:
> >>> On Sep 12, 2020, at 14:57, Bob Goodwin <[email protected]> wrote:
> >>>> /I am the onlly client and my fstab is:
> >>>> 192.168.50.32:/nfs4exports/home  /media/nfs    nfs4
> rw,soft,intr,fg,comment=systemd.automout  0 0
> >>> I see a typo in the “comment=systemd.automout”.
> >>>
> >>> Also, earlier mail makes me think it’s not actually mounted.  What
> does “mount -a” return?
> >>>
> >>> Does /media/nfs exist?  Once you get the fstab fixed, test to see if
> it automounts.
> >>>
> >> FWIW, I believe the preferred current option is now
> >>
> >> x-systemd.automount
> >>
> >> And if desired
> >>
> >> x-systemd.idle-timeout=
> >> x-systemd.mount-timeout=
> >>
> >> See, man systemd.mount
> >>
> >> --
> >> The key to getting good answers is to ask good questions.
> >> _______________________________________________
> >> users mailing list -- [email protected]
> >> To unsubscribe send an email to [email protected]
> >> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >> List Archives:
> https://lists.fedoraproject.org/archives/list/[email protected]
> > _______________________________________________
> > users mailing list -- [email protected]
> > To unsubscribe send an email to [email protected]
> > Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> https://lists.fedoraproject.org/archives/list/[email protected]
>
> --
> Bob Goodwin - Zuni, Virginia, USA
> FEDORA-32/64bit LINUX XFCE Fastmail POP3
> _______________________________________________
> users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[email protected]
>
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]

Reply via email to