search for: remolina

...> Change gluster client and brick logs back to info. Let me know if I need to redo any tests, change any steps or provide more logs I may have missed. Diego On Fri, Jun 2, 2017 at 8:19 PM, Raghavendra Talur <rtalur at redhat.com> wrote: > > > On 03-Jun-2017 3:27 AM, "Diego Remolina" <dijuremo at gmail.com> wrote: > > Hi everyone, > > Is there anything else we could do to check on this problem and try to > fix it? The issue is definitively related to either the samba vfs > gluster plugin or gluster itself. I am not sure how to pin it down > futh...

...t Managers writeable = yes guest ok = no create mask = 660 directory mask = 770 This test will determine if the issue is the samba vfs gluster plugin or if it is the fact that the file is stored in the gluster volume. Any other thoughts? Diego On Wed, May 31, 2017 at 12:59 PM, Diego Remolina <dijuremo at gmail.com> wrote: > The vfs gluster plugin for samba is linked against libglusterfs.so.0 > which is provided by glusterfs-libs-3.10.2-1.el7.x86_64, please see > below. > > # ldd /usr/lib64/samba/vfs/glusterfs.so | grep glus > libglusterfs.so.0 => /lib6...

Hi, I believe that the BUG 2346 which was resolved in samba 3.0.14 has come back in the 3.0.23 series. Here is what I have noticed on two separate configurations. The samba packages were built on each machine using rpmbuild with the SRPMS provided for Fedora in the samba web site. Configuration 1. Two machines running with RHEL4, samba 3.0.23b-1, drbd-0.7.21 protocol C. Kernel:

On 03-Jun-2017 3:27 AM, "Diego Remolina" <dijuremo at gmail.com> wrote: Hi everyone, Is there anything else we could do to check on this problem and try to fix it? The issue is definitively related to either the samba vfs gluster plugin or gluster itself. I am not sure how to pin it down futher. I don't think it is vfs...

Did the logs provide any hints as to what the issue may be? Diego On Sat, Jun 3, 2017 at 12:16 PM, Diego Remolina <dijuremo at gmail.com> wrote: > Thanks for taking the time to look into this. Since we needed downtime > due to the gluster update, we also updated the OS, including samba. We > went from 4.2.x to 4.4.4 and many other packages for CentOS were > updated as well. OS and samba updat...

Hi Diego, Just to clarify, so did you do an offline upgrade with an existing cluster (3.6.x => 3.10.x)? Thanks. On Fri, Aug 25, 2017 at 8:42 PM, Diego Remolina <dijuremo at gmail.com> wrote: > I was never able to go from 3.6.x to 3.7.x without downtime. Then > 3.7.x did not work well for me, so I stuck with 3.6.x until recently. > I went from 3.6.x to 3.10.x but downtime was scheduled. > > Diego > > On Fri, Aug 25, 2017 at 8:25...

...as a witness. HTH, Diego On Fri, Aug 25, 2017 at 8:56 AM, Yong Tseng <yongtw123 at gmail.com> wrote: > Hi Diego, > > Just to clarify, so did you do an offline upgrade with an existing cluster > (3.6.x => 3.10.x)? > Thanks. > > On Fri, Aug 25, 2017 at 8:42 PM, Diego Remolina <dijuremo at gmail.com> wrote: >> >> I was never able to go from 3.6.x to 3.7.x without downtime. Then >> 3.7.x did not work well for me, so I stuck with 3.6.x until recently. >> I went from 3.6.x to 3.10.x but downtime was scheduled. >> >> Diego >> &...

...-3.10.3-1.el7.x86_64 glusterfs-api-3.10.3-1.el7.x86_64 centos-release-gluster310-1.0-1.el7.centos.noarch glusterfs-fuse-3.10.3-1.el7.x86_64 samba-vfs-glusterfs-4.4.4-14.el7_3.x86_64 glusterfs-libs-3.10.3-1.el7.x86_64 glusterfs-cli-3.10.3-1.el7.x86_64 Diego On Mon, Jun 26, 2017 at 10:14 AM, Diego Remolina <dijuremo at gmail.com> wrote: > Hi, > > I was wondering if you have had a chance to review the logs and if you > can tell me know if more information is needed. > > Diego > > On Mon, Jun 12, 2017 at 8:20 AM, Diego Remolina <dijuremo at gmail.com> wrote: >>...

On Tue, Jul 11, 2017 at 5:12 PM, Diego Remolina <dijuremo at gmail.com> wrote: > > > > You should first upgrade servers and then clients. New servers can > > understand old clients, but it is not easy for old servers to understand > new > > clients in case it started doing something new. > > But isn't...

