On 08/28/2017 04:44 PM, Nigel Babu wrote:
Hello folks,
I spend some time today mucking about trying to figure out how to make
our documentation search a better experience. The short answer is,
search kind of works now.
Long answer: mkdocs creates a client side file which is used for
search.
Till now I haven't found anything significant.
Can you send me gluster logs along with command-history-logs for these
scenarios:
Scenario1 : 20 servers
Scenario2 : 40 servers
Scenario3: 80 Servers
Thanks
Gaurav
On Mon, Aug 28, 2017 at 11:22 AM, Serkan Çoban
wrote:
> Hi Gaurav,
> Any pro
Also include gluster v status, I want to check the status of your bricks and
SHD processes.
-b
- Original Message -
> From: "Ben Turner"
> To: "Christoph Schäbel"
> Cc: gluster-users@gluster.org
> Sent: Tuesday, August 29, 2017 12:35:05 AM
> Subject: Re: [Gluster-users] GFID attir is m
This is strange, a couple of questions:
1. What volume type is this? What tuning have you done? gluster v info
output would be helpful here.
2. How big are your bricks?
3. Can you write me a quick reproducer so I can try this in the lab? Is it
just a single multi TB file you are untarrin
As suggested I have now opened a bug on bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1486063
> Original Message
> Subject: Re: [Gluster-users] self-heal not working
> Local Time: August 28, 2017 4:29 PM
> UTC Time: August 28, 2017 2:29 PM
> From: ravishan...@redhat.com
>
- Original Message -
> From: "mabi"
> To: "Ravishankar N"
> Cc: "Ben Turner" , "Gluster Users"
>
> Sent: Monday, August 28, 2017 3:59:06 AM
> Subject: Re: [Gluster-users] self-heal not working
>
> Excuse me for my naive questions but how do I reset the afr.dirty xattr on
> the file to
Great, can you raise a bug for the issue so that it is easier to keep
track (plus you'll be notified if the patch is posted) of it? The
general guidelines are @
https://gluster.readthedocs.io/en/latest/Contributors-Guide/Bug-Reporting-Guidelines
but you just need to provide whatever you describ
Thank you for the command. I ran it on all my nodes and now finally the the
self-heal daemon does not report any files to be healed. Hopefully this
scenario can get handled properly in newer versions of GlusterFS.
> Original Message
> Subject: Re: [Gluster-users] self-heal not
Hello folks,
I spend some time today mucking about trying to figure out how to make our
documentation search a better experience. The short answer is, search kind
of works now.
Long answer: mkdocs creates a client side file which is used for search.
RTD overrides this by referring people to Elast
On 08/28/2017 01:29 PM, mabi wrote:
Excuse me for my naive questions but how do I reset the afr.dirty
xattr on the file to be healed? and do I need to do that through a
FUSE mount? or simply on every bricks directly?
Directly on the bricks: `setfattr -n trusted.afr.dirty -v
0x0
Excuse me for my naive questions but how do I reset the afr.dirty xattr on the
file to be healed? and do I need to do that through a FUSE mount? or simply on
every bricks directly?
> Original Message
> Subject: Re: [Gluster-users] self-heal not working
> Local Time: August 28,
Hi Cluster Community,
we are seeing some problems when adding multiple terrabytes of data to a 2 node
replicated GlusterFS installation.
The version is 3.8.11 on CentOS 7.
The machines are connected via 10Gbit LAN and are running 24/7. The OS is
virtualized on VMWare.
After a restart of node-1
12 matches
Mail list logo
