search for: nfs01

Dear mail list, I have a Ubuntu server which I upgraded from 11.10 to current LTS 14.4 running kernel: Linux bgo-nfs01 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux. Filename: pool/main/s/samba/samba_4.1.6+dfsg-1ubuntu2_amd64.deb At the same time the purpose was changed from NFS with Samba for limited amount of users to NFS and SAMBA with file shares served to som...

...hat's alot of CPU usage >> in top. Seems bottle-necked via a single execution core somewhere trying >> to facilitate read / writes to the other bricks. >> >> Writes to the gluster FS from within one of the gluster participating >> bricks: >> >> [root at nfs01 n]# dd if=/dev/zero of=./some-file.bin >> >> 393505+0 records in >> 393505+0 records out >> 201474560 bytes (201 MB) copied, 50.034 s, 4.0 MB/s > > That's not really a fare comparison as you don't specify a blocksize. > What does > > dd if=/dev/zero...

...allow the secondary node to function then replicate what changed to the first (primary) when it's back online? Or should I just go for a third node to allow for this? Also, how safe is it to set the following to none? cluster.quorum-type: auto cluster.server-quorum-type: server [root at nfs01 /]# gluster volume start gv01 volume start: gv01: failed: Quorum not met. Volume operation not allowed. [root at nfs01 /]# [root at nfs01 /]# gluster volume status Status of volume: gv01 Gluster process TCP Port RDMA Port Online Pid ---------------------------------...

On 09/02/15 14:56, sk at green.no wrote: > Dear mail list, > > I have a Ubuntu server which I upgraded from 11.10 to current LTS 14.4 > running kernel: Linux bgo-nfs01 3.13.0-44-generic #73-Ubuntu SMP Tue Dec > 16 00:22:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux. > Filename: pool/main/s/samba/samba_4.1.6+dfsg-1ubuntu2_amd64.deb > > At the same time the purpose was changed from NFS with Samba for limited > amount of users to NFS and SAMBA with file...

...eplicate what > changed to the first (primary) when it's back online? Or should I just > go for a third node to allow for this? > > Also, how safe is it to set the following to none? > > cluster.quorum-type: auto > cluster.server-quorum-type: server > > > [root at nfs01 /]# gluster volume start gv01 > volume start: gv01: failed: Quorum not met. Volume operation not allowed. > [root at nfs01 /]# > > > [root at nfs01 /]# gluster volume status > Status of volume: gv01 > Gluster process TCP Port RDMA Port Online >...

...ed to the first (primary) when it's back online?? Or should I just > go for a third node to allow for this? > > Also, how safe is it to set the following to none? > > cluster.quorum-type: auto > cluster.server-quorum-type: server > > > [root at nfs01 /]# gluster volume start gv01 > volume start: gv01: failed: Quorum not met. Volume operation not > allowed. > [root at nfs01 /]# > > > [root at nfs01 /]# gluster volume status > Status of volume: gv01 > Gluster process? ? ? ? ? ? ? ? ? ? ? ? ? ? ?TC...

Hey All, Appears I solved this one and NFS mounts now work on all my clients. No issues since fixing it a few hours back. RESOLUTION Auditd is to blame for the trouble. Noticed this in the logs on 2 of the 3 NFS servers (nfs01, nfs02, nfs03): type=AVC msg=audit(1526965320.850:4094): avc: denied { write } for pid=8714 comm="ganesha.nfsd" name="nfs_0" dev="dm-0" ino=201547689 scontext=system_u:system_r:ganesha_t:s0 tcontext=system_u:object_r:krb5_host_rcache_t:s0 tclass=file type=SYSCALL...

...K wrote: Hey Guy's, Returning to this topic, after disabling the the quorum: cluster.quorum-type: none cluster.server-quorum-type: none I've ran into a number of gluster errors (see below). I'm using gluster as the backend for my NFS storage. I have gluster running on two nodes, nfs01 and nfs02. It's mounted on /n on each host. The path /n is in turn shared out by NFS Ganesha. It's a two node setup with quorum disabled as noted below: [root at nfs02 ganesha]# mount|grep gv01 nfs02:/gv01 on /n type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissio...

...ack online? Or should I >> just >> go for a third node to allow for this? >> >> Also, how safe is it to set the following to none? >> >> cluster.quorum-type: auto >> cluster.server-quorum-type: server >> >> >> [root at nfs01 /]# gluster volume start gv01 >> volume start: gv01: failed: Quorum not met. Volume operation not >> allowed. >> [root at nfs01 /]# >> >> >> [root at nfs01 /]# gluster volume status >> Status of volume: gv01 >> Gluster process...

