Displaying 3 results from an estimated 3 matches for "a51f".
Did you mean:
551f
2017 Oct 26
0
not healing one file
Hey Richard,
Could you share the following informations please?
1. gluster volume info <volname>
2. getfattr output of that file from all the bricks
getfattr -d -e hex -m . <brickpath/filepath>
3. glustershd & glfsheal logs
Regards,
Karthik
On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote:
> On a side note, try recently released health
2017 Oct 26
3
not healing one file
On a side note, try recently released health report tool, and see if it
does diagnose any issues in setup. Currently you may have to run it in all
the three machines.
On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote:
> Thanks for this report. This week many of the developers are at Gluster
> Summit in Prague, will be checking this and respond next
2017 Oct 26
2
not healing one file
...mmon.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed entry selfheal on a3f5a769-8859-48e3-96ca-60a988eb9358. sources=1 [2] sinks=0
[2017-10-25 10:14:42.223815] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on efd9431c-08cd-45ec-a51f-d35a56cbbe1f. sources=1 [2] sinks=0
[2017-10-25 10:14:42.224689] I [MSGID: 108026] [afr-self-heal-metadata.c:52:__afr_selfheal_metadata_do] 0-home-replicate-0: performing metadata selfheal on efd9431c-08cd-45ec-a51f-d35a56cbbe1f
[2017-10-25 10:14:42.226767] I [MSGID: 108026] [afr-self-heal-common...