Re: [Gluster-users] untrusted users

2019-10-21 Thread Pankaj Kumar
Hi Jim Thanks a lot for your detailed response. Some clarifications: >> If they have no sudo, they can't mount. Use a centralized authentication system like freeipa or IdM. Every user should have their own userid that's unique. No exceptions. << Every user has a user id. And they also have sudo

Re: [Gluster-users] untrusted users

2019-10-21 Thread Jim Kinney
Shell access to untrusted users. I would fight that tooth and nail as a sysadmin. User that are untrusted get accounts deactivated. If they have no sudo, they can't mount. Make mounts for them in fstab. Set ownership and groups on mount points so each user is restricted to their folder only.

[Gluster-users] untrusted users

2019-10-21 Thread pankaj kumar
We are attaching a gluster storage to our cluster. We give shell access to our cluster to untrusted users. Each user has a folder in gluster. The problem is that the users could get to mount as any user id and then access the other users files as their own. Is there a way to authenticate a user

Re: [Gluster-users] FUSE Client Crashes On Shared File

2019-10-21 Thread Timothy Orme
Some further bits of info on this. I've found a lot of similar issues related to linking, but I don't seem to have any of those same issues. I've checked the gfids on all 3 of the replicas and they are the same, as are all extended attributes. I did notice that the gfid is present in the

[Gluster-users] FUSE Client Crashes On Shared File

2019-10-21 Thread Timothy Orme
Hello, I'm running gluster 6.5 on Amazon Linux 2 (CentOS 7 variant). I have a distributed-replicated cluster running, with sharding enabled for files over 512 MB. I tried issuing an `rm` for a large number of files, and seem to be consistently getting the client to crash on a specific file

Re: [Gluster-users] Adding arbiter on a large existing replica 2 set

2019-10-21 Thread Thorgeir Marthinussen
Hi, The new cluster is set up with two physical servers with HDDs and a VM backed by an all-flash stretched vSAN. The old cluster will be set up the same way. The main volume that I'm concerned about usually takes about 20-30 minutes to finish the self-heal, the network is 10Gbps. Best

Re: [Gluster-users] Announcing Gluster release 5.10

2019-10-21 Thread Hu Bert
Hi Shwetha, thx for your efforts, now i see the amd64 packages - i need those and not arm64 ;-) Now i noticed something new: the 5.9 folder now contains the 5.10 packages - see: https://download.gluster.org/pub/gluster/glusterfs/5/5.9/Debian/stretch/amd64/apt/pool/main/g/glusterfs/ So it seems

Re: [Gluster-users] Announcing Gluster release 5.10

2019-10-21 Thread Shwetha Acharya
Hu Bert, Find my reply inline. Regards, Shwetha On Mon, Oct 21, 2019 at 1:22 PM Hu Bert wrote: > Hi Shwetha, > > thx, now there are the 5.10 packages. But maybe I should've been more > precise: > > https://download.gluster.org/pub/gluster/glusterfs/5/LATEST/Debian/stretch/ > -> only arm64

[Gluster-users] Invitation: Gluster community meeting APAC @ Tue Oct 22, 2019 11:30am - 12:20pm (IST) (gluster-users@gluster.org)

2019-10-21 Thread hgowtham
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20191022T06Z DTEND:20191022T065000Z DTSTAMP:20191021T092844Z ORGANIZER;CN=hgowt...@redhat.com:mailto:hgowt...@redhat.com

Re: [Gluster-users] Announcing Gluster release 5.10

2019-10-21 Thread Hu Bert
Hi Shwetha, thx, now there are the 5.10 packages. But maybe I should've been more precise: https://download.gluster.org/pub/gluster/glusterfs/5/LATEST/Debian/stretch/ -> only arm64 available - where is amd64? For 5.9 there's also no amd64 anymore (but has been at least back in August). 5.8

Re: [Gluster-users] Announcing Gluster release 5.10

2019-10-21 Thread Shwetha Acharya
Hi Hu Bert, Thanks for informing about the issue. Now, you can find correct packages at https://download.gluster.org/pub/gluster/glusterfs/5/LATEST/Debian/stretch/arm64/apt/pool/main/g/glusterfs/ Regards, Shwetha On Mon, Oct 21, 2019 at 10:53 AM Hu Bert wrote: > Good morning, > > i just