Hi Olav,
I have a hunch that our problem was caused by improper unmounting of the
gluster volume, and have since found that the proper order should be: kill all
jobs using volume -> unmount volume on clients -> gluster volume stop -> stop
gluster service (if necessary)
In my case, I wrote a Python script to find duplicate files on the mounted
volume, then delete the corresponding link files on the bricks (making sure to
also delete files in the .glusterfs directory)
However, your find command was also suggested to me and I think it's a simpler
solution. I believe removing all link files (even ones that are not causing
duplicates) is fine since the next file access gluster will do a lookup on all
bricks and recreate any link files if necessary. Hopefully a gluster expert can
chime in on this point as I'm not completely sure.
Keep in mind your setup is somewhat different than mine as I have only 5 bricks
with no replication.
Regards,
Tom
--------- Original Message --------- Subject: Re: [Gluster-users] Hundreds of
duplicate files
From: "Olav Peeters" <opeet...@gmail.com>
Date: 2/18/15 10:52 am
To: gluster-users@gluster.org, tben...@3vgeomatics.com
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?
Does anyone have an idea yet how this happens in the first place? Can it be
connected to upgrading?
Cheers,
Olav
On 01/01/15 03:07, tben...@3vgeomatics.com 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: [Gluster-users] Hundreds of
duplicate files
From: "Vijay Bellur" <vbel...@redhat.com>
Date: 12/28/14 3:23 am
To: tben...@3vgeomatics.com, gluster-users@gluster.org
On 12/28/2014 01:20 PM, tben...@3vgeomatics.com 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: [Gluster-users] Hundreds of duplicate files
> From: "Vijay Bellur" <vbel...@redhat.com>
> Date: 12/27/14 9:57 pm
> To: tben...@3vgeomatics.com, gluster-users@gluster.org
>
> On 12/28/2014 10:13 AM, tben...@3vgeomatics.com 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@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
>
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users
