With only one sever reboot it should not lead to this issue. Will it be possible to send the logs so that I can root cause the issue. What is the version of glusterfs? Are you sure the file is not in active use at the time of getfattr command execution? Check md5sums of the files on both the bricks when no operations are in progress on the file. If they are same we can erase these changelog xattrs and things should be back to normal. If md5sums are different then one needs to figure out which files are more recent and edit the xattrs so that it is healed in the right direction. I can help you with this on IRC. my nick on irc is pranithk. I will be online in 30 minutes. But It is still not clear how the files ended up in this situation. How many files are in this status. Logs would be helpful. Pranith. ----- Original Message ----- > From: "Nux!" <nux at li.nux.ro> > To: "Pranith Kumar Karampuri" <pkarampu at redhat.com> > Cc: "Gluster Users" <gluster-users at gluster.org> > Sent: Monday, August 5, 2013 2:52:26 PM > Subject: Re: No active sinks for performing self-heal on file > > On 05.08.2013 10:15, Pranith Kumar Karampuri wrote: > > Nux, > > This can happen if there is a failure on both the files in > > write/truncate/ftruncate. I am wondering how the file went into such a > > state. > > Could you throw some light as to what had happened? > > Not really, one of the servers hosting one of the bricks did have to be > power cycled, but I'd imagine this is not a problem for glusterfs. > Does this mean the file is corrupt? What can I do to fix the issue? > > Lucian > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro >
