<div dir="ltr"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 16 May 2019 at 03:05, Paul van der Vlis <<a href="mailto:paul@vandervlis.nl" target="_blank">paul@vandervlis.nl</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Op 15-05-19 om 15:45 schreef Nithya Balachandran:<br>
> Hi Paul,<br>
> <br>
> A few questions:<br>
> Which version of gluster are you using?<br>
<br>
On the server and some clients: glusterfs 4.1.2<br>
On a new client: glusterfs 5.5<br>
<br></blockquote><div>Is the same behaviour seen on both client versions?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> Did this behaviour start recently? As in were the contents of that<br>
> directory visible earlier?<br>
<br>
This directory was normally used in the headoffice, and there is direct<br>
access to the files without Glusterfs. So I don't know.<br></blockquote><div><br></div><div>Do you mean that they access the files on the gluster volume without using the client or that these files were stored elsewhere</div><div>earlier (not on gluster)? Files on a gluster volume should never be accessed directly.</div><div><br></div><div>To debug this further, please send the following:</div><div><ol><li>The directory contents when the listing is performed directly on the brick.</li><li>The tcpdump of the gluster client when listing the directory using the following command:</li></ol></div></div></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div dir="ltr"><div class="gmail_quote"><div>tcpdump -i any -s 0 -w /var/tmp/dirls.pcap tcp and not port 22</div></div></div></blockquote><div dir="ltr"><div class="gmail_quote"><div><br></div><div>You can send these directly to me in case you want to keep the information private.</div><div><br></div><div>Regards,</div><div>Nithya</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
With regards,<br>
Paul van der Vlis<br>
<br>
> Regards,<br>
> Nithya<br>
> <br>
> <br>
> On Wed, 15 May 2019 at 18:55, Paul van der Vlis <<a href="mailto:paul@vandervlis.nl" target="_blank">paul@vandervlis.nl</a><br>
> <mailto:<a href="mailto:paul@vandervlis.nl" target="_blank">paul@vandervlis.nl</a>>> wrote:<br>
> <br>
> Hello Strahil,<br>
> <br>
> Thanks for your answer. I don't find the word "sharding" in the<br>
> configfiles. There is not much shared data (24GB), and only 1 brick:<br>
> ---<br>
> root@xxx:/etc/glusterfs# gluster volume info DATA<br>
> <br>
> Volume Name: DATA<br>
> Type: Distribute<br>
> Volume ID: db53ece1-5def-4f7c-b59d-3a230824032a<br>
> Status: Started<br>
> Snapshot Count: 0<br>
> Number of Bricks: 1<br>
> Transport-type: tcp<br>
> Bricks:<br>
> Brick1: xxx-vpn:/DATA<br>
> Options Reconfigured:<br>
> transport.address-family: inet<br>
> nfs.disable: on<br>
> ----<br>
> (I have edited this a bit for privacy of my customer).<br>
> <br>
> I think they have used glusterfs because it can do ACLs.<br>
> <br>
> With regards,<br>
> Paul van der Vlis<br>
> <br>
> <br>
> Op 15-05-19 om 14:59 schreef Strahil Nikolov:<br>
> > Most probably you use sharding , which splits the files into smaller<br>
> > chunks so you can fit a 1TB file into gluster nodes with bricks of<br>
> > smaller size.<br>
> > So if you have 2 dispersed servers each having 500Gb brick-> without<br>
> > sharding you won't be able to store files larger than the brick size -<br>
> > no matter you have free space on the other server.<br>
> ><br>
> > When sharding is enabled - you will see on the brick the first<br>
> shard as<br>
> > a file and the rest is in a hidden folder called ".shards" (or<br>
> something<br>
> > like that).<br>
> ><br>
> > The benefit is also viewable when you need to do some maintenance on a<br>
> > gluster node, as you will need to heal only the shards containing<br>
> > modified by the customers' data.<br>
> ><br>
> > Best Regards,<br>
> > Strahil Nikolov<br>
> ><br>
> ><br>
> > В сряда, 15 май 2019 г., 7:31:39 ч. Гринуич-4, Paul van der Vlis<br>
> > <<a href="mailto:paul@vandervlis.nl" target="_blank">paul@vandervlis.nl</a> <mailto:<a href="mailto:paul@vandervlis.nl" target="_blank">paul@vandervlis.nl</a>>> написа:<br>
> ><br>
> ><br>
> > Hello,<br>
> ><br>
> > I am the new sysadmin of an organization what uses Glusterfs.<br>
> > I did not set it up, and I don't know much about Glusterfs.<br>
> ><br>
> > What I do not understand is that I do not see all data in the mount.<br>
> > Not as root, not as a normal user who has privileges.<br>
> ><br>
> > When I do "ls" in one of the subdirectories I don't see any data, but<br>
> > this data exists at the server!<br>
> ><br>
> > In another subdirectory I see everything fine, the rights of the<br>
> > directories and files inside are the same.<br>
> ><br>
> > I mount with something like:<br>
> > /bin/mount -t glusterfs -o acl 10.8.0.1:/data /data<br>
> > I see data in /data/VOORBEELD/, and I don't see any data in<br>
> /data/ALGEMEEN/.<br>
> ><br>
> > I don't see something special in /etc/exports or in /etc/glusterfs on<br>
> > the server.<br>
> ><br>
> > Is there maybe a mechanism in Glusterfs what can exclude data from<br>
> > export? Or is there a way to debug this problem?<br>
> ><br>
> > With regards,<br>
> > Paul van der Vlis<br>
> ><br>
> > ----<br>
> > # file: VOORBEELD<br>
> > # owner: root<br>
> > # group: secretariaat<br>
> > # flags: -s-<br>
> > user::rwx<br>
> > group::rwx<br>
> > group:medewerkers:r-x<br>
> > mask::rwx<br>
> > other::---<br>
> > default:user::rwx<br>
> > default:group::rwx<br>
> > default:group:medewerkers:r-x<br>
> > default:mask::rwx<br>
> > default:other::---<br>
> ><br>
> > # file: ALGEMEEN<br>
> > # owner: root<br>
> > # group: secretariaat<br>
> > # flags: -s-<br>
> > user::rwx<br>
> > group::rwx<br>
> > group:medewerkers:r-x<br>
> > mask::rwx<br>
> > other::---<br>
> > default:user::rwx<br>
> > default:group::rwx<br>
> > default:group:medewerkers:r-x<br>
> > default:mask::rwx<br>
> > default:other::---<br>
> > ------<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Paul van der Vlis Linux systeembeheer Groningen<br>
> > <a href="https://www.vandervlis.nl/" rel="noreferrer" target="_blank">https://www.vandervlis.nl/</a><br>
> > _______________________________________________<br>
> > Gluster-users mailing list<br>
> > <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a> <mailto:<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>><br>
> <mailto:<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a> <mailto:<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>>><br>
> > <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
> <br>
> <br>
> <br>
> -- <br>
> Paul van der Vlis Linux systeembeheer Groningen<br>
> <a href="https://www.vandervlis.nl/" rel="noreferrer" target="_blank">https://www.vandervlis.nl/</a><br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a> <mailto:<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>><br>
> <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
> <br>
<br>
<br>
<br>
-- <br>
Paul van der Vlis Linux systeembeheer Groningen<br>
<a href="https://www.vandervlis.nl/" rel="noreferrer" target="_blank">https://www.vandervlis.nl/</a><br>
</blockquote></div></div></div>