search for: default_permissions

Hello, libguestfs has a guestmount command that basically gives access via fuse to filesystem images. It also takes options for fuse. When -o default_permissions is not given, the mounting user should have full access to everything (he will have access to the image anyway). Of course, it should also be possible to give -o default_permissions to have the kernel check the permissions, which could be useful for some use cases. Now the strange thing is tha...

On 24/09/2020 12:47, Christian Naumer via samba wrote: > I am using it on Fedora with Volume Definition looking like this: and I use this: <volume fstype="cifs" ??????? server="CIFS_SERVER_FQDN" ??????? path="linprofiles" ??????? mountpoint="/mnt/%(USER)" options="username=%(USER),uid=%(USERUID),gid=%(USERGID),domain=%(DOMAIN_NAME)"

...on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw,size=8g) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/xvda1 on /boot type reiserfs (rw,acl,user_xattr) securityfs on /sys/kernel/security type securityfs (rw) glusterfs on /data type fuse (rw,max_read=1048576,allow_other,default_permissions) Waiting for your help ,thanks a lot 2009-03-18 eagleeyes -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20090318/4f817826/attachment.html>

...o servers 192.168.104.151 and 192.168.104.152. Both are running GlusterD and both offer one of the bricks for the volume. Both mount also the volume locally. The working /etc/fstab entry on 192.168.104.151 is: 192.168.104.151:/gluster-data /var/gluster/data glusterfs auto,_netdev,rw,allow_other,default_permissions,max_read=131072 0 0 Likewise, the working /etc/fstab entry on 192.168.104.152 is: 192.168.104.152:/gluster-data /var/gluster/data glusterfs auto,_netdev,rw,allow_other,default_permissions,max_read=131072 0 0 If you don't have the "auto,_netdev" options on the mount, then you can m...

...fs), the same version and op-version as the hosts. - Gluster server and client version: 3.12.2 (also found on 3.12.1, unsure about previous versions) running on CentOS 7. Examples: mount: 192.168.0.151:/gluster_vol on /var/lib/mountedgluster type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072) root at gluster-client:/var/lib/mountedgluster # ls -la total 0 (note no . or .. directories) root at gluster-client:/var/lib/mountedgluster # touch test root at gluster-client:/var/lib/mountedgluster # ls -la total 0 -rw-r--r--. 1 root root 0 Nov 6 10:10 test...

...in mount () from /lib/libc.so.6 (gdb) bt #0 0x00007f7768005e2a in mount () from /lib/libc.so.6 #1 0x00007f77668b2af4 in fuse_mount_sys (mountpoint=0x1020140 "/mnt/lan/nas", fsname=0x101e260 "/etc/glusterfs/nas-client.vol", mnt_param=0x7f77668b3558 "allow_other,default_permissions,max_read=131072") at ../../../../contrib/fuse-lib/mount.c:538 #2 gf_fuse_mount (mountpoint=0x1020140 "/mnt/lan/nas", fsname=0x101e260 "/etc/glusterfs/nas-client.vol", mnt_param=0x7f77668b3558 "allow_other,default_permissions,max_read=131072") at...

...ster v set <vol-name> performance.parallel-readdir on (Note : readdir > should be on) > This is what i'm getting with suggested parameters. I'm running "fio" from a mounted gluster client: 172.16.0.12:/gv0 on /mnt2 type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072) # fio --ioengine=libaio --filename=fio.test --size=256M --direct=1 --rw=randrw --refill_buffers --norandommap --bs=8k --rwmixread=70 --iodepth=16 --numjobs=16 --runtime=60 --group_reporting --name=fio-test fio-test: (g=0): rw=r...

...samba-3.0.33-3.29.el5_7.4.x86_64 samba-common-3.0.33-3.29.el5_7.4.x86_64 2 servers, one provides samba-shares and one I use as client. Samba-Server (HOST2): FuseFS: hadoop-fuse-dfs#dfs://HOSTNAME:9000 /123/hdfs fuse usetrash,rw 0 0 mount: fuse on /123/hdfs type fuse (rw,nosuid,nodev,allow_other,default_permissions) the mount /123 is accessible over ssh, cp, rsnyc from any host. Now I was using NFS for populating, but the performance was not as I expected. So I switched to samba and get real good results for reading. Cifs-Client(HOST1): mount -t cifs -o username=BLUBB,domain=hdfs,rw,uid=104 //lHOST2/hdfs /t...

...sts. > - Gluster server and client version: 3.12.2 (also found on 3.12.1, unsure > about previous versions) running on CentOS 7. > > > Examples: > > > mount: > 192.168.0.151:/gluster_vol on /var/lib/mountedgluster type fuse.glusterfs > (rw,relatime,user_id=0,group_id=0,default_permissions, > allow_other,max_read=131072) > > root at gluster-client:/var/lib/mountedgluster # ls -la > total 0 > > (note no . or .. directories) > > root at gluster-client:/var/lib/mountedgluster # touch test > root at gluster-client:/var/lib/mountedgluster # ls -la > total...

...brick > Options Reconfigured: > nfs.disable: on *Client *is also gluster 3.12.6, Centos 7.3 virtual machine, *FUSE mount* > root at centos7u3-nogdesktop2 ~ $ mount |grep gluster > gluster-host.ibnet:/r2vol on /mnt/gluster/r2 type fuse.glusterfs > (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072) > gluster-host.ibnet:/r3vol on /mnt/gluster/r3 type fuse.glusterfs > (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072) *The problem *is that there is a significant performance loss with smaller block sizes. For example: *4K blo...

