Bug 1783222 - Unable to mount some glusterfs volumes.
Summary: Unable to mount some glusterfs volumes.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterfs
Version: rhgs-3.5
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
: RHGS 3.5.z Batch Update 1
Assignee: Csaba Henk
QA Contact: Nag Pavan Chilakam
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-13 11:10 UTC by Nitin Goyal
Modified: 2020-01-30 06:43 UTC (History)
12 users (show)

Fixed In Version: glusterfs-6.0-25
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-30 06:42:48 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0288 0 None None None 2020-01-30 06:43:08 UTC

Description Nitin Goyal 2019-12-13 11:10:12 UTC
Description of problem:
Unable to mount some glusterfs volumes from the same cluster with error [1] in Additional info.
hitting the same issue as in bz1659824.

I had around 800 volumes in the cluster, I am able to mount some of the volumes and unable to mount some of those 800.

Version-Release number of selected component (if applicable):
glusterfs-6.0-24.el7rhgs.x86_64

How reproducible:


Steps to Reproduce:
1. Create the volumes and mount them.
2.
3.

Actual results:


Expected results:


Additional info:
[1]
[2019-12-13 10:58:17.420687] E [glusterfsd.c:815:gf_remember_backup_volfile_server] 0-glusterfs: failed to set volfile server: File exists
Mount failed. Please check the log file for more details.

, the following error information was pulled from the glusterfs log to help diagnose this issue: 
[2019-12-13 10:58:28.426650] E [fuse-bridge.c:5215:fuse_first_lookup] 0-fuse: first lookup on root failed (Transport endpoint is not connected)

Comment 20 errata-xmlrpc 2020-01-30 06:42:48 UTC
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.

https://access.redhat.com/errata/RHBA-2020:0288


Note You need to log in before you can comment on or make changes to this bug.