Hi,
Thank you for your reply.
Lindsay,
Uunfortunately i do not have backup for this template.
Krutika,
The stat-prefetch is already disabled on the volume.
--
Respectfully
Mahdi A. Mahdi
From: Krutika Dhananjay
Sent: Friday, October 6, 2017 7:39 AM
To: Lindsa
The Gluster community is pleased to announce the release of Gluster
3.10.6 (packages available at [1]).
Release notes for the release can be found at [2].
We are still working on a further fix for the corruption issue when
sharded volumes are rebalanced, details as below.
* Expanding a glus
On Fri, Oct 06, 2017 at 11:31:47AM -0400, Shyam Ranganathan wrote:
> On 10/04/2017 06:17 AM, Niels de Vos wrote:
> > On Wed, Oct 04, 2017 at 09:44:44AM +, ismael mondiu wrote:
> > > Hello,
> > >
> > > I'd like to test if 3.10.6 version fixes the problem . I'm wondering
> > > which is the cor
On 10/04/2017 06:17 AM, Niels de Vos wrote:
On Wed, Oct 04, 2017 at 09:44:44AM +, ismael mondiu wrote:
Hello,
I'd like to test if 3.10.6 version fixes the problem . I'm wondering which is
the correct way to upgrade from 3.10.5 to 3.10.6.
It's hard to find upgrade guides for a minor relea
Any update about this?
I've seen some works about optimizing performance for small files, is
now gluster "usable" for storing, in example, Maildirs or git sources
?
at least in 3.7 (or 3.8, I don't remember exactly), extracting kernel
sources took about 4-5 minutes.
___
nfsv4 id mapping is based on username not uid so you could use ganesha nfs
to share the files.
On 5 October 2017 at 04:42, Frizz wrote:
> I have a setup with multiple hosts, each of them are administered
> separately. So there are no unified uid/gid for the users.
>
> When mounting a GlusterFS v
Hi,
It's time to prepare the 3.12.2 release, which falls on the 10th of
each month, and hence would be 10-10-2017 this time around.
This mail is to call out the following,
1) Are there any pending *blocker* bugs that need to be tracked for
3.12.2? If so mark them against the provided tracker [1
On 10/03/2017 02:15 AM, Bernhard Dübi wrote:
Hi Soumya,
what I can say so far:
it is working on a standalone system but not on the clustered system
Hi,
Sorry for the delay. Locking seem to have failed due to below
nsm_monitor error :
03/10/2017 14:27:38 : epoch 59cbce8c : chvirnfsprd12
