Hi,
so I ran gfid_needing_heal_parallel_new.sh. First try, I got a whole bunch of
"ssh_exchange_identification: Connection closed by remote host",
increasing MaxStartups in sshd_config fixed that. The results were the same in
both runs though, so that might be a cosmetic problem.
I ended up
Am Montag, den 02.12.2019, 02:15 -0500 schrieb Ashish Pandey:
>
>
> From: "Gudrun Mareike Amedick"
> To: "Ashish Pandey"
> Cc: "Gluster-users"
> Sent: Friday, November 29, 2019 8:45:13 PM
> Subject: Re: [Gluster-users] Trying to fix files that don't want to heal
>
> Hi Ashish,
>
> thanks
- Original Message -
From: "Gudrun Mareike Amedick"
To: "Ashish Pandey"
Cc: "Gluster-users"
Sent: Friday, November 29, 2019 8:45:13 PM
Subject: Re: [Gluster-users] Trying to fix files that don't want to heal
Hi Ashish,
thanks for your reply. To fulfill the "no
Hi Ashish,
thanks for your reply. To fulfill the "no IO"-requirement, I'll have to wait
until second week of December (9th – 14th).
We originally planned to update GlusterFS from 4.1.7 to 5 and then to 6 in
December. Should we do that upgrade before or after running those scripts?
Kind
Hey Gudrun,
Could you please try to use the scripts and try to resolve it.
We have written some scripts and it is in final phase to get merge -
https://review.gluster.org/#/c/glusterfs/+/23380/
You can find the steps to use these scripts in README.md file
---
Ashish
- Original
Hi,
I have a distributed dispersed volume with files that don't want to heal. I'm
trying to fix them manually.
I'm currently working on a file that is present on all bricks, GFID exists in
.glusterfs-structure and getfattr shows identical attributes for all
files. They look like this:
#
