search for: jlawrence

...ork on this, as there exists a workaround and I've been busy with other tasks. If anyone wants to volunteer to get this done, I'll be happy to help). But anway, why is copying data into new unsharded volume disruptive for you? -Krutika On Sat, Apr 21, 2018 at 1:14 AM, Jamie Lawrence <jlawrence at squaretrade.com> wrote: > Hello, > > So I have a volume on a gluster install (3.12.5) on which sharding was > enabled at some point recently. (Don't know how it happened, it may have > been an accidental run of an old script.) So it has been happily sharding > behind ou...

On Tue, Mar 6, 2018 at 6:00 AM, Jamie Lawrence <jlawrence at squaretrade.com> wrote: > Hello, > > So I'm seeing a rejected peer with 3.12.6. This is with a replica 3 volume. > > It actually began as the same problem with a different peer. I noticed > with (call it) gluster-2, when I couldn't make a new volume. I compared &gt...

...hat if you restart the rejected peer I believe the problem should go away, if it doesn't I'd need to investigate further once you can pass down the glusterd and cmd_history log files and the content of /var/lib/glusterd from all the nodes. On Wed, Mar 7, 2018 at 4:13 AM, Jamie Lawrence <jlawrence at squaretrade.com> wrote: > > > On Mar 5, 2018, at 6:41 PM, Atin Mukherjee <amukherj at redhat.com> wrote: > > > I'm tempted to repeat - down things, copy the checksum the "good" ones > agree on, start things; but given that this has turned into a >...

Hello, So I'm seeing a rejected peer with 3.12.6. This is with a replica 3 volume. It actually began as the same problem with a different peer. I noticed with (call it) gluster-2, when I couldn't make a new volume. I compared /var/lib/glusterd between them, and found that somehow the options in one of the vols differed. (I suspect this was due to attempting to create the volume via the

Hello, So I have a volume on a gluster install (3.12.5) on which sharding was enabled at some point recently. (Don't know how it happened, it may have been an accidental run of an old script.) So it has been happily sharding behind our backs and it shouldn't have. I'd like to turn sharding off and reverse the files back to normal. Some of these are sparse files, so I need to account

> On Mar 5, 2018, at 6:41 PM, Atin Mukherjee <amukherj at redhat.com> wrote: > I'm tempted to repeat - down things, copy the checksum the "good" ones agree on, start things; but given that this has turned into a balloon-squeezing exercise, I want to make sure I'm not doing this the wrong way. > > Yes, that's the way. Copy

Hello Glusterites, I have a volume that will not mount read/write. V3.10.3 on Centos 7, this is a replica-3 volume, mounted with the fuse client. This is in support of an Ovirt installation, but I've isolated the problem to Gluster. `gluster peer status` looks normal, as does a `gluster v status`. Server.allow-insecure is set to on. Notable from the client volume logs are the 'connection

> On Apr 23, 2018, at 10:49 AM, WK <wkmail at bneit.com> wrote: > > From some old May 2017 email. I asked the following: > "From the docs, I see you can identify the shards by the GFID > # getfattr -d -m. -e hex path_to_file > # ls /bricks/*/.shard -lh | grep GFID > > Is there a gluster tool/script that will recreate the file? > > or can you just sort