My troubleshooting took me to confirming that all my package versions
were lined up and I came to realized that I had gotten version 5.0 from
the debian repos instead of the repo at download.gluster.org. I
downgraded everything to 4.1.5-1 from gluster.org, rebooted, and messed
around a bit,
forgot to add output of glusterd console when starting the volume:
[2018-10-31 17:31:33.887923] D [MSGID: 0]
[glusterd-volume-ops.c:572:__glusterd_handle_cli_start_volume]
0-management: Received start vol req for volume moogle-gluster
[2018-10-31 17:31:33.887976] D [MSGID: 0]
Hi,
it occurs maybe the previous email was too many words and not enough
data. so will try to display the issue differently.
gluster created (single brick volume following advice from
https://lists.gluster.org/pipermail/gluster-users/2016-October/028821.html):
root@sand1lian:~# gluster
These log messages represent a transient state and are harmless and can be
ignored. This happens when a lookup and mknod to create shards happen in
parallel.
Regarding the preallocated disk creation issue, could you check if there
are any errors/warnings in the fuse mount logs (these are named as
On 10/31/18 2:53 AM, Jeevan Patnaik wrote:
> Hi Vlad,
>
> Can gluster 4.1.5 too be used for production? There's no documentation
> for gluster 4.
>
The documentation for GlusterFS 4.x and 5 is about 99.99% the same as
GlusterFS 3.x.
That's not a reason not to use GlusterFS 4.x or GlusterFS 5
Hi,
I have the similar issues with ovirt 4.2 on a glusterfs-3.8.15 cluster.
This was a new volume and I created first a thin provisioned disk, then
I tried to create a preallocated disk but it hangs after 4MB. The only
issue I can find in the logs sofar are the [File exists] errors with the
Hi Vlad,
because I never got affinity and distributed.migrate-data using attrs
working, I finally invested time in nufa and found out that (against
docs) that "gluster volume set gv0 cluster.nufa 1" works to enable nufa,
so I did also with the data I had.
Then I started to copy files off the
Hello,
I have a GlusterFS 4.1.5 cluster with 3 nodes (including 1 arbiter) and
currently have a volume with around 27174 files which are not being healed. The
"volume heal info" command shows the same 27k files under the first node and
the second node but there is nothing under the 3rd node
I also noticed in the quotad.log file a lot of the following error messages:
The message "W [MSGID: 101016] [glusterfs3.h:743:dict_to_xdr] 0-dict: key
'trusted.glusterfs.quota.size' is not sent on wire [Invalid argument]" repeated
107 times between [2018-10-31 08:00:27.718645] and [2018-10-31
Hi Vlad,
Can gluster 4.1.5 too be used for production? There's no documentation for
gluster 4.
Regards,
Jeevan.
On Wed, Oct 31, 2018, 9:37 AM Vlad Kopylov wrote:
> 3.12.14 working fine in production for file access
> you can find vol and mount settings in mailing list archive
>
> On Tue, Oct
10 matches
Mail list logo