...t it can be upgraded but with a downtime, which means that there are no clients writing to this gluster volume, as the volume is stopped. But post a upgrade we will still have the data on the gluster volume that we had before the upgrade(but with downtime). - Hemant On 9/13/17 2:33 PM, Diego Remolina wrote: > Nope, not gonna work... I could never go even from 3.6. to 3.7 without > downtime cause of the settings change, see: > > http://lists.gluster.org/pipermail/gluster-users.old/2015-September/023470.html > > Even when changing options in the older 3.6.x I had installed, my n...

...rade. However I added brick, turned volume to replica 3 with arbiter and got very strange issue I will mail to this list in a moment... Thanks. -ps On Tue, Jul 11, 2017 at 1:55 PM, Pranith Kumar Karampuri <pkarampu at redhat.com> wrote: > > > On Tue, Jul 11, 2017 at 5:12 PM, Diego Remolina <dijuremo at gmail.com> wrote: >> >> > >> > You should first upgrade servers and then clients. New servers can >> > understand old clients, but it is not easy for old servers to understand >> > new >> > clients in case it started doing someth...

...es-template.qcow2 -rw-------. 2 root root 3792371712 May 9 16:15 kworker01.qcow2 -rw-------. 2 root root 3792371712 May 10 11:20 kworker02.qcow2 [root at glusterp2 gv0]# So some files have re-synced but not the kworker machines network activity has stopped. On 10 May 2018 at 12:05, Diego Remolina <dijuremo at gmail.com> wrote: > Show us output from: gluster v status > > It should be easy to fix. Stop gluster daemon on that node, mount the > brick, start gluster daemon again. > > Check: gluster v status > > Does it show the brick up? > > HTH, > > Di...

Gandalf, SIGKILL (killall -9 glusterfsd) did not stop I/O after few minutes. SIGTERM on the other hand causes crash, but this time it is not read-only remount, but around 10 IOPS tops and 2 IOPS on average. -ps On Fri, Sep 8, 2017 at 1:56 PM, Diego Remolina <dijuremo at gmail.com> wrote: > I currently only have a Windows 2012 R2 server VM in testing on top of > the gluster storage, so I will have to take some time to provision a > couple Linux VMs with both ext4 and XFS to see what happens on those. > > The Windows server VM is OK...

I've been spending some time backporting Samba 4.0.3 from Fedora 19 to RHEL 6, partly as proof of concept, partly to make it available to others. I've published my work at: https://github.com/nkadel/samba4repo/ The key RPM building tools are at: https://github.com/nkadel/samba-4.0.3-srpm/ And there are dependencies listed for libtalloc, libtevent,

...wd entries and not through kerberos. This is my understanding so please correct me if I am wrong. Is there a good document that explains in detail all the configure options for samba? I have not been able to find one. Thanks for your help, Diego ---------------------------------- Diego Julian Remolina System Administrator School of Mathematics Georgia Institute of Technology ----------------------------------

...3792371712 May 9 16:15 kworker01.qcow2 > -rw-------. 2 root root 3792371712 May 10 11:20 kworker02.qcow2 > [root at glusterp2 gv0]# > > So some files have re-synced but not the kworker machines network > activity has stopped. > > > > On 10 May 2018 at 12:05, Diego Remolina <dijuremo at gmail.com> wrote: > >> Show us output from: gluster v status >> >> It should be easy to fix. Stop gluster daemon on that node, mount the >> brick, start gluster daemon again. >> >> Check: gluster v status >> >> Does it show the b...

I'm receiving the errors listed below. It also seems unable to map the root user uid 0 with this filter. That's not that big of a deal. Wbinfo -u and -g return output but getent passwd does not. This is Ubuntu 7 using debian packages. [2007/06/28 13:27:59, 5] lib/username.c:Get_Pwnam_alloc(131) Finding user DOMAIN\chapman [2007/06/28 13:27:59, 5]

....qcow2 >> -rw-------. 2 root root 3792371712 May 10 11:20 kworker02.qcow2 >> [root at glusterp2 gv0]# >> >> So some files have re-synced but not the kworker machines network >> activity has stopped. >> >> >> >> On 10 May 2018 at 12:05, Diego Remolina <dijuremo at gmail.com> wrote: >> >>> Show us output from: gluster v status >>> >>> It should be easy to fix. Stop gluster daemon on that node, mount the >>> brick, start gluster daemon again. >>> >>> Check: gluster v status >>...

...make and make install. We really need to use smbwrappers to make our server more secure. I tried to change the option from -fPIC to -KPIC on the configure.in file but the result was that things would not compile. Thanks for any help or clues you may give me as to how to fix this problem. Diego Remolina System Administrator School of Mathematics Georgia Institute of Technology -------------- next part -------------- HTML attachment scrubbed and removed

> > You should first upgrade servers and then clients. New servers can > understand old clients, but it is not easy for old servers to understand new > clients in case it started doing something new. But isn't that the reason op-version exists? So that regardless of client/server mix, nobody tries to do "new" things above the current op-version? He is not changing mayor