On Fri, Sep 9, 2016 at 3:55 AM, Niels de Vos wrote:
> On Thu, Sep 08, 2016 at 10:03:03PM +0530, Sankarshan Mukhopadhyay wrote:
>> On Sun, Aug 28, 2016 at 2:13 PM, Niels de Vos wrote:
>> > This definitely has my preference too. I've always wanted to try to
>> > register port 24007/8, and maybe the
We have been collaborating for this work using the following trello board:
https://trello.com/b/mpM8rkmK/gluster-container-storage it is open for
public
Feel free to follow/comment about things you are interested in at that
board.
Work done in the past week:
1) Prashant completed containerizing s
On Thu, Sep 8, 2016 at 12:33 PM, Sankarshan Mukhopadhyay
wrote:
> On Sun, Aug 28, 2016 at 2:13 PM, Niels de Vos wrote:
>> This definitely has my preference too. I've always wanted to try to
>> register port 24007/8, and maybe the time has come to look into it.
>
> Has someone within the project p
On Thu, Sep 08, 2016 at 10:03:03PM +0530, Sankarshan Mukhopadhyay wrote:
> On Sun, Aug 28, 2016 at 2:13 PM, Niels de Vos wrote:
> > This definitely has my preference too. I've always wanted to try to
> > register port 24007/8, and maybe the time has come to look into it.
>
> Has someone within th
On 09/08/2016 10:33 AM, Vijay Bellur wrote:
On Thu, Sep 8, 2016 at 9:07 AM, Jeff Darcy wrote:
In a few places in our code (e.g. gf_log_callingfn) we use the "backtrace" and
"backtrace_symbols" functions from libc to log stack traces. Unfortunately, these
functions don't seem very smart about
On Sun, Aug 28, 2016 at 2:13 PM, Niels de Vos wrote:
> This definitely has my preference too. I've always wanted to try to
> register port 24007/8, and maybe the time has come to look into it.
Has someone within the project previously undertaken the process of
requesting the IANA for assignment o
On Thu, Sep 08, 2016 at 10:33:25AM -0400, Vijay Bellur wrote:
> On Thu, Sep 8, 2016 at 9:07 AM, Jeff Darcy wrote:
> > In a few places in our code (e.g. gf_log_callingfn) we use the "backtrace"
> > and "backtrace_symbols" functions from libc to log stack traces.
> > Unfortunately, these function
On Thu, Sep 8, 2016 at 9:07 AM, Jeff Darcy wrote:
> In a few places in our code (e.g. gf_log_callingfn) we use the "backtrace"
> and "backtrace_symbols" functions from libc to log stack traces.
> Unfortunately, these functions don't seem very smart about dynamically loaded
> libraries - such a
On Thu, Sep 08, 2016 at 09:07:33AM -0400, Jeff Darcy wrote:
> In a few places in our code (e.g. gf_log_callingfn) we use the "backtrace"
> and "backtrace_symbols" functions from libc to log stack traces.
> Unfortunately, these functions don't seem very smart about dynamically loaded
> libraries
08.09.2016 16:07, Jeff Darcy wrote:
(1) Has somebody already gone down this path? Does it work?
We've switched most of our internal projects to libunwind. It works OK.
(2) Are there any other reasons we wouldn't want to switch?
No, just go and switch :).
___
In a few places in our code (e.g. gf_log_callingfn) we use the "backtrace" and
"backtrace_symbols" functions from libc to log stack traces. Unfortunately,
these functions don't seem very smart about dynamically loaded libraries - such
as translators, where most of our code lives. They give us
> 1) Doing file snapshot using shards: (This is suggested by shyam, tried to
> keep the text as is)
> If a block for such a file is written to with a higher version then the brick
> xlators can perform a block copy and then change the new block to the new
> version, and let the older version be as
The meeting minutes are here slightly late, because I forgot to
`#startmeeting` the meeting. The minutes and logs can be obtained at
the links below,
Minutes:
https://meetbot.fedoraproject.org/gluster-meeting/2016-09-07/gluster-meeting.2016-09-07-17.30.html
Minutes(text):
https://meetbot-raw.fe
hi,
Doing file-snapshots is becoming important in the context of
providing virtual block in containers so that we can take a snapshot of the
block device and switch to different snapshots etc. So there have been some
attempts at the design for such solutions. This is a very early look at
som
14 matches
Mail list logo