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 Messag
Hello everyone,
For a change, you are seeing me posting release planning email, instead of
Shyam, (and recently Rinku/Hari). Just today, I summed up my thoughts on
Gluster’s release planning in my blog [1]. Continuation of that, I am
asking for providing your valuable feedback on what are the feat
Hi Deepu,
Can you try this:
ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i
/var/lib/glusterd/geo-replication/secret.pem -p 22
sas@192.168.185.118 "sudo gluster volume status"
/sunny
On Thu, Nov 28, 2019 at 12:14 PM deepu srinivasan wrote:
>>
>> MASTER NODEMASTER VOL
Hi Deepu,
Looks like this is error generated due to ssh restrictions:
Can you please check and confirm ssh is properly configured?
2019-11-28 11:59:12.934436] E [syncdutils(worker
/home/sas/gluster/data/code-misc):809:logerr] Popen: ssh>
**
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:
# getfa
Yeah..zo the right procedure should be to setup a new volume without
sharding and copy everything over.
On Thu, 28 Nov 2019, 06:45 Strahil, wrote:
> I have already tried disabling sharding on a test oVirt volume... The
> results were devastating for the app, so please do not disable sharding.
>
