search for: bneit

...ut not by much if you are > already used to bond setups. I haven't noticed any bugs or issues > using teaming. > > */David Gossage/*/* > */ > //*Carousel Checks Inc.| System Administrator* > *Office*708.613.2284 > > On Sat, Jun 17, 2017 at 2:59 PM, wk <wkmail at bneit.com > <mailto:wkmail at bneit.com>> wrote: > > I'm looking at tuning up a new site and the bonding issue came up > > A google search reveals that the gluster docs (and Lindsay) > recommend balance-alb bonding. > > However, "team"ing ca...

I'm looking at tuning up a new site and the bonding issue came up A google search reveals that the gluster docs (and Lindsay) recommend balance-alb bonding. However, "team"ing came up which I wasn't familiar with. Its already in RH6/7 and Ubuntu and their Github page implies its stable. The libteam.org people seem to feel their solution is more lightweight and it seems easy

...onding. Teaming may be slightly easier to manage, but not by much if you are already used to bond setups. I haven't noticed any bugs or issues using teaming. *David Gossage* *Carousel Checks Inc. | System Administrator* *Office* 708.613.2284 On Sat, Jun 17, 2017 at 2:59 PM, wk <wkmail at bneit.com> wrote: > I'm looking at tuning up a new site and the bonding issue came up > > A google search reveals that the gluster docs (and Lindsay) recommend > balance-alb bonding. > > However, "team"ing came up which I wasn't familiar with. Its already in > R...

Interesting problem... Did you considered an insider job?( comes to mind http://verelox.com <https://t.co/dt1c78VRxA> recent troubles) On Mon, Aug 7, 2017 at 3:30 AM, W Kern <wkmail at bneit.com> wrote: > > > On 8/6/2017 4:57 PM, lemonnierk at ulrar.net wrote: > > > Gluster already uses a vlan, the problem is that there is no easy way > that I know of to tell gluster not to listen on an interface, and I > can't not have a public IP on the server. I reall...

On 8/23/2017 10:44 PM, Pavel Szalbot wrote: > Hi, > > On Thu, Aug 24, 2017 at 2:13 AM, WK <wkmail at bneit.com> wrote: >> The default timeout for most OS versions is 30 seconds and the Gluster >> timeout is 42, so yes you can trigger an RO event. > I get read-only mount within approximately 2 seconds after failed IO. Hmm, we don't see that, even on busy VMs. We ARE using QCOW2 dis...

On 4 October 2017 at 23:34, WK <wkmail at bneit.com> wrote: > Just so I know. > > Is it correct to assume that this corruption issue is ONLY involved if you > are doing rebalancing with sharding enabled. > > So if I am not doing rebalancing I should be fine? > That is correct. > -bill > > > > On 10/3/20...

Hi, On Thu, Aug 24, 2017 at 2:13 AM, WK <wkmail at bneit.com> wrote: > The default timeout for most OS versions is 30 seconds and the Gluster > timeout is 42, so yes you can trigger an RO event. I get read-only mount within approximately 2 seconds after failed IO. > Though it is easy enough to raise as Pavel mentioned > > # echo 90 &g...

...39;d leave the website of a hungarian company in there, we contacted them and they think it's one of their ex-employee trying to cause them problems. I think we were just unlucky, but I'd really love to confirm how they did it > > On Mon, Aug 7, 2017 at 3:30 AM, W Kern <wkmail at bneit.com> wrote: > > > > > > > On 8/6/2017 4:57 PM, lemonnierk at ulrar.net wrote: > > > > > > Gluster already uses a vlan, the problem is that there is no easy way > > that I know of to tell gluster not to listen on an interface, and I > > can'...

That really isnt an arbiter issue or for that matter a Gluster issue. We have seen that with vanilla NAS servers that had some issue or another. Arbiter simply makes it less likely to be an issue than replica 2 but in turn arbiter is less 'safe' than replica 3. However, in regards to Gluster and RO behaviour The default timeout for most OS versions is 30 seconds and the Gluster

Hi, On Sat, Sep 9, 2017 at 2:35 AM, WK <wkmail at bneit.com> wrote: > Pavel. > > Is there a difference between native client (fuse) and libgfapi in regards > to the crashing/read-only behaviour? I switched to FUSE now and the VM crashed (read-only remount) immediately after one node started rebooting. I tried to mount.glusterfs same vol...

...area named ?lru? .Have you noticed any ECC errors in dmesg/IPMI of the system ? At least I would reboot the node and run hardware diagnostics to check that everything is fine. Best Regards,Strahil Nikolov? Sent from Yahoo Mail for iPhone On Tuesday, July 25, 2023, 4:31 AM, W Kern <wkmail at bneit.com> wrote: we have an older 2+1 arbiter gluster cluster running 6.10? on Ubuntu18LTS It has run beautifully for years. Only occaisionally needing attention as drives have died, etc Each peer has two volumes. G1 and G2 with a shared 'gluster' network. Since July 1st one of the peers...

On 8/6/2017 4:57 PM, lemonnierk at ulrar.net wrote: > > Gluster already uses a vlan, the problem is that there is no easy way > that I know of to tell gluster not to listen on an interface, and I > can't not have a public IP on the server. I really wish ther was a > simple "listen only on this IP/interface" option for this What about this?

Pavel. Is there a difference between native client (fuse) and libgfapi in regards to the crashing/read-only behaviour? We use Rep2 + Arb and can shutdown a node cleanly, without issue on our VMs. We do it all the time for upgrades and maintenance. However we are still on native client as we haven't had time to work on libgfapi yet. Maybe that is more tolerant. We have linux VMs mostly

...failed brick/disks ? Will this trigger a rebalance and then corruption? rebalance, is only needed when you have to expend a volume, ie by adding more bricks ? 2017-10-05 13:55 GMT+02:00 Nithya Balachandran <nbalacha at redhat.com>: > > > On 4 October 2017 at 23:34, WK <wkmail at bneit.com> wrote: >> >> Just so I know. >> >> Is it correct to assume that this corruption issue is ONLY involved if you >> are doing rebalancing with sharding enabled. >> >> So if I am not doing rebalancing I should be fine? > > > That is correct. &g...

Just so I know. Is it correct to assume that this corruption issue is ONLY involved if you are doing rebalancing with sharding enabled. So if I am not doing rebalancing I should be fine? -bill On 10/3/2017 10:30 PM, Krutika Dhananjay wrote: > > > On Wed, Oct 4, 2017 at 10:51 AM, Nithya Balachandran > <nbalacha at redhat.com <mailto:nbalacha at redhat.com>> wrote:

...there anyone who can audit the libgfapi usage in libvirt? :-) WK: I use bonded 2x10Gbps and I do get crashes only in heavy I/O situations (fio). Upgrading system (apt-get dist-upgrade) was ok, so this might be even related to amount of IOPS. -ps On Sun, Sep 10, 2017 at 6:37 AM, WK <wkmail at bneit.com> wrote: > I'm on 3.10.5. Its rock solid (at least with the fuse mount <Grin>) > > We are also typically on a somewhat slower GlusterFS LAN network (bonded > 2x1G, jumbo frames) so that may be a factor. > > I'll try to setup a trusted pool to test libgfapi soon...