...on my own setup either. For the writes it's doing, that's alot of CPU usage in top. Seems bottle-necked via a single execution core somewhere trying to facilitate read / writes to the other bricks. Writes to the gluster FS from within one of the gluster participating bricks: [root at nfs01 n]# dd if=/dev/zero of=./some-file.bin 393505+0 records in 393505+0 records out 201474560 bytes (201 MB) copied, 50.034 s, 4.0 MB/s [root at nfs01 n]# Top results (10 second average)won't go over 32%: top - 00:49:38 up 21:39, 2 users, load average: 0.42, 0.24, 0.19 Tasks: 164 total, 1 r...

...e writes it's doing, that's alot of CPU usage > in top. Seems bottle-necked via a single execution core somewhere trying > to facilitate read / writes to the other bricks. > > Writes to the gluster FS from within one of the gluster participating > bricks: > > [root at nfs01 n]# dd if=/dev/zero of=./some-file.bin > > 393505+0 records in > 393505+0 records out > 201474560 bytes (201 MB) copied, 50.034 s, 4.0 MB/s That's not really a fare comparison as you don't specify a blocksize. What does dd if=/dev/zero of=./some-file.bin bs=1M count=1000 ofla...

...>>> in top. Seems bottle-necked via a single execution core somewhere trying >>> to facilitate read / writes to the other bricks. >>> >>> Writes to the gluster FS from within one of the gluster participating >>> bricks: >>> >>> [root at nfs01 n]# dd if=/dev/zero of=./some-file.bin >>> >>> 393505+0 records in >>> 393505+0 records out >>> 201474560 bytes (201 MB) copied, 50.034 s, 4.0 MB/s >>> >> >> That's not really a fare comparison as you don't specify a blocksize. >&g...

Hi, As I posted in my previous emails - glusterfs can never match NFS (especially async one) performance of small files/latency. That's given by the design. Nothing you can do about it. Ondrej -----Original Message----- From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Rik Theys Sent: Monday, March 19, 2018 10:38 AM To: gluster-users at

...information if required. Thanks in advance. ===> 'gluster volume status' ran on non-upgraded peers Status of volume: gsnfs Gluster process Port Online Pid ------------------------------------------------------------------------------ Brick gs-nfs01:/ftpdata 49154 Y 2931 Brick gs-nfs02:/ftpdata 49152 Y 29875 Brick gs-nfs03:/ftpdata 49153 Y 6987 Brick gs-nfs04:/ftpdata 49153 Y 24768 Self-heal Daemon...

...n advance. > > ===> 'gluster volume status' ran on non-upgraded peers > > Status of volume: gsnfs > Gluster process Port Online Pid > ------------------------------------------------------------------------------ > Brick gs-nfs01:/ftpdata 49154 Y 2931 > Brick gs-nfs02:/ftpdata 49152 Y > 29875 > Brick gs-nfs03:/ftpdata 49153 Y 6987 > Brick gs-nfs04:/ftpdata 49153 Y &g...

...t;> > Status of volume: gsnfs > >> > Gluster process Port Online > >> > Pid > >> > > >> > ------------------------------------------------------------ > ------------------ > >> > Brick gs-nfs01:/ftpdata 49154 Y > >> > 2931 > >> > Brick gs-nfs02:/ftpdata 49152 Y > >> > 29875 > >> > Brick gs-nfs03:/ftpdata 49153 Y > >> > 6987 >...

...> >> To >> >> idmap config GREENREEFERS:backend = rid >> idmap config GREENREEFERS:range=10000-99999 > I did the change, restarted samba and it didn't do any changes. OK, make the [global] part of your smb.conf look like this: [global] netbios name = bgo-nfs01 workgroup = GREENREEFERS security = ADS realm = GREENREEFERS.NO dedicated keytab file = /etc/krb5.keytab kerberos method = secrets and keytab server string = %h server winbind enum users = yes winbind enum groups = yes...

...; Gluster process Port >> >> > Online >> >> > Pid >> >> > >> >> > >> >> > ------------------------------------------------------------------------------ >> >> > Brick gs-nfs01:/ftpdata 49154 Y >> >> > 2931 >> >> > Brick gs-nfs02:/ftpdata 49152 Y >> >> > 29875 >> >> > Brick gs-nfs03:/ftpdata 49153 Y >> >...

samba-bounces at lists.samba.org wrote on 09.02.2015 20:52:43: > OK, make the [global] part of your smb.conf look like this: > > [global] > netbios name = bgo-nfs01 > workgroup = GREENREEFERS > security = ADS > realm = GREENREEFERS.NO > dedicated keytab file = /etc/krb5.keytab > kerberos method = secrets and keytab > server string = %h server > winbind enum users = yes >...

On 12/02/15 09:51, sk at green.no wrote: > samba-bounces at lists.samba.org wrote on 09.02.2015 20:52:43: > >> OK, make the [global] part of your smb.conf look like this: >> >> [global] >> netbios name = bgo-nfs01 >> workgroup = GREENREEFERS >> security = ADS >> realm = GREENREEFERS.NO >> dedicated keytab file = /etc/krb5.keytab >> kerberos method = secrets and keytab >> server string = %h server >>...