Re: Hundreds of duplicate files

[Joe Julian <joe@xxxxxxxxxxxxxxxx>]

On 02/18/2015 10:52 AM, Olav Peeters wrote:

Hi all,
I'm have this problem after upgrading from 3.5.3 to 3.6.2.
At the moment I am still waiting for a heal to finish (on a 31TB volume with 42 bricks, replicated over three nodes).

Tom,
how did you remove the duplicates?
with 42 bricks I will not be able to do this manually..
Did a:
find $brick_root -type f -size 0 -perm 1000 -exec /bin/rm {} \;
work for you?

Should this type of thing ideally not be checked and mended by a heal?

This problem should never happen. If it does, yes, I believe this should be recognized by gluster and fixed. The problem is, nobody's been able to reproduce this in a lab and those that have found it have only found it in production. Since those in production want it fixed quickly, there's generally no ability to go back and forth with the developers to adequately identify the problem and file a proper bug report.

If you have the time to figure out what happened, please file a bug report and provide any feedback the developers need to be able to reproduce this problem.

https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS

Does anyone have an idea yet how this happens in the first place? Can it be connected to upgrading?

You have given me one clue, above, that may be relevant. "I am waiting for a heal to finish". One guess would be that if you have volumes in an unhealed state and upgrade while unhealed, perhaps that may be a possible issue.

Cheers,
Olav
On 01/01/15 03:07, tbenzvi@xxxxxxxxxxxxxxx wrote:

No, the files can be read on a newly mounted client! I went ahead and deleted all of the link files associated with these duplicates, and then remounted the volume. The problem is fixed!

Thanks again for the help, Joe and Vijay.

 

Tom

 

--------- Original Message ---------

Subject: Re: Hundreds of duplicate files
From: "Vijay Bellur" <vbellur@xxxxxxxxxx>
Date: 12/28/14 3:23 am
To: tbenzvi@xxxxxxxxxxxxxxx, gluster-users@xxxxxxxxxxx

On 12/28/2014 01:20 PM, tbenzvi@xxxxxxxxxxxxxxx wrote:
> Hi Vijay,
> Yes the files are still readable from the .glusterfs path.
> There is no explicit error. However, trying to read a text file in
> python simply gives me null characters:
>
> >>> open('ott_mf_itab').readlines()
> ['\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00']
>
> And reading binary files does the same
>

Is this behavior seen with a freshly mounted client too?

-Vijay

> --------- Original Message ---------
> Subject: Re: Hundreds of duplicate files
> From: "Vijay Bellur" <vbellur@xxxxxxxxxx>
> Date: 12/27/14 9:57 pm
> To: tbenzvi@xxxxxxxxxxxxxxx, gluster-users@xxxxxxxxxxx
>
> On 12/28/2014 10:13 AM, tbenzvi@xxxxxxxxxxxxxxx wrote:
> > Thanks Joe, I've read your blog post as well as your post
> regarding the
> > .glusterfs directory.
> > I found some unneeded duplicate files which were not being read
> > properly. I then deleted the link file from the brick. This always
> > removes the duplicate file from the listing, but the file does not
> > always become readable. If I also delete the associated file in the
> > .glusterfs directory on that brick, then some more files become
> > readable. However this solution still doesn't work for all files.
> > I know the file on the brick is not corrupt as it can be read
> directly
> > from the brick directory.
>
> For files that are not readable from the client, can you check if the
> file is readable from the .glusterfs/ path?
>
> What is the specific error that is seen while trying to read one such
> file from the client?
>
> Thanks,
> Vijay
>
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users@xxxxxxxxxxx
> http://www.gluster.org/mailman/listinfo/gluster-users
>

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users