On Wed, Oct 4, 2017 at 10:51 AM, Nithya Balachandran <nbalacha at redhat.com> wrote: > > > On 3 October 2017 at 13:27, Gandalf Corvotempesta < > gandalf.corvotempesta at gmail.com> wrote: > >> Any update about multiple bugs regarding data corruptions with >> sharding enabled ? >> >> Is 3.12.1 ready to be used in production? >> > >

> You should add VLANS, and/or overlay networks and/or Mac Address > filtering/locking/security which raises the bar quite a bit for hackers. > Perhaps your provider can help you with that. > Gluster already uses a vlan, the problem is that there is no easy way that I know of to tell gluster not to listen on an interface, and I can't not have a public IP on the server. I really

I'm on 3.10.5. Its rock solid (at least with the fuse mount <Grin>) We are also typically on a somewhat slower GlusterFS LAN network (bonded 2x1G, jumbo frames) so that may be a factor. I'll try to setup a trusted pool to test libgfapi soon. I'm curious as to how much faster it is, but the fuse mount is fast enough, dirt simple to use, and just works on all VM ops such as

Mh, not so sure really, using libgfapi and it's been working perfectly fine. And trust me, there had been A LOT of various crashes, reboots and kill of nodes. Maybe it's a version thing ? A new bug in the new gluster releases that doesn't affect our 3.7.15. On Sat, Sep 09, 2017 at 10:19:24AM -0700, WK wrote: > Well, that makes me feel better. > > I've seen all these