search for: hulsman

We've a fix in release-3.10 branch which is merged and should be available in the next 3.10 update. On Wed, Nov 8, 2017 at 4:58 PM, Mike Hulsman <mike.hulsman at proxy.nl> wrote: > Hi, > > This bug is hitting me hard on two different clients. > In RHGS 3.3 and on glusterfs 3.10.2 on Centos 7.4 > in once case I had 59 differences in a total of 203 bricks. > > I wrote a quick and dirty script to check all ports aga...

...int $NF}' | awk -F"." '{print $2}'` #echo Onfile: ${Onfile} #echo Daemon: ${Daemon} if [ "${Onfile}" = "${Daemon}" ]; then echo "OK For ${Brick}" else echo "!!! NOT OK For ${Brick}" fi done done Met vriendelijke groet, Mike Hulsman Proxy Managed Services B.V. | www.proxy.nl | Enterprise IT-Infra, Open Source and Cloud Technology Delftweg 128 3043 NB Rotterdam The Netherlands | +31 10 307 0965 From: "Jo Goossens" <jo.goossens at hosted-power.com> To: "Atin Mukherjee" <amukherj at redhat.co...

Hello Atin, ? ? I just read it and very happy you found the issue. We really hope this will be fixed in the next 3.10.7 version! ? ? PS: Wow nice all that c code and those "goto out" statements (not always considered clean but the best way often I think). Can remember the days I wrote kernel drivers myself in c :) ? ? Regards Jo Goossens ? ? ? -----Original message----- From:Atin

For what it's worth, I just updated some CentOS 7 servers from GlusterFS 3.12.1 to 3.12.4 and hit this bug. Did the patch make it into 3.12.4? I had to use Mike Hulsman's script to check the daemon port against the port in the volume's brick info, update the port, and restart glusterd on each node. Luckily I only have four servers! Hoping I don't have to do this every time I reboot! Regards, On Sat, Dec 2, 2017 at 5:23 PM Atin Mukherjee <amukherj...

...handy with you when this happened? On Sun, Jan 21, 2018 at 10:21 PM, Alan Orth <alan.orth at gmail.com> wrote: > For what it's worth, I just updated some CentOS 7 servers from GlusterFS > 3.12.1 to 3.12.4 and hit this bug. Did the patch make it into 3.12.4? I had > to use Mike Hulsman's script to check the daemon port against the port in > the volume's brick info, update the port, and restart glusterd on each > node. Luckily I only have four servers! Hoping I don't have to do this > every time I reboot! > > Regards, > > On Sat, Dec 2, 2017 at 5:2...

This patch builds a floppy image with contains HDT, so users of GRUB or GRUB4DOS can use HDT too, without installing Syslinux. When you compile Syslinux, this floppy image isn't build automatically. To build it, runthe following from the extracted Syslinux source: $ cd ./com32/hdt $ make hdt.img As suggested by Pierre-Alexandre Meyer, all extra files required for building the floppy

...happened? > > On Sun, Jan 21, 2018 at 10:21 PM, Alan Orth <alan.orth at gmail.com> wrote: > >> For what it's worth, I just updated some CentOS 7 servers from GlusterFS >> 3.12.1 to 3.12.4 and hit this bug. Did the patch make it into 3.12.4? I had >> to use Mike Hulsman's script to check the daemon port against the port in >> the volume's brick info, update the port, and restart glusterd on each >> node. Luckily I only have four servers! Hoping I don't have to do this >> every time I reboot! >> >> Regards, >> >&gt...

...is happened? On Sun, Jan 21, 2018 at 10:21 PM, Alan Orth <alan.orth at gmail.com <mailto:alan.orth at gmail.com> > wrote: For what it's worth, I just updated some CentOS 7 servers from GlusterFS 3.12.1 to 3.12.4 and hit this bug. Did the patch make it into 3.12.4? I had to use Mike Hulsman's script to check the daemon port against the port in the volume's brick info, update the port, and restart glusterd on each node. Luckily I only have four servers! Hoping I don't have to do this every time I reboot! ?Regards, On Sat, Dec 2, 2017 at 5:23 PM Atin Mukherjee <amukherj...

...> On Sun, Jan 21, 2018 at 10:21 PM, Alan Orth <alan.orth at gmail.com> wrote: >> >>> For what it's worth, I just updated some CentOS 7 servers from GlusterFS >>> 3.12.1 to 3.12.4 and hit this bug. Did the patch make it into 3.12.4? I had >>> to use Mike Hulsman's script to check the daemon port against the port in >>> the volume's brick info, update the port, and restart glusterd on each >>> node. Luckily I only have four servers! Hoping I don't have to do this >>> every time I reboot! >>> >>> Regar...

...ou when this happened? > > On Sun, Jan 21, 2018 at 10:21 PM, Alan Orth <alan.orth at gmail.com> wrote: > > For what it's worth, I just updated some CentOS 7 servers from GlusterFS > 3.12.1 to 3.12.4 and hit this bug. Did the patch make it into 3.12.4? I had > to use Mike Hulsman's script to check the daemon port against the port in > the volume's brick info, update the port, and restart glusterd on each > node. Luckily I only have four servers! Hoping I don't have to do this > every time I reboot! > > Regards, > > On Sat, Dec 2, 2017 at 5:2...

On Sat, 2 Dec 2017 at 19:29, Jo Goossens <jo.goossens at hosted-power.com> wrote: > Hello Atin, > > > > > > Could you confirm this should have been fixed in 3.10.8? If so we'll test > it for sure! > Fix should be part of 3.10.8 which is awaiting release announcement. > > Regards > > Jo > > > > > > > -----Original

We (finally) figured out the root cause, Jo! Patch https://review.gluster.org/#/c/18579 posted upstream for review. On Thu, Sep 21, 2017 at 2:08 PM, Jo Goossens <jo.goossens at hosted-power.com> wrote: > Hi, > > > > > > We use glusterfs 3.10.5 on Debian 9. > > > > When we stop or restart the service, e.g.: service glusterfs-server restart > > >