hi,
Nowadays I am seeing quite a few patches are straightforward backports
from master. But if I follow the process it generally takes around 10
minutes to complete porting each patch. I was wondering if anyone else
looked into automating this. Yesterday I had to backport
On Tue, Oct 25, 2016 at 01:11:26PM -0400, Kaleb S. KEITHLEY wrote:
> On 10/25/2016 12:11 PM, Niels de Vos wrote:
> > On Tue, Oct 25, 2016 at 07:51:47AM -0400, Kaleb S. KEITHLEY wrote:
> >> On 10/25/2016 06:46 AM, Atin Mukherjee wrote:
> >>>
> >>>
> >>> On Tue, Oct 25, 2016 at 4:12 PM, Aravinda
Here are some of the numbers. Note that these are *without* multiplexing,
which is where these changes are really most beneficial, because I wanted to
measure the effect of this patch on its own. Also, perf-test.sh is a truly
awful test. For one thing it's entirely single-threaded, which
Gluster 3.9.0rc2 tarball is available here
http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.9.0rc2.tar.gz
regards
Aravinda
On Tuesday 25 October 2016 04:12 PM, Aravinda wrote:
Hi,
Since Automated test framework for Gluster is in progress, we need
help from Maintainers and
Hello.
As a result of today's community meeting I start dedicated ML thread for
gathering memory management issues together to make it possible to
summarize them and construct some plan what to do next.
Very important notice: I'm not the active GlusterFS developer, but
gained excessive
Hi all!
This weeks meeting was GD.
We got rid of the regular updates, and just had an open floor. This
had the intended effect of more conversations.
We discussed 3 main topics today,
- How do we recognize contributors and their contributions [manikandan]
- What's happening with memory
Hi all,
Please be reminded that changes need to be merged into release-3.7 for
GlusterFS-3,7.17 by today.
Regards,
Samikshan
On 10/24/2016 05:32 PM, Samikshan Bairagya wrote:
Hi all,
GlusterFS-3.7.17 is on target to be released on October 30th (Sunday).
In preparation for the release,
Do you also have the brick logs? Looks like the bricks are returning EINVAL
on lookup
which AFR is subsequently converting into an EIO. And sharding is merely
delivering the same error code upwards.
-Krutika
On Wed, Oct 26, 2016 at 6:38 AM, qingwei wei wrote:
> Hi,
>
> Pls
Brief update on progress we made on NFS-Ganesha
In last week NFS-Ganesha with FSAL_GLUSTER was tested in Bakeathon-
Boston 2016 and
found issues in ACL, solaris client and pNFS. There were four different
test environment
used with default configuration, kerberos configured, ACLs enabled
Ahead of the community meeting (barely), here's where things are. I've been in
meetings all week, so progress has been a bit slower than usual. When I've
been able to do direct work at all, it has mostly been on testing and mostly
for the prerequisite io-threads patch
On Wed, Oct 26, 2016 at 4:08 PM, Saravanakumar Arumugam
wrote:
>
>
> On 10/26/2016 03:58 PM, Raghavendra Talur wrote:
>>
>> HI,
>>
>> Is there any method to determine if volume "myvol" accessible through
>> volfile server "server1" is same as volume "myvol" accessible through
On 10/26/2016 03:58 PM, Raghavendra Talur wrote:
HI,
Is there any method to determine if volume "myvol" accessible through
volfile server "server1" is same as volume "myvol" accessible through
volfile server "server2"?
This is easy with trusted storage pool access, one has to determine if
Vijay Bellur wrote:
> Emmanuel might be able to help with problems related to NetBSD
> environment.
Sure, feel free to ask if you hit NetBSD-speciic troubles.
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org
___
Any progress about the major issue with gluster: the small files
performance?
Anyone working on this?
I would really like to use gluster as storage for maildirs or web hosting,
but with the current performance this wouldn't be possible without adding
additional layers (like exporting huge files
This week in GD2,
- We now have a Docker image and Vagrantfile for easier testing of GD2.
- The Dockerfiles and Vagrantfiles are available under
`/extras/dev-docker`[1] and `/extras/test-env`[2] in the GD2
repository.
- Docker images for testing will be automatically built for every
GD2
15 matches
Mail list logo