I recently started using snapshots for a versioned YUM repository. This
While testing one of my update scripts for my yum repositories, it accidentally deleted some of the directories I needed to keep. No problem. I had a snapshot of the previous version that I could easily rebase from.
The NFS Share is FREENAS1:mnt/VM_Vol1/GGVA-Yum-Repos/
So I rolled back the snapshot and checked in FreeNAS's file structure if it had done so. It looked like it had done it without issue.
My NFS mount is defined as:
So I go check it on my NFS client where all the YUM update script runs from and the YUM HTTP repositories are hosted from. It is mounted as /mnt/GGVA-Yum-Repos on my CentOS 7 NFS client:
I have it mounted as on the client:
At first, I thought this was a client caching issue, but it is not. I rebooted the client machine and the same issue there. I tried mounting the share from a new NFS client machine. I had the same issue.
Nothing not worthy is coming up in the client or server logs.
Does anybody have any idea at what I should throw at this thing?
While testing one of my update scripts for my yum repositories, it accidentally deleted some of the directories I needed to keep. No problem. I had a snapshot of the previous version that I could easily rebase from.
The NFS Share is FREENAS1:mnt/VM_Vol1/GGVA-Yum-Repos/
So I rolled back the snapshot and checked in FreeNAS's file structure if it had done so. It looked like it had done it without issue.
Code:
root@FREENAS1:/mnt/VM_Vol1/GGVA-Yum-Repos/CURRENT # ls -l /mnt/VM_Vol1/GGVA-Yum-Repos/CURRENT total 2 drwxr-xr-x 3 root wheel 3 May 17 2019 epel drwxrwxr-x 3 496 493 3 Nov 29 2018 extras lrwxr-xr-x 1 root wheel 25 Nov 11 13:03 os -> ../../CENTOS/7.6.1810/os/ drwxrwxr-x 3 496 493 3 Nov 29 2018 updates root@FREENAS1:/mnt/VM_Vol1/GGVA-Yum-Repos/CURRENT #
My NFS mount is defined as:
Code:
/mnt/VM_Vol1/GGVA-Yum-Repos -alldirs -maproot="root":"wheel"
So I go check it on my NFS client where all the YUM update script runs from and the YUM HTTP repositories are hosted from. It is mounted as /mnt/GGVA-Yum-Repos on my CentOS 7 NFS client:
Code:
ls -l /mnt/GGVA-Yum-Repos/CURRENT/ total 1 drwxrwxr-x. 3 496 493 3 Sep 14 07:26 updates
I have it mounted as on the client:
Code:
freenas1.stc.int:/mnt/VM_Vol1/YUM_Repos on /mnt/data/yum_repos type nfs (rw,noatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.1.1.226,mountvers=3,mountport=892,mountproto=udp,local_lock=none,addr=10.1.1.226)
At first, I thought this was a client caching issue, but it is not. I rebooted the client machine and the same issue there. I tried mounting the share from a new NFS client machine. I had the same issue.
Nothing not worthy is coming up in the client or server logs.
Does anybody have any idea at what I should throw at this thing?