On Thu, Jan 11, 2018 at 1:56 AM, Kaleb S. KEITHLEY wrote:
> comments inline
>
> On 01/10/2018 02:08 PM, Shyam Ranganathan wrote:
>
> Hi, (GD2 team, packaging team, please read)
>
> Here are some things we need to settle so that we can ship/release GD2
> along with Gluster 4.0 release (considering
On Thu, Jan 11, 2018 at 12:38 AM, Shyam Ranganathan wrote:
> Hi, (GD2 team, packaging team, please read)
>
> Here are some things we need to settle so that we can ship/release GD2
> along with Gluster 4.0 release (considering this is a separate
> repository as of now).
>
> 1) Generating release pa
bit-rot is another feature that consumes much CPU to calculate the file
content hash
On Thu, Jan 11, 2018 at 11:42 AM, Ashish Pandey wrote:
> Hi,
>
> We have been thinking of exploiting GPU capabilities to enhance
> performance of glusterfs. We would like to know others thoughts on this.
> In E
Hi,
We have been thinking of exploiting GPU capabilities to enhance performance of
glusterfs. We would like to know others thoughts on this.
In EC, we have been doing CPU intensive computations to encode and decode data
before writing and reading. This requires a lot of CPU cycles and we have
Hi,
DISK_SPACE_CHECK_AND_GOTO in posix.h allows all calls from internal clients
to bypass the check. But in edge cases, internal clients could write to
files and fill up the brick. Would it be better to not allow some fops like
write in this case for internal clients as well?
Regards,
Nithya
Hi,
It's time to prepare the 3.12.5 release, which falls on the 10th of
each month, and hence would be 12-01-2018 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.5? If so mark them against the provided tracker [1
Hello folks,
If you take a machine offline, please file a bug so that the machine can be
debugged and return to the pool.
--
nigelb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel
Hello folks,
We may have been a little too quick to blame Meltdown on the Jenkins
failures yesterday. In any case, we've open a ticket with our provider and
they're looking into the failures. I've looked at the last 90 failures to
get a comprehensive number on the failures.
Total Jobs: 90
Failure
On Thu, Jan 11, 2018 at 6:35 AM, Lian, George (NSB - CN/Hangzhou) <
george.l...@nokia-sbell.com> wrote:
> Hi,
>
> >>> In which protocol are you seeing this issue? Fuse/NFS/SMB?
>
> It is fuse, within mountpoint by “mount -t glusterfs …“ command.
>
Could you let me know the test you did so that I
+csaba for fuse. +poornima, if the issue turns out to be an issue in
md-cache caching.
On Wed, Jan 10, 2018 at 5:37 PM, Pranith Kumar Karampuri <
pkara...@redhat.com> wrote:
>
>
> On Wed, Jan 10, 2018 at 11:09 AM, Lian, George (NSB - CN/Hangzhou) <
> george.l...@nokia-sbell.com> wrote:
>
>> Hi, P
+gluster-devel
- Original Message -
> From: "Raghavendra Gowdappa"
> To: "Omar Kohl"
> Cc: gluster-us...@gluster.org
> Sent: Wednesday, January 10, 2018 11:47:31 AM
> Subject: Re: [Gluster-users] Exact purpose of network.ping-timeout
>
>
>
> - Original Message -
> > From: "Rag
Hi,
As we are introducing a new protocol version, the existing gluster
wireshark plugin [1] needs to be updated.
Further this needs to get released to wireshark users in some fashion,
which looks like a need to follow wireshark roadmap [2] (not sure if
this can be part of a maintenance release, w
comments inline
On 01/10/2018 02:08 PM, Shyam Ranganathan wrote:
> Hi, (GD2 team, packaging team, please read) Here are some things we
> need to settle so that we can ship/release GD2 along with Gluster 4.0
> release (considering this is a separate repository as of now). 1)
> Generating release pa
Hi, (GD2 team, packaging team, please read)
Here are some things we need to settle so that we can ship/release GD2
along with Gluster 4.0 release (considering this is a separate
repository as of now).
1) Generating release package (read as RPM for now) to go with Gluster
4.0 release
Proposal:
Hi,
4.0 branching date is slated on the 16th of Jan 2018 and release is
slated for the end of Feb (28th), 2018.
We are at the phase when we need to ensure our release scope is correct
and *must* release features are landing. Towards this we need the
following information for all contributors.
1)
The first maintainers' meeting of the year 2018 went well, and there were
discussion and participation till the last minute. I hope more maintainers
join regularly to this meeting, and make it easier to take decisions.
BJ Link
- Bridge: https://bluejeans.com/205933580
- Download: https
Hi,
so it seems that the meltdown fix did slowdown regression testing, as
told to me by Nigel (after Nithya pointed this looked like timing
issue).
After a quick discussion on irc, we suspect this might be the lack of
pcid for the rackspace hosts.
So the good news is that we have a fix:
https:
Check the files in $mountpoint/.meta/ directory. These are all virtual. And
meta xlator gives a very good idea about how to handle virtual files (and
directories).
-Amar
On Wed, Jan 10, 2018 at 6:36 PM, Xavi Hernandez wrote:
> Hi David,
>
> On Wed, Jan 10, 2018 at 1:42 PM, David Spisla
> wrote
Hi David,
On Wed, Jan 10, 2018 at 1:42 PM, David Spisla
wrote:
>
> *[David Spisla] I tried this:*
>
> *char *new_path = malloc(1+len_path-5);*
>
> *memcpy(new_path, loc->path, len_path-5);*
>
> *new_path[strlen(new_path)] = '\0';*
>
> *loc->name = new_path + (len_path - len_name);*
>
>
>
> First
On Wed, Jan 10, 2018 at 11:09 AM, Lian, George (NSB - CN/Hangzhou) <
george.l...@nokia-sbell.com> wrote:
> Hi, Pranith Kumar,
>
>
>
> I has create a bug on Bugzilla https://bugzilla.redhat.com/
> show_bug.cgi?id=1531457
>
> After my investigation for this link issue, I suppose your changes on
> af
20 matches
Mail list logo