...gt; unsure about previous versions) running on CentOS 7. >>> >>> >>> Examples: >>> >>> >>> mount: >>> 192.168.0.151:/gluster_vol on /var/lib/mountedgluster type >>> fuse.glusterfs (rw,relatime,user_id=0,group_i >>> d=0,default_permissions,allow_other,max_read=131072) >>> >>> root at gluster-client:/var/lib/mountedgluster # ls -la >>> total 0 >>> >>> (note no . or .. directories) >>> >>> root at gluster-client:/var/lib/mountedgluster # touch test >>> root at gl...

...ostics.client-log-level: INFO diagnostics.brick-log-level: INFO Mount points for the bricks: /dev/sdb on /data/brick2 type xfs (rw,noatime,nobarrier) /dev/sda on /data/brick1 type xfs (rw,noatime,nobarrier) Mount point on the client: 10.xx.xx.xx:/hpcscratch on /scratch type fuse.glusterfs (rw,default_permissions,allow_other,max_read=131072) My question is what are some of the possibilities for the root cause of this issue and what is the recommended way of recovering from it? Let me know if you need any more information. -- Mike Jarsulic Sr. HPC Administrator Center for Research Informatics | Universit...

Hi Gluster experts, I'm new to glusterfs and I have encountered a problem about list directory of glusters 3.3. I have a volume configuration of 3(distribute) * 2(replica). When write file on the glusterfs client mount directory some of the files can't be listed through ls command but the file exists. Some times the ls command hangs. Any one know what's the problem is? Thank you

...oot root 0 Nov 6 10:10 test The mount entry looks like: root at int-kube-01:~ # mount | grep iss3dev-static 10.51.70.151:/dev_static on /var/lib/kubelet/pods/434cba8e-bf87-11e7-8389-1aa903709357/volumes/kubernetes.io~glusterfs/iss3dev-static type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171109/de6d59f4/attachment.html>

An HTML attachment was scrubbed... URL: http://zresearch.com/pipermail/gluster-users/attachments/20081201/151a90cd/attachment.htm

...> nfs.disable: on > > > > *Client *is also gluster 3.12.6, Centos 7.3 virtual machine, *FUSE mount* > >> root at centos7u3-nogdesktop2 ~ $ mount |grep gluster >> gluster-host.ibnet:/r2vol on /mnt/gluster/r2 type fuse.glusterfs >> (rw,relatime,user_id=0,group_id=0,default_permissions, >> allow_other,max_read=131072) >> gluster-host.ibnet:/r3vol on /mnt/gluster/r3 type fuse.glusterfs >> (rw,relatime,user_id=0,group_id=0,default_permissions, >> allow_other,max_read=131072) > > > > *The problem *is that there is a significant performance loss wi...

...3.12.2 (also found on 3.12.1, unsure >> about previous versions) running on CentOS 7. >> >> >> Examples: >> >> >> mount: >> 192.168.0.151:/gluster_vol on /var/lib/mountedgluster type >> fuse.glusterfs (rw,relatime,user_id=0,group_i >> d=0,default_permissions,allow_other,max_read=131072) >> >> root at gluster-client:/var/lib/mountedgluster # ls -la >> total 0 >> >> (note no . or .. directories) >> >> root at gluster-client:/var/lib/mountedgluster # touch test >> root at gluster-client:/var/lib/mountedglu...

...ormance.parallel-readdir on (Note : readdir >> should be on) >> > > This is what i'm getting with suggested parameters. > I'm running "fio" from a mounted gluster client: > 172.16.0.12:/gv0 on /mnt2 type fuse.glusterfs > (rw,relatime,user_id=0,group_id=0,default_permissions, > allow_other,max_read=131072) > > > > # fio --ioengine=libaio --filename=fio.test --size=256M > --direct=1 --rw=randrw --refill_buffers --norandommap > --bs=8k --rwmixread=70 --iodepth=16 --numjobs=16 > --runtime=60 --group_reporting...

...t;> >> *Client *is also gluster 3.12.6, Centos 7.3 virtual machine, *FUSE mount* >> >> >>> root at centos7u3-nogdesktop2 ~ $ mount |grep gluster >>> gluster-host.ibnet:/r2vol on /mnt/gluster/r2 type fuse.glusterfs >>> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_ >>> other,max_read=131072) >>> gluster-host.ibnet:/r3vol on /mnt/gluster/r3 type fuse.glusterfs >>> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_ >>> other,max_read=131072) >> >> >> >> *The problem *is that there is a...

...This time, it is found. $ ls -l /home/RESEARCH/user.x/some_path/idtracker.log -rw-r--r-- 1 user.x group_x 1185 Jun 5 10:05 /home/RESEARCH/user.x/some_path/idtracker.log The glusterfs filesystem is mounted like this storage:/tank on /nfs/tank type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072) At the moment, cluster.readdir-optimize was on, cluster.lookup-optimize was on and cluster.lookup-unhashed was off. Now I've changed those 3 options to check if the problem still appears. Current configuration: $ sudo gluster volume info tank Volume Name: tank...