Thank you for the suggestion!
I mounted the volume on a new mount point, retrieved the gfid of another file,
and was able to obtain the file information through Method2.
However, when I used the gfids listed in heal, I get a “transport endpoint is
not connected” error, despite them showing as “connected” in heal info (and
volume status).
Thanks,
Collin
From: Strahil Nikolov
Sent: Friday, March 25, 2022 1:47 PM
To: Collin Strassburger ; gluster-users@gluster.org
Subject: Re: [Gluster-users] gfid entries failing to heal
CAUTION - EXTERNAL EMAIL: Do not click any links or open any attachments unless
you trust the sender and know the content is safe.
To find gfid path, you can use
https://docs.gluster.org/en/main/Troubleshooting/gfid-to-path/
Usually, I prefer to mount and then use Method2 to retrieve the path.
Then, you can getfattr the file/dir to get a clue.
Best Regards,
Strahil Nikolov
On Fri, Mar 25, 2022 at 18:51, Collin Strassburger
mailto:cstrassbur...@bihrle.com>> wrote:
Hello,
I am having a problem with a replica 3 volume.
When I run: gluster volume heal hydra_pbs_vol info
It returns:
Brick hydra1:/data/glusterfs/PBS/NonMountDir
Status: Connected
Number of entries: 1
Brick hydra2:/data/glusterfs/PBS/NonMountDir
Status: Connected
Number of entries: 4
Brick viz1:/data/glusterfs/PBS/NonMountDir
Status: Connected
Number of entries: 0
The items have been present for some time and do not appear to be healing.
As shown above, the items are not labeled as split-brain and they do not have
path information to do a manual delete-and-heal.
~~
Content of /var/log/glusterfs/glfsheal-hydra_pbs_vol.log is attached
~~
Info:
gluster volume info hydra_pbs_vol
Volume Name: hydra_pbs_vol
Type: Replicate
Volume ID: efb30804-1c08-4ef6-a579-a2f77d5049e0
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: hydra1:/data/glusterfs/PBS/NonMountDir
Brick2: hydra2:/data/glusterfs/PBS/NonMountDir
Brick3: viz1:/data/glusterfs/PBS/NonMountDir
Options Reconfigured:
performance.client-io-threads: off
nfs.disable: on
transport.address-family: inet
storage.fips-mode-rchecksum: on
cluster.granular-entry-heal: on
features.bitrot: on
features.scrub: Active
~~
Status:
Status of volume: hydra_pbs_vol
Gluster process TCP Port RDMA Port Online Pid
--
Brick hydra1:/data/glusterfs/PBS/NonMountDi
r 49152 0 Y 1518
Brick hydra2:/data/glusterfs/PBS/NonMountDi
r 49152 0 Y 1438
Brick viz1:/data/glusterfs/PBS/NonMountDir 49152 0 Y 2991
Self-heal Daemon on localhost N/A N/AY 1942
Bitrot Daemon on localhost N/A N/AY 1563
Scrubber Daemon on localhostN/A N/AY 1738
Self-heal Daemon on viz1N/A N/AY 3491
Bitrot Daemon on viz1 N/A N/AY 3203
Scrubber Daemon on viz1 N/A N/AY 3261
Self-heal Daemon on hydra2 N/A N/AY 1843
Bitrot Daemon on hydra2 N/A N/AY 1475
Scrubber Daemon on hydra2 N/A N/AY 1651
Task Status of Volume hydra_pbs_vol
--
There are no active volume tasks
~~
How can I resolve these entries/issues?
Thanks,
Collin Strassburger (he/him)
Community Meeting Calendar:
Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
Gluster-users@gluster.org<mailto:Gluster-users@gluster.org>
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://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users
