It seems that I got confused.
So you see the files on the bricks (servers) , but not when you mount glusterfs on the clients ?
If so - this is not the sharding feature as it works the opposite way.
Best Regards,
Strahil Nikolov
В четвъртък, 16 май 2019 г., 0:35:04 ч. Гринуич+3, Paul van der Vlis <paul@xxxxxxxxxxxxx> написа:
Op 15-05-19 om 15:45 schreef Nithya Balachandran:
> Hi Paul,
>
> A few questions:
> Which version of gluster are you using?
On the server and some clients: glusterfs 4.1.2
On a new client: glusterfs 5.5
> Did this behaviour start recently? As in were the contents of that
> directory visible earlier?
This directory was normally used in the headoffice, and there is direct
access to the files without Glusterfs. So I don't know.
With regards,
Paul van der Vlis
> Regards,
> Nithya
>
>
> On Wed, 15 May 2019 at 18:55, Paul van der Vlis <paul@xxxxxxxxxxxxx
> <mailto:paul@xxxxxxxxxxxxx>> wrote:
>
> Hello Strahil,
>
> Thanks for your answer. I don't find the word "sharding" in the
> configfiles. There is not much shared data (24GB), and only 1 brick:
> ---
> root@xxx:/etc/glusterfs# gluster volume info DATA
>
> Volume Name: DATA
> Type: Distribute
> Volume ID: db53ece1-5def-4f7c-b59d-3a230824032a
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 1
> Transport-type: tcp
> Bricks:
> Brick1: xxx-vpn:/DATA
> Options Reconfigured:
> transport.address-family: inet
> nfs.disable: on
> ----
> (I have edited this a bit for privacy of my customer).
>
> I think they have used glusterfs because it can do ACLs.
>
> With regards,
> Paul van der Vlis
>
>
> Op 15-05-19 om 14:59 schreef Strahil Nikolov:
> > Most probably you use sharding , which splits the files into smaller
> > chunks so you can fit a 1TB file into gluster nodes with bricks of
> > smaller size.
> > So if you have 2 dispersed servers each having 500Gb brick-> without
> > sharding you won't be able to store files larger than the brick size -
> > no matter you have free space on the other server.
> >
> > When sharding is enabled - you will see on the brick the first
> shard as
> > a file and the rest is in a hidden folder called ".shards" (or
> something
> > like that).
> >
> > The benefit is also viewable when you need to do some maintenance on a
> > gluster node, as you will need to heal only the shards containing
> > modified by the customers' data.
> >
> > Best Regards,
> > Strahil Nikolov
> >
> >
> > В сряда, 15 май 2019 г., 7:31:39 ч. Гринуич-4, Paul van der Vlis
> > <paul@xxxxxxxxxxxxx <mailto:paul@xxxxxxxxxxxxx>> написа:
> >
> >
> > Hello,
> >
> > I am the new sysadmin of an organization what uses Glusterfs.
> > I did not set it up, and I don't know much about Glusterfs.
> >
> > What I do not understand is that I do not see all data in the mount.
> > Not as root, not as a normal user who has privileges.
> >
> > When I do "ls" in one of the subdirectories I don't see any data, but
> > this data exists at the server!
> >
> > In another subdirectory I see everything fine, the rights of the
> > directories and files inside are the same.
> >
> > I mount with something like:
> > /bin/mount -t glusterfs -o acl 10.8.0.1:/data /data
> > I see data in /data/VOORBEELD/, and I don't see any data in
> /data/ALGEMEEN/.
> >
> > I don't see something special in /etc/exports or in /etc/glusterfs on
> > the server.
> >
> > Is there maybe a mechanism in Glusterfs what can exclude data from
> > export? Or is there a way to debug this problem?
> >
> > With regards,
> > Paul van der Vlis
> >
> > ----
> > # file: VOORBEELD
> > # owner: root
> > # group: secretariaat
> > # flags: -s-
> > user::rwx
> > group::rwx
> > group:medewerkers:r-x
> > mask::rwx
> > other::---
> > default:user::rwx
> > default:group::rwx
> > default:group:medewerkers:r-x
> > default:mask::rwx
> > default:other::---
> >
> > # file: ALGEMEEN
> > # owner: root
> > # group: secretariaat
> > # flags: -s-
> > user::rwx
> > group::rwx
> > group:medewerkers:r-x
> > mask::rwx
> > other::---
> > default:user::rwx
> > default:group::rwx
> > default:group:medewerkers:r-x
> > default:mask::rwx
> > default:other::---
> > ------
> >
> >
> >
> >
> >
> > --
> > Paul van der Vlis Linux systeembeheer Groningen
> > https://www.vandervlis.nl/
> > _______________________________________________
> > Gluster-users mailing list
> > Gluster-users@xxxxxxxxxxx <mailto:Gluster-users@xxxxxxxxxxx>
> <mailto:Gluster-users@xxxxxxxxxxx <mailto:Gluster-users@xxxxxxxxxxx>>
> > https://lists.gluster.org/mailman/listinfo/gluster-users
>
>
>
> --
> Paul van der Vlis Linux systeembeheer Groningen
> https://www.vandervlis.nl/
> _______________________________________________
> Gluster-users mailing list
> Gluster-users@xxxxxxxxxxx <mailto:Gluster-users@xxxxxxxxxxx>
> https://lists.gluster.org/mailman/listinfo/gluster-users
>
--
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
> Hi Paul,
>
> A few questions:
> Which version of gluster are you using?
On the server and some clients: glusterfs 4.1.2
On a new client: glusterfs 5.5
> Did this behaviour start recently? As in were the contents of that
> directory visible earlier?
This directory was normally used in the headoffice, and there is direct
access to the files without Glusterfs. So I don't know.
With regards,
Paul van der Vlis
> Regards,
> Nithya
>
>
> On Wed, 15 May 2019 at 18:55, Paul van der Vlis <paul@xxxxxxxxxxxxx
> <mailto:paul@xxxxxxxxxxxxx>> wrote:
>
> Hello Strahil,
>
> Thanks for your answer. I don't find the word "sharding" in the
> configfiles. There is not much shared data (24GB), and only 1 brick:
> ---
> root@xxx:/etc/glusterfs# gluster volume info DATA
>
> Volume Name: DATA
> Type: Distribute
> Volume ID: db53ece1-5def-4f7c-b59d-3a230824032a
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 1
> Transport-type: tcp
> Bricks:
> Brick1: xxx-vpn:/DATA
> Options Reconfigured:
> transport.address-family: inet
> nfs.disable: on
> ----
> (I have edited this a bit for privacy of my customer).
>
> I think they have used glusterfs because it can do ACLs.
>
> With regards,
> Paul van der Vlis
>
>
> Op 15-05-19 om 14:59 schreef Strahil Nikolov:
> > Most probably you use sharding , which splits the files into smaller
> > chunks so you can fit a 1TB file into gluster nodes with bricks of
> > smaller size.
> > So if you have 2 dispersed servers each having 500Gb brick-> without
> > sharding you won't be able to store files larger than the brick size -
> > no matter you have free space on the other server.
> >
> > When sharding is enabled - you will see on the brick the first
> shard as
> > a file and the rest is in a hidden folder called ".shards" (or
> something
> > like that).
> >
> > The benefit is also viewable when you need to do some maintenance on a
> > gluster node, as you will need to heal only the shards containing
> > modified by the customers' data.
> >
> > Best Regards,
> > Strahil Nikolov
> >
> >
> > В сряда, 15 май 2019 г., 7:31:39 ч. Гринуич-4, Paul van der Vlis
> > <paul@xxxxxxxxxxxxx <mailto:paul@xxxxxxxxxxxxx>> написа:
> >
> >
> > Hello,
> >
> > I am the new sysadmin of an organization what uses Glusterfs.
> > I did not set it up, and I don't know much about Glusterfs.
> >
> > What I do not understand is that I do not see all data in the mount.
> > Not as root, not as a normal user who has privileges.
> >
> > When I do "ls" in one of the subdirectories I don't see any data, but
> > this data exists at the server!
> >
> > In another subdirectory I see everything fine, the rights of the
> > directories and files inside are the same.
> >
> > I mount with something like:
> > /bin/mount -t glusterfs -o acl 10.8.0.1:/data /data
> > I see data in /data/VOORBEELD/, and I don't see any data in
> /data/ALGEMEEN/.
> >
> > I don't see something special in /etc/exports or in /etc/glusterfs on
> > the server.
> >
> > Is there maybe a mechanism in Glusterfs what can exclude data from
> > export? Or is there a way to debug this problem?
> >
> > With regards,
> > Paul van der Vlis
> >
> > ----
> > # file: VOORBEELD
> > # owner: root
> > # group: secretariaat
> > # flags: -s-
> > user::rwx
> > group::rwx
> > group:medewerkers:r-x
> > mask::rwx
> > other::---
> > default:user::rwx
> > default:group::rwx
> > default:group:medewerkers:r-x
> > default:mask::rwx
> > default:other::---
> >
> > # file: ALGEMEEN
> > # owner: root
> > # group: secretariaat
> > # flags: -s-
> > user::rwx
> > group::rwx
> > group:medewerkers:r-x
> > mask::rwx
> > other::---
> > default:user::rwx
> > default:group::rwx
> > default:group:medewerkers:r-x
> > default:mask::rwx
> > default:other::---
> > ------
> >
> >
> >
> >
> >
> > --
> > Paul van der Vlis Linux systeembeheer Groningen
> > https://www.vandervlis.nl/
> > _______________________________________________
> > Gluster-users mailing list
> > Gluster-users@xxxxxxxxxxx <mailto:Gluster-users@xxxxxxxxxxx>
> <mailto:Gluster-users@xxxxxxxxxxx <mailto:Gluster-users@xxxxxxxxxxx>>
> > https://lists.gluster.org/mailman/listinfo/gluster-users
>
>
>
> --
> Paul van der Vlis Linux systeembeheer Groningen
> https://www.vandervlis.nl/
> _______________________________________________
> Gluster-users mailing list
> Gluster-users@xxxxxxxxxxx <mailto:Gluster-users@xxxxxxxxxxx>
> https://lists.gluster.org/mailman/listinfo/gluster-users
>
--
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users