We are working on a patch and target is to get it in 3.10.1. Apologies for
the inconvenience.
On Mon, 20 Mar 2017 at 04:02, Yong Zhang wrote:
> Someone already logged a bug here:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1429117
>
>
>
> I have the same issue, any
[
repost of http://blog.nixpanic.net/2017/03/glusterfs-3810-is-available.html
coming to https://planet.gluster.org/ any minute now
Enjoy the update,
Niels
]
The 10th update for GlusterFS 3.8 is available for users of the 3.8
Long-Term-Maintenance version. Packages for this minor update
On 03/20/2017 06:31 PM, Bernhard Dübi wrote:
Hi Ravi,
thank you very much for looking into this
The gluster volumes are used by CommVault Simpana to store backup
data. Nothing/Nobody should access the underlying infrastructure.
while looking at the xattrs of the files, I noticed that the
Hello,
I'm using one volume exclusively for configuration files, therefore
there is no I/O within this volume when the cluster is up and running.
It is a replicate volume with three bricks, one on each node. Pacemaker
is used to manage services including Gluster, using the
On 17/03/2017 9:41 PM, Niels de Vos wrote:
repost ofhttp://blog.nixpanic.net/2017/03/glusterfs-3810-is-available.html
coming tohttps://planet.gluster.org/ any minute now
Enjoy the update,
Niels
Thanks everyone, much appreciated. Currently doing a full backup of our
cluster and will
Hi,
Do you know the GFIDs of the VM images which were corrupted?
Regards,
Nithya
On 20 March 2017 at 20:37, Krutika Dhananjay wrote:
> I looked at the logs.
>
> From the time the new graph (since the add-brick command you shared where
> bricks 41 through 44 are added) is
Hello -
We have several
G
luster clusters, with both clients and servers running 3.5.3.
Each cluster can have several hundred clients
( so client updates will be particularly difficult )
We are looking at potential upgrade paths
that would minimize our impact,
and give us some of
Dear Matt,
we went the same route a couple of weeks ago and managed to upgrade a
legacy 3.5 installation to 3.8 on Gentoo Linux. Most of the upgrade
steps were pretty straight forward, a few needed some special attention
(such as op-code and volume parameter adaptions).
Foremost, we did the
I looked at the logs.
>From the time the new graph (since the add-brick command you shared where
bricks 41 through 44 are added) is switched to (line 3011 onwards in
nfs-gfapi.log), I see the following kinds of errors:
1. Lookups to a bunch of files failed with ENOENT on both replicas which