I think I found one problem with the mount script. Please look at the output of
sh-4.2# cat /var/log/glusterfs/container/mountfstab
mount: special device /dev/mapper/vg_8377c3ad7380bc5110664247eff77dc6-brick_2de9b07bd586eeae37a378737b137c96 does not exist
mount command exited with code 32
Now, I am able to mount the same device using the command:
mount -a --fstab /var/lib/heketi/fstab
We need to debug this further. At the minimum we need to ensure that the pod does not start at all if /etc/systemd/system/gluster-setup.service fails.
The upstream fix PR # https://github.com/gluster/gluster-containers/pull/103
This is interesting that the issue is always seen for bricks which are part of BHV.
saravana, can you please confirm or update the workaround mentioned in c#29 ?
Workaround: ( Thanks to Atin++ and Saravana++)
Mount the brick(s) :
# mount -a --fstab /var/lib/heketi/fstab
Start the corresponding volume
# gluster volume start <volume name> force
The explanation is very plausible, and let's treat the image of
as a proposed patch for this problem.
proposing for 3.11.0
Updated doc text kindly review for technical accuracy.
Looks good to me, thanks! I just changed the last words to "logical volumes", as there are multiple of them, not only one.
Neils, thank you for the update.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.