On 07/22/2014 12:07 PM, Kaushal M wrote:
The clear you have at top (the one for "clear-stats") is for 'top
clear'. Below there is a section with GF_CLI_INFO_CLEAR, which handles
'profile info clear'.
Cool. Thanks :-). The stuff that is present on master for 'profile' is
so much better :-)
Pra
On Monday 21 July 2014 13:14:46 Jeff Darcy wrote:
> Perhaps it's time to revisit the idea of making assumptions about d_off
> values and twiddling them back and forth, vs. maintaining a precise
> mapping between our values and local-FS values.
>
> http://review.gluster.org/#/c/4675/
>
> That patc
Joe,
BTW, Vipul (in CC) is also looking to quantify the impact of enabling
io-stats counters permanently.
It'd be great if you both could help each other out.
~kaushal
On Tue, Jul 22, 2014 at 12:54 PM, Pranith Kumar Karampuri
wrote:
>
> On 07/22/2014 12:07 PM, Kaushal M wrote:
>>
>> The clear yo
Here is my first draft of mem-pool data structure for review:
http://review.gluster.org/8343
Please don't laugh at the ascii art ;-).
Pranith
On 07/17/2014 04:10 PM, Ravishankar N wrote:
On 07/15/2014 04:39 PM, Pranith Kumar Karampuri wrote:
hi,
Please respond if you guys volunteer to a
I am trying to compile master for doing a fresh Coverity run. But
Coverity is complaining that source is not compiled fully. When I did
the same manually, I saw "make" is returning very less output compared
to past. I have copied the make output (along with autogen and
configure) in http://ur
On 07/22/2014 03:01 PM, Lalatendu Mohanty wrote:
>
> I am trying to compile master for doing a fresh Coverity run. But
> Coverity is complaining that source is not compiled fully. When I did
> the same manually, I saw "make" is returning very less output compared
> to past. I have copied the mak
On 07/22/2014 03:07 PM, Atin Mukherjee wrote:
On 07/22/2014 03:01 PM, Lalatendu Mohanty wrote:
I am trying to compile master for doing a fresh Coverity run. But
Coverity is complaining that source is not compiled fully. When I did
the same manually, I saw "make" is returning very less output co
> One possible solution is to convert directories into files managed by
> storage/posix (some changes will also be required in dht and afr
> probably). We will have full control about the format of this file,
> so we'll be able to use the directory offset that we want to avoid
> interferences with
I understand that when something is new and different, it is most likely
blamed for anything wrong that happens. I highly propose that we do not
do this, and instead work to learn more about the tool.
Cmockery2 is a tool that is important as the compiler. It provides an
extremely easy method
On 07/22/2014 04:28 AM, Vijay Bellur wrote:
On 07/21/2014 05:09 AM, Pranith Kumar Karampuri wrote:
On 07/21/2014 02:08 PM, Jiri Moskovcak wrote:
On 07/19/2014 08:58 AM, Pranith Kumar Karampuri wrote:
On 07/19/2014 11:25 AM, Andrew Lau wrote:
On Sat, Jul 19, 2014 at 12:03 AM, Pranith Kumar
On 07/22/2014 04:35 PM, Luis Pabón wrote:
I understand that when something is new and different, it is most
likely blamed for anything wrong that happens. I highly propose that
we do not do this, and instead work to learn more about the tool.
Cmockery2 is a tool that is important as the compi
Hi Lala,
No problem at all, I just want to make sure that developers
understand the importance of the tool. On the topic of RPMs, they have
a really cool section called "%check", which is currently being used to
run the unit tests after the glusterfs RPM is created. Normally
developers te
On 07/22/2014 05:22 PM, Luis Pabón wrote:
Hi Lala,
No problem at all, I just want to make sure that developers
understand the importance of the tool. On the topic of RPMs, they
have a really cool section called "%check", which is currently being
used to run the unit tests after the gluste
Hi All,
As with further investigation found the following,
1) Was the able to reproduce the issue, without running the complete
regression, just by running bug-1112559.t only on slave30(which is been
rebooted and a clean gluster setup).
This rules out any involvement of previous failure from
On Tuesday 22 July 2014 07:33:44 Jiffin Thottan wrote:
> Hi,
>
> There are some issues we are dealing with trash translator(see attachment
> for design doc).In our implementation, we create trash directory using
> trash translator.Thus trash directories on different bricks will have
> different gf
On Tuesday 22 July 2014 07:04:54 Jeff Darcy wrote:
> > One possible solution is to convert directories into files managed by
> > storage/posix (some changes will also be required in dht and afr
> > probably). We will have full control about the format of this file,
> > so we'll be able to use the
On 2014-07-22 15:12, Joseph Fernandes wrote:
> Hi All,
>
> As with further investigation found the following,
>
> 1) Was the able to reproduce the issue, without running the complete
> regression, just by running bug-1112559.t only on slave30(which is been
> rebooted and a clean gluster setup).
The issue is resolved now. "make clean" fixed the issue.
On 07/22/2014 03:34 PM, Lalatendu Mohanty wrote:
On 07/22/2014 03:07 PM, Atin Mukherjee wrote:
On 07/22/2014 03:01 PM, Lalatendu Mohanty wrote:
I am trying to compile master for doing a fresh Coverity run. But
Coverity is complaining t
On 07/22/2014 07:19 AM, Anders Blomdell wrote:
Could this be a time to propose that gluster understands port reservation a'la
systemd (LISTEN_FDS),
and make the test harness make sure that random ports do not collide with the
set of expected ports,
which will be beneficial when starting from sy
Hey everyone,
While I was writing the documentation for the options framework, I
thought up of a way to better organize the code documentation we are
creating now. I've posted a patch for review that implements this
organization. [1]
Copying the description from the patch I've posted for review,
On 22/07/2014, at 3:28 PM, Joe Julian wrote:
> On 07/22/2014 07:19 AM, Anders Blomdell wrote:
>> Could this be a time to propose that gluster understands port reservation
>> a'la systemd (LISTEN_FDS),
>> and make the test harness make sure that random ports do not collide with
>> the set of expec
On 2014-07-22 16:44, Justin Clift wrote:
> On 22/07/2014, at 3:28 PM, Joe Julian wrote:
>> On 07/22/2014 07:19 AM, Anders Blomdell wrote:
>>> Could this be a time to propose that gluster understands port reservation
>>> a'la systemd (LISTEN_FDS),
>>> and make the test harness make sure that random
To fix these Coverity issues , please check the below link for guidelines:
http://www.gluster.org/community/documentation/index.php/Fixing_Issues_Reported_By_Tools_For_Static_Code_Analysis#Coverity
Thanks,
Lala
Original Message
Subject:New Defects reported by Coverity
On 07/22/2014 06:58 PM, Xavier Hernandez wrote:
On Tuesday 22 July 2014 07:33:44 Jiffin Thottan wrote:
Hi,
There are some issues we are dealing with trash translator(see attachment
for design doc).In our implementation, we create trash directory using
trash translator.Thus trash directories on
On Tuesday 22 July 2014 22:02:53 Anoop C S wrote:
> > I see some other issues to this approach.
> >
> > 1. If the directory is physically created inside the normal namespace of
> > posix, it will be visible even if you disable the xlator. In this case all
> > users will have uncontrolled access to
Compilation fails if configured with --disable-xml-output
--disable-georeplication options.
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1122186
-Santosh
On 07/22/2014 07:56 PM, Lalatendu Mohanty wrote:
The issue is resolved now. "make clean" fixed the issue.
On 07/22/2014 03:34 PM, Lala
On Tue, Jul 22, 2014 at 7:35 AM, Kaushal M wrote:
> Hey everyone,
>
> While I was writing the documentation for the options framework, I
> thought up of a way to better organize the code documentation we are
> creating now. I've posted a patch for review that implements this
> organization. [1]
>
Thanks for the update :-)
Pranith
On 07/22/2014 06:42 PM, Joseph Fernandes wrote:
Hi All,
As with further investigation found the following,
1) Was the able to reproduce the issue, without running the complete
regression, just by running bug-1112559.t only on slave30(which is been
rebooted a
On 22/07/14 22:25, Xavier Hernandez wrote:
On Tuesday 22 July 2014 22:02:53 Anoop C S wrote:
I see some other issues to this approach.
1. If the directory is physically created inside the normal namespace of
posix, it will be visible even if you disable the xlator. In this case all
users will
Including Santosh and Niels
Pranith
On 07/21/2014 09:50 PM, Benjamin Turner wrote:
From what I can tell I incorrectly assumed that I was seeing a problem
deleting directories as described in:
https://bugzilla.redhat.com/show_bug.cgi?id=1121347#c4
This is definitely different than Anders is s
30 matches
Mail list logo