Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster, 2017-04-30

| Channels | #gluster index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:44 webe joined #gluster
00:45 webe Hi I have gluster 3.9 & am having an issue with a directory. It will not ls or rm -rf & the permissions are wonky. It set itself to 5000:5000 ownership at some point.
00:46 webe If I try to ls or rm -rf it will freeze for hours on end, I tried giving it 6hrs without any change in state. How do I sanely remove this troublesome directory?
00:50 derjohn_mob joined #gluster
01:39 derjohn_mob joined #gluster
02:18 Vaelatern joined #gluster
02:31 bmurt joined #gluster
02:32 gyadav__ joined #gluster
03:05 Gambit15 joined #gluster
03:06 rastar joined #gluster
03:10 Vaelatern joined #gluster
04:41 bmurt joined #gluster
05:30 major joined #gluster
06:19 gyadav__ joined #gluster
06:33 glisigno1i joined #gluster
06:33 glisigno1i Any have expirence with disperse-data volumes? I'm created one but I've been seeing very poor performance
06:34 jiffin joined #gluster
06:35 glisigno1i On a 30 node cluster with 12 bricks each, I'm getting just under 120MB/s. On a 4+2 configuration
06:37 riyas joined #gluster
06:38 gyadav__ joined #gluster
06:40 nuk3 joined #gluster
06:50 nuk3 hello, I'm having some difficulty adding new bricks (additional node) onto existing 2-node ditribute cluster. I'm running btrfs, so all harddrives appear as single device on their repsective node, and each node has approximately 10 folders each of which are shared as a gluster brick. I had a number of (peer rejected) issues initially and managed to resolve those using
06:50 nuk3 https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/. BUT, I had initially been able to add bricks from the peer rejected node, and the on further inspection with rebalance fix-layout, I noticed that the peer rejected node had picked up all the correct sub-folders from glusterd network, but it was the only node doing the rebalancing fix-layout. And was not probable from the other networks. So I
06:50 nuk3 purged gluster from the new node, cleared the attributes of the previous bricks on this new node as per https://joejulian.name/blog/glusterfs-path-or-a-prefix-of-it-is-already-part-of-a-volume/, but Pre-Validation is still failing when I now attempt to add bricks. All three nodes can peer status each other, and see each other as 'Peer in Cluster (Connected)' state
06:50 glusterbot Title: Resolving Peer Rejected State - Gluster Docs (at gluster.readthedocs.io)
06:51 skoduri joined #gluster
06:52 derjohn_mob joined #gluster
06:59 gyadav__ joined #gluster
07:05 jiffin joined #gluster
07:06 [diablo] joined #gluster
07:23 gyadav joined #gluster

| Channels | #gluster index | Today | | Search | Google Search | Plain-Text | summary