On 11/10/2014 11:21 AM, Vijay Bellur wrote:
On 11/08/2014 08:19 AM, Peter Auyeung wrote:
I have a node down while gfs still open for writing.
Got tons of heal-failed on a replicated volume showing as gfid.
Tried gfid-resolver and got the following:
# ./gfid-resolver.sh /brick02/gfs/
On 11/08/2014 08:19 AM, Peter Auyeung wrote:
I have a node down while gfs still open for writing.
Got tons of heal-failed on a replicated volume showing as gfid.
Tried gfid-resolver and got the following:
# ./gfid-resolver.sh /brick02/gfs/ 88417c43-7d0f-4ec5-8fcd-f696617b5bc1
Heal-failed can be for any reason that's not defined as split brain. The only
place I've been able to find clues is in the log files. Look at the timestamp
on the heal-failed output and match it to log entries in glustershd logs.
On November 7, 2014 6:49:36 PM PST, Peter Auyeung
I have a node down while gfs still open for writing.
Got tons of heal-failed on a replicated volume showing as gfid.
Tried gfid-resolver and got the following:
# ./gfid-resolver.sh /brick02/gfs/ 88417c43-7d0f-4ec5-8fcd-f696617b5bc1
88417c43-7d0f-4ec5-8fcd-f696617b5bc1==File:11/07/14
