Hi Strahil,Diego,
Thanks for your help. Moving the folder on the Arbiter and touching the
directory on another node solved the issue.
Much appreciated
David
On Thu, 23 Feb 2023 at 13:29, Diego Zuccato wrote:
> IIUC that should be it.
> But I think you also should remove the gfid file correspon
Just to confirm I've got this correct?
So I'll move the directory with the different gfid on the Arbiter brick to
somewhere else
I then touch this directory on another brick(software is not sensitive to
atime update)
I guess the healing should then take place automatically?
Thanks
David
On Thu,
Move away the file located onthe arbiter brick as it has different gfid and
touch it(only if the software that consumes it is NOT sensitive to atime
modification).
Best Regards,Strahil Nikolov
On Wed, Feb 22, 2023 at 13:09, David Dolan wrote: Hi
Strahil,
The output in my previous email s
Hi Strahil,
The output in my previous email showed the directory the file is located in
with a different GFID on the Arbiter node compared with the bricks on the
other nodes.
Based on that, do you know what my next step should be?
Thanks
David
On Wed, 15 Feb 2023 at 09:21, David Dolan wrote:
sorry I didn't receive the previous email.
I've run the command on all 3 nodes(bricks). See below. The directory only
has one file.
On the Arbiter, the file doesn't exist and the directory the file should be
in has a different GFID than the bricks on the other nodes
Node 1 Brick
getfattr -d -m . -
I guess you didn't receive my last e-mail.
Use getfattr and identify if the gfid mismatch. If yes, move away the
mismatched one.
In order a dir to heal, you have to fix all files inside it before it can be
healed.
Best Regards,
Strahil Nikolov В вторник, 14 февруари 2023 г., 14:04:31 ч. Гри
I've touched the directory one level above the directory with the I\O issue
as the one above that is the one showing as dirty.
It hasn't healed. Should the self heal daemon automatically kick in here?
Is there anything else I can do?
Thanks
David
On Tue, 14 Feb 2023 at 07:03, Strahil Nikolov wr
Setting blame on client-1 and client-2 will make a bigger mess.Can't you touch
the affected file from the FUSE mount point ?
Best Regards,Strahil Nikolov
On Tue, Feb 7, 2023 at 14:42, David Dolan wrote: Hi
All.
Hoping you can help me with a healing problem. I have one file which didn't
Hi All.
Hoping you can help me with a healing problem. I have one file which didn't
self heal.
it looks to be a problem with a directory in the path as one node says it's
dirty. I have a replica volume with arbiter
This is what the 3 nodes say. One brick on each
Node1
getfattr -d -m . -e hex /pat
