Well, thanks for the info.
I have upgraded my servers from 7.8-2 to 7.8-3.
7.8-3 contains the needed mount-shared-storage.sh
And Ingo is right - it was not there on 21st of October ...;-)
NOTE: when i disable the glusterfssharedstorage.service, i can live without it.
What is the real purpose of using this service?
Kind regards,
peterk
On Fri, 23 Oct 2020 at 18:34, Ingo Fischer <ingo@xxxxxxxxxxxxx> wrote:
Hi,
verified ... they are available now ... were not on 21.10. :-)
Thank you!
Ingo
Am 23.10.20 um 18:05 schrieb Kaleb Keithley:
>
>
> On Fri, Oct 23, 2020 at 6:15 AM peter knezel <peter.knezel@xxxxxxxxx
> <mailto:peter.knezel@xxxxxxxxx>> wrote:
>
> Hello All,
>
> can somebody responsible confirm me, that mount-shared-storage.sh
> is really missing from glusterfs 7.8-2 packages?
> Will new version be created?
>
>
> It is fixed in 7.8-3, which has been on download.gluster.org
> <http://download.gluster.org> for several days now.
>
>
>
> I have recreated this file manually on my two glusterfs servers
> (i took the mount-shared-storage.sh file from a server that was OS
> updated from debian stretch to debian buster (10.5)) - with 7.8-1 at
> that time:
>
> root@server1:~# cd /usr/lib/x86_64-linux-gnu/glusterfs
> root@server1:/usr/lib/x86_64-linux-gnu/glusterfs# ls -ltr|grep
> storage.sh
> -rwxr-xr-x 1 root root 1259 Oct 23 09:28 mount-shared-storage.sh
> root@server1:/usr/lib/x86_64-linux-gnu/glusterfs# cat
> mount-shared-storage.sh
> #!/bin/bash
> #Post reboot there is a chance in which mounting of shared storage
> will fail
> #This will impact starting of features like NFS-Ganesha. So this
> script will
> #try to mount the shared storage if it fails
>
> exitStatus=0
>
> while IFS= read -r glm
> do
> IFS=$' \t' read -r -a arr <<< "$glm"
>
> #Validate storage type is glusterfs
> if [ "${arr[2]}" == "glusterfs" ]
> then
>
> #check whether shared storage is mounted
> #if it is mounted then mountpoint -q will return a 0
> success code
> if mountpoint -q "${arr[1]}"
> then
> echo "${arr[1]} is already mounted"
> continue
> fi
>
> mount -t glusterfs "${arr[0]}" "${arr[1]}"
> #wait for few seconds
> sleep 10
>
> #recheck mount got succeed
> if mountpoint -q "${arr[1]}"
> then
> echo "${arr[1]} has been mounted"
> continue
> else
> echo "${arr[1]} failed to mount"
> exitStatus=1
> fi
> fi
> done <<< "$(sed '/^#/ d' </etc/fstab | grep 'glusterfs')"
> exit $exitStatus
> root@server1:/usr/lib/x86_64-linux-gnu/glusterfs#
>
> root@server1:/usr/lib/x86_64-linux-gnu/glusterfs# uname -a
> Linux server1 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24)
> x86_64 GNU/Linux
> root@server1:/usr/lib/x86_64-linux-gnu/glusterfs# cat
> /etc/debian_version
> 10.5
> root@server1:/usr/lib/x86_64-linux-gnu/glusterfs#
>
>
> Then I enabled and started glusterfssharedstorage.service.
> It works.
> NOTE: same done on server2 as well.
>
>
>
> Kind regards,
> peterk
>
>
> ________
>
>
>
> Community Meeting Calendar:
>
> Schedule -
> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
> Bridge: https://bluejeans.com/441850968
>
> Gluster-users mailing list
> Gluster-users@xxxxxxxxxxx <mailto:Gluster-users@xxxxxxxxxxx>
> https://lists.gluster.org/mailman/listinfo/gluster-users
>
>
> ________
>
>
>
> Community Meeting Calendar:
>
> Schedule -
> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
> Bridge: https://bluejeans.com/441850968
>
> Gluster-users mailing list
> Gluster-users@xxxxxxxxxxx
> https://lists.gluster.org/mailman/listinfo/gluster-users
>
-
________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users