Re: [Gluster-devel] nfs/bug-904065.t fails test 22

2015-06-30 Thread Niels de Vos
On Thu, Jun 25, 2015 at 12:42:31AM -0400, Krishnan Parthasarathi wrote:
> Niels,
> 
> 
> 
> Test 22: 81: EXPECT '4' count_lines $M0/rmtab
> not ok 22 Got "2" instead of "4"
> 
> 
> 
> The above failure was observed with http://review.gluster.com/10445.
> For more details - 
> http://build.gluster.org/job/rackspace-regression-2GB-triggered/11321/consoleFull
> 
> How should I proceed with analysing what went wrong?

Hmm, I've seen this happen too now. Not sure why it would fail though.
Maybe it needs an EXPECT_WITHIN instead of a plain EXPECT. But, the
writing of $M0/rmtab is done by glusterd-store functions and is done
under locks.

I'll try to figure out what could make this fail.

Thanks,
Niels
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


Re: [Gluster-devel] Gluster and GCC 5.1

2015-06-30 Thread Joseph Fernandes
new patch sent : http://review.gluster.org/#/c/11214/


- Original Message -
From: "Niels de Vos" 
To: "Prashanth Pai" 
Cc: "Joseph Fernandes" , "Gluster Devel" 

Sent: Tuesday, June 30, 2015 2:00:15 AM
Subject: Re: [Gluster-devel] Gluster and GCC 5.1

On Mon, Jun 29, 2015 at 01:47:11PM -0400, Prashanth Pai wrote:
> Ah, I thought it was just me who was running into this.
> http://review.gluster.org/11214

Please file a decent bug with the behaviour and error messages. We need
this documented for our users that will likely hit the same problem at
one point.

Thanks,
Niels

> 
> Regards,
>  -Prashanth Pai
> 
> - Original Message -
> > From: "Joseph Fernandes" 
> > To: "Gluster Devel" 
> > Sent: Monday, June 29, 2015 5:54:28 PM
> > Subject: [Gluster-devel] Gluster and GCC 5.1
> > 
> > Hi All,
> > 
> > Recently I installed Fedora 22 on some fresh vms, which comes with gcc
> > 5.1.1-1(which can be upgraded to 5.1.1-4)
> > Observed one thing that normal "inline functions" will be undefined symbols
> > in the "so" files.
> > As a result I had trouble in start volume as "gf_sql_str2sync_t"
> > 
> > [2015-06-29 05:52:38.491378] I [MSGID: 101190]
> > [event-epoll.c:627:event_dispatch_epoll_worker] 0-epoll: Started thread with
> > index 1
> > [2015-06-29 05:52:38.499205] W [MSGID: 101095] [xlator.c:189:xlator_dynload]
> > 0-xlator: /usr/local/lib/libgfdb.so.0: undefined symbol: gf_sql_str2sync_t
> > [2015-06-29 05:52:38.499229] E [MSGID: 101002] [graph.y:211:volume_type]
> > 0-parser: Volume 'test-changetimerecorder', line 16: type
> > 'features/changetimerecorder' is not valid or not found on this machine
> > [2015-06-29 05:52:38.499262] E [MSGID: 101019] [graph.y:319:volume_end]
> > 0-parser: "type" not specified for volume test-changetimerecorder
> > [2015-06-29 05:52:38.499335] E [MSGID: 100026]
> > [glusterfsd.c:2151:glusterfs_process_volfp] 0-: failed to construct the
> > graph
> > [2015-06-29 05:52:38.499470] W [glusterfsd.c:1214:cleanup_and_exit] (--> 0-:
> > received signum (0), shutting down
> > 
> > when gf_sql_str2sync_t was made "static inline gf_sql_str2sync_t" the next
> > issue was with "changelog_dispatch_vec"
> > 
> > [2015-06-29 07:11:33.367259] I [MSGID: 101190]
> > [event-epoll.c:627:event_dispatch_epoll_worker] 0-epoll: Started thread with
> > index 1
> > [2015-06-29 07:11:33.368816] W [MSGID: 101095] [xlator.c:189:xlator_dynload]
> > 0-xlator: /usr/local/lib/glusterfs/3.8dev/xlator/features/changelog.so:
> > undefined symbol: changelog_dispatch_vec
> > [2015-06-29 07:11:33.368829] E [MSGID: 101002] [graph.y:211:volume_type]
> > 0-parser: Volume 'test-changelog', line 32: type 'features/changelog' is not
> > valid or not found on this machine
> > [2015-06-29 07:11:33.368843] E [MSGID: 101019] [graph.y:319:volume_end]
> > 0-parser: "type" not specified for volume test-changelog
> > [2015-06-29 07:11:33.368922] E [MSGID: 100026]
> > [glusterfsd.c:2151:glusterfs_process_volfp] 0-: failed to construct the
> > graph
> > [2015-06-29 07:11:33.369025] W [glusterfsd.c:1214:cleanup_and_exit] (--> 0-:
> > received signum (0), shutting down
> > 
> > and so on.
> > 
> > Looks like "inline" functions should be marked as "static inline" or "extern
> > inline" explicitly
> > Please refer https://gcc.gnu.org/gcc-5/porting_to.html
> > 
> > To recreate the issue without glusterfs, try out this sample code program on
> > fedora 22 gcc 5.1.1 or higher
> > 
> > hello.c
> > ===
> > 
> > #include 
> > 
> > inline void foo () {
> > printf ("hello world");
> > }
> > 
> > int main () {
> > 
> > foo ();
> > return 0;
> > }
> > 
> > # gcc hello.c
> > /tmp/ccUQ1XPp.o: In function `main':
> > hello.c:(.text+0xa): undefined reference to `foo'
> > collect2: error: ld returned 1 exit status
> > #
> > 
> > Should we change all the inline function to "static inline" or "extern
> > inline" in gluster, appropriately to their scope of use (IMHO would be a
> > right thing to do)?
> > or should we use a compiler flag to suppress this?
> > 
> > Regards,
> > Joe
> > 
> > 
> > 
> > 
> > ___
> > Gluster-devel mailing list
> > Gluster-devel@gluster.org
> > http://www.gluster.org/mailman/listinfo/gluster-devel
> > 
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


Re: [Gluster-devel] nfs/bug-904065.t fails test 22

2015-06-30 Thread Krishnan Parthasarathi

> Hmm, I've seen this happen too now. Not sure why it would fail though.
> Maybe it needs an EXPECT_WITHIN instead of a plain EXPECT. But, the
> writing of $M0/rmtab is done by glusterd-store functions and is done
> under locks.
> 
> I'll try to figure out what could make this fail.

Thanks for looking into this.
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


[Gluster-devel] REMINDER: Gluster Community Bug Triage meeting today at 12:00 UTC (~in 60 minutes)

2015-06-30 Thread Mohammed Rafi K C
Hi all,

This meeting is scheduled for anyone that is interested in learning more
about, or assisting with the Bug Triage.

Meeting details:
- location: #gluster-meeting on Freenode IRC
( https://webchat.freenode.net/?channels=gluster-meeting )
- date: every Tuesday
- time: 12:00 UTC
(in your terminal, run: date -d "12:00 UTC")
- agenda: https://public.pad.fsfe.org/p/gluster-bug-triage

Currently the following items are listed:
* Roll Call
* Status of last weeks action items
* Group Triage
* Open Floor

The last two topics have space for additions. If you have a suitable bug
or topic to discuss, please add it to the agenda.

Appreciate your participation.


Regards
Rafi KC

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


[Gluster-devel] Minutes from todays Gluster Community Bug Triage meeting

2015-06-30 Thread Mohammed Rafi K C


Minutes:
http://meetbot.fedoraproject.org/gluster-meeting/2015-06-30/gluster-meeting.2015-06-30-12.00.html
Minutes (text):
http://meetbot.fedoraproject.org/gluster-meeting/2015-06-30/gluster-meeting.2015-06-30-12.00.txt
Log:
http://meetbot.fedoraproject.org/gluster-meeting/2015-06-30/gluster-meeting.2015-06-30-12.00.log.html


Meeting summary
---
* Roll Call  (rafi, 12:01:12)
  * Agenda https://public.pad.fsfe.org/p/gluster-bug-triage  (rafi,
12:02:53)

* Action Items from last week  (rafi, 12:04:02)

* Group Triage  (rafi, 12:05:43)
  * 12 new bugs that have not been triaged yet : http://goo.gl/WuDQun
(rafi, 12:06:11)

* Open Floor  (rafi, 12:35:24)
  * ACTION: rafi need to send a followup mail in gluster-dev for
automated bug status  (rafi, 12:40:36)
  * ACTION: kkeithley_ will send a mail to encourage developers  to
upgrade to fedora 22 (for those who are using older version of
fedora )  (rafi, 12:47:04)

Meeting ended at 12:48:33 UTC.




Action Items

* rafi need to send a followup mail in gluster-dev for automated bug
  status
* kkeithley_ will send a mail to encourage developers  to upgrade to
  fedora 22 (for those who are using older version of fedora )




Action Items, by person
---
* kkeithley_
  * kkeithley_ will send a mail to encourage developers  to upgrade to
fedora 22 (for those who are using older version of fedora )
* rafi
  * rafi need to send a followup mail in gluster-dev for automated bug
status
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* rafi (56)
* ndevos (13)
* kkeithley_ (8)
* Saravana (4)
* zodbot (2)
* soumya_ (1)



On 06/30/2015 04:30 PM, Mohammed Rafi K C wrote:
> Hi all,
>
> This meeting is scheduled for anyone that is interested in learning more
> about, or assisting with the Bug Triage.
>
> Meeting details:
> - location: #gluster-meeting on Freenode IRC
> ( https://webchat.freenode.net/?channels=gluster-meeting )
> - date: every Tuesday
> - time: 12:00 UTC
> (in your terminal, run: date -d "12:00 UTC")
> - agenda: https://public.pad.fsfe.org/p/gluster-bug-triage
>
> Currently the following items are listed:
> * Roll Call
> * Status of last weeks action items
> * Group Triage
> * Open Floor
>
> The last two topics have space for additions. If you have a suitable bug
> or topic to discuss, please add it to the agenda.
>
> Appreciate your participation.
>
>
> Regards
> Rafi KC
>
>
> ___
> Gluster-users mailing list
> gluster-us...@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


[Gluster-devel] Justin's last day at Red Hat today ;)

2015-06-30 Thread Justin Clift
Hi us,

It's my last day at Red Hat today, so I've just adjusted the
jus...@gluster.org email address to redirect things to
jus...@postgresql.org instead.  So, people can still email
me.

I do have some Gluster things I'd like to finish off, it's just
I need a bit of a break first. ;)

+ Justin

--
GlusterFS - http://www.gluster.org

An open source, distributed file system scaling to several
petabytes, and handling thousands of clients.

My personal twitter: twitter.com/realjustinclift

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


[Gluster-devel] GlusterFS 3.7.2 RPMs for aarch64, Red Hat Linux Server for ARM

2015-06-30 Thread Kaleb KEITHLEY


In case anyone is interested, there are now aarch64 RPMs for RHELSA 7 at 
http://download.gluster.org/pub/gluster/glusterfs/LATEST/RHELSA/


--

Kaleb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


Re: [Gluster-devel] Justin's last day at Red Hat today ;)

2015-06-30 Thread Pranith Kumar Karampuri

All the best Justin!

Pranith

On 06/30/2015 08:11 PM, Justin Clift wrote:

Hi us,

It's my last day at Red Hat today, so I've just adjusted the
jus...@gluster.org email address to redirect things to
jus...@postgresql.org instead.  So, people can still email
me.

I do have some Gluster things I'd like to finish off, it's just
I need a bit of a break first. ;)

+ Justin

--
GlusterFS - http://www.gluster.org

An open source, distributed file system scaling to several
petabytes, and handling thousands of clients.

My personal twitter: twitter.com/realjustinclift

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


[Gluster-devel] Fedora users: upgrade to Fedora 22

2015-06-30 Thread Kaleb KEITHLEY


I have knowledge that more than one of our Gluster developers are still 
using Fedora 19 (or earlier?) for their development work.


This is bad for many reasons, but perhaps the worst one is that Fedora 
22 ships with gcc-5.1.x. which now defaults to newer versions of the C 
standard among other things.


One of the practices our developers have that's routinely breaking 
things is the use of 'inline'.  Using inline has some subtle traps, e.g. 
using alloca(), and we just shouldn't generally be using it. I.e. we 
shouldn't be using inline.


The use of inline with gcc-5 is producing other bugs too. Sometimes 
these are compile errors, and worse, some of them are run-time errors 
(like unresolved symbols and core dumps) that are somehow not being seen 
or worse, ignored, during development.


Please find half an hour and use fedup to update your development box.

And if you're using an old version of Debian, Ubuntu, or CentOS, the 
same is also true, even if the newer version doesn't have gcc-5 yet.


--

Kaleb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


Re: [Gluster-devel] Justin's last day at Red Hat today ;)

2015-06-30 Thread Atin Mukherjee
Its a sad news for many reasons but good to know (I firmly believe) that I
can still reach to you for any help on Gluster side especially on the infra
;)

It has been a pleasure working with you. I wish you all the best for your
future endeavors.

-Atin
Sent from one plus one
On Jun 30, 2015 8:12 PM, "Justin Clift"  wrote:

> Hi us,
>
> It's my last day at Red Hat today, so I've just adjusted the
> jus...@gluster.org email address to redirect things to
> jus...@postgresql.org instead.  So, people can still email
> me.
>
> I do have some Gluster things I'd like to finish off, it's just
> I need a bit of a break first. ;)
>
> + Justin
>
> --
> GlusterFS - http://www.gluster.org
>
> An open source, distributed file system scaling to several
> petabytes, and handling thousands of clients.
>
> My personal twitter: twitter.com/realjustinclift
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


Re: [Gluster-devel] Gluster Docker images are available at docker hub

2015-06-30 Thread Atin Mukherjee


On 05/06/2015 12:31 PM, Humble Devassy Chirammal wrote:
> Hi All,
> 
> 
> Docker images of GlusterFS 3.6 for Fedora ( 21) and CentOS  (7) are now
> available at docker hub ( https://registry.hub.docker.com/u/gluster/ ).
> These images can be used to deploy GlusterFS  containers.
> 
> The blog entry at planet.gluster.org [1] have details about how these
> images can be used.
> 
> Please let me know if you have any comments/feedback/questions.
> 
> [1] Building GlusterFS in a docker container @ planet.gluster.org
> [2] http://humblec.com/building-glusterfs-in-a-docker-container/
Hi Humble,

As discussed yesterday, post daemon refactoring we generate UUID at the
the time of glusterD init and this has caused an issue in bringing
multiple docker containers as UUIDs will be same across different
containers since yum install brings up glusterd and persist the
information in /var/lib/glusterd.info. To make this work for docker
containers could you add a line just after the installation steps in
Dockerfile?

rm -rf /var/lib/glusterd/glusterd.info

I could not find a way to send a pull request on this.

~Atin
> 
> --Humble
> 
> 
> 
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
> 

-- 
~Atin
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


Re: [Gluster-devel] [Gluster-users] Gluster Docker images are available at docker hub

2015-06-30 Thread Deepak Shetty
On Wed, Jul 1, 2015 at 9:39 AM, Atin Mukherjee  wrote:

>
>
> On 05/06/2015 12:31 PM, Humble Devassy Chirammal wrote:
> > Hi All,
> >
> >
> > Docker images of GlusterFS 3.6 for Fedora ( 21) and CentOS  (7) are now
> > available at docker hub ( https://registry.hub.docker.com/u/gluster/ ).
> > These images can be used to deploy GlusterFS  containers.
> >
> > The blog entry at planet.gluster.org [1] have details about how these
> > images can be used.
> >
> > Please let me know if you have any comments/feedback/questions.
> >
> > [1] Building GlusterFS in a docker container @ planet.gluster.org
> > [2] http://humblec.com/building-glusterfs-in-a-docker-container/
> Hi Humble,
>
> As discussed yesterday, post daemon refactoring we generate UUID at the
> the time of glusterD init and this has caused an issue in bringing
> multiple docker containers as UUIDs will be same across different
> containers since yum install brings up glusterd and persist the
> information in /var/lib/glusterd.info. To make this work for docker
> containers could you add a line just after the installation steps in
> Dockerfile?
>

Yeah I too faced this issued in recent past, fixing this will help users
running gluster in containers.


>
> rm -rf /var/lib/glusterd/glusterd.info
>

Yeah this followed by glusterd restart should help

But frankly, i was hoping that 'rm' the file isn't a neat way to fix this
issue
AFAICT we have 2 scenarios:

1) Non-container scenario, where the current behaviour of glusterd
persisting the info in .info file makes sense

2) Container scenario, where the same image gets used as the base, hence
all containers gets the same UUID
For this we can have an option to tell glusterd that instructs it to
refresh the UUID during next start.

Maybe somethign like presence of a file /var/lib/glusterd/refresh_uuid
makes glusterd refresh the UUID in .info
and then delete this file, that ways, Dockerfile can touch this file, post
gluster rpm install step and things should
work as expected ?

thanx,
deepak



>
> I could not find a way to send a pull request on this.
>
> ~Atin
> >
> > --Humble
> >
> >
> >
> > ___
> > Gluster-devel mailing list
> > Gluster-devel@gluster.org
> > http://www.gluster.org/mailman/listinfo/gluster-devel
> >
>
> --
> ~Atin
> ___
> Gluster-users mailing list
> gluster-us...@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


Re: [Gluster-devel] [Gluster-users] Gluster Docker images are available at docker hub

2015-06-30 Thread Atin Mukherjee


On 07/01/2015 11:09 AM, Deepak Shetty wrote:
> On Wed, Jul 1, 2015 at 9:39 AM, Atin Mukherjee  wrote:
> 
>>
>>
>> On 05/06/2015 12:31 PM, Humble Devassy Chirammal wrote:
>>> Hi All,
>>>
>>>
>>> Docker images of GlusterFS 3.6 for Fedora ( 21) and CentOS  (7) are now
>>> available at docker hub ( https://registry.hub.docker.com/u/gluster/ ).
>>> These images can be used to deploy GlusterFS  containers.
>>>
>>> The blog entry at planet.gluster.org [1] have details about how these
>>> images can be used.
>>>
>>> Please let me know if you have any comments/feedback/questions.
>>>
>>> [1] Building GlusterFS in a docker container @ planet.gluster.org
>>> [2] http://humblec.com/building-glusterfs-in-a-docker-container/
>> Hi Humble,
>>
>> As discussed yesterday, post daemon refactoring we generate UUID at the
>> the time of glusterD init and this has caused an issue in bringing
>> multiple docker containers as UUIDs will be same across different
>> containers since yum install brings up glusterd and persist the
>> information in /var/lib/glusterd.info. To make this work for docker
>> containers could you add a line just after the installation steps in
>> Dockerfile?
>>
> 
> Yeah I too faced this issued in recent past, fixing this will help users
> running gluster in containers.
> 
> 
>>
>> rm -rf /var/lib/glusterd/glusterd.info
>>
> 
> Yeah this followed by glusterd restart should help
> 
> But frankly, i was hoping that 'rm' the file isn't a neat way to fix this
> issue
> AFAICT we have 2 scenarios:
> 
> 1) Non-container scenario, where the current behaviour of glusterd
> persisting the info in .info file makes sense
> 
> 2) Container scenario, where the same image gets used as the base, hence
> all containers gets the same UUID
> For this we can have an option to tell glusterd that instructs it to
> refresh the UUID during next start.
> 
> Maybe somethign like presence of a file /var/lib/glusterd/refresh_uuid
> makes glusterd refresh the UUID in .info
> and then delete this file, that ways, Dockerfile can touch this file, post
> gluster rpm install step and things should
> work as expected ?
We do have a way to tackle this situation from the code. Raghavendra
Talur will be sending a patch shortly.
> 
> thanx,
> deepak
> 
> 
> 
>>
>> I could not find a way to send a pull request on this.
>>
>> ~Atin
>>>
>>> --Humble
>>>
>>>
>>>
>>> ___
>>> Gluster-devel mailing list
>>> Gluster-devel@gluster.org
>>> http://www.gluster.org/mailman/listinfo/gluster-devel
>>>
>>
>> --
>> ~Atin
>> ___
>> Gluster-users mailing list
>> gluster-us...@gluster.org
>> http://www.gluster.org/mailman/listinfo/gluster-users
>>
> 

-- 
~Atin
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


[Gluster-devel] Updated Invitation: Gluster Community Weekly Meeting @ Weekly from 5am to 6am on Wednesday from Wed Aug 20, 2014 to Wed Jun 24 (vbel...@redhat.com)

2015-06-30 Thread vbellur
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Asia/Calcutta
X-LIC-LOCATION:Asia/Calcutta
BEGIN:STANDARD
TZOFFSETFROM:+0530
TZOFFSETTO:+0530
TZNAME:IST
DTSTART:19700101T00
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=Asia/Calcutta:20140820T173000
DTEND;TZID=Asia/Calcutta:20140820T183000
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=WE;UNTIL=20150624T12Z
DTSTAMP:20150701T055636Z
ORGANIZER;CN=Vijay Bellur:mailto:vbel...@redhat.com
UID:7b49ac44-ffca-4de4-a179-f9edde80bf1e
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=nde...@redhat.com;X-NUM-GUESTS=0:mailto:nde...@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=jim...@redhat.com;X-NUM-GUESTS=0:mailto:jim...@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dlamb...@redhat.com;X-NUM-GUESTS=0:mailto:dlamb...@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=DECLINED;RSVP=TRUE
 ;CN=pport...@redhat.com;X-NUM-GUESTS=0:mailto:pport...@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Vijay Bellur;X-NUM-GUESTS=0:mailto:vbel...@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=jcl...@redhat.com;X-NUM-GUESTS=0:mailto:jcl...@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=gluster-us...@gluster.org;X-NUM-GUESTS=0:mailto:gluster-users@glust
 er.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=nmaje...@suntradingllc.com;X-NUM-GUESTS=0:mailto:nmajeran@suntradin
 gllc.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=o...@heha.org;X-NUM-GUESTS=0:mailto:o...@heha.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=btur...@redhat.com;X-NUM-GUESTS=0:mailto:btur...@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=kdhan...@redhat.com;X-NUM-GUESTS=0:mailto:kdhan...@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=DECLINED;RSVP=TRUE
 ;CN=rwhee...@redhat.com;X-NUM-GUESTS=0:mailto:rwhee...@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=DECLINED;RSVP=TRUE
 ;CN=jshuc...@redhat.com;X-NUM-GUESTS=0:mailto:jshuc...@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=nbala...@redhat.com;X-NUM-GUESTS=0:mailto:nbala...@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;RSVP=TRU
 E;CN=lpa...@redhat.com;X-NUM-GUESTS=0:mailto:lpa...@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=bjorn.sko...@basefarm.com;X-NUM-GUESTS=0:mailto:bjorn.skobba@basefa
 rm.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=gluster-devel@gluster.org;X-NUM-GUESTS=0:mailto:gluster-devel@glust
 er.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=vah...@doruk.net.tr;X-NUM-GUESTS=0:mailto:vah...@doruk.net.tr
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=rta...@redhat.com;X-NUM-GUESTS=0:mailto:rta...@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=kkeit...@redhat.com;X-NUM-GUESTS=0:mailto:kkeit...@redhat.com
CREATED:20150424T220745Z
DESCRIPTION:Greetings\,\n\nThis is the new weekly slot to discuss all aspec
 ts concerning the Gluster community. \n\nAgenda - https://public.pad.fsfe.o
 rg/p/gluster-community-meetings \n\nPlease feel free to add your agenda ite
 ms before the meeting. \n\nCheers\, \nVijay\nView your event at https://www
 .google.com/calendar/event?action=VIEW&eid=XzZ0aDM4ZWIxY2NxMzhiYjZjcGhtMmI5
 a2NoaWo4YmIxNjRyamliYjY3NWltOHAzNTcwbzY0cGhoY2sgZ2x1c3Rlci1kZXZlbEBnbHVzdGV
 yLm9yZw&tok=MTgjdmJlbGx1ckByZWRoYXQuY29tMWIyY2ZmZTAwNGFlZGY1OTI0OTViMDNmZWU
 1MDM2ODViNzY3NGY5Yw&ctz=America/Los_Angeles&hl=en.
LAST-MODIFIED:20150701T055635Z
LOCATION:#gluster-meeting on irc.freenode.net
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Gluster Community Weekly Meeting
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


Re: [Gluster-devel] [Gluster-users] Gluster Docker images are available at docker hub

2015-06-30 Thread Krishnan Parthasarathi

> Yeah this followed by glusterd restart should help
> 
> But frankly, i was hoping that 'rm' the file isn't a neat way to fix this
> issue

Why is rm not a neat way? Is it because the container deployment tool needs to
know about gluster internals? But isn't a Dockerfile dealing with details
of the service(s) that is being deployment in a container.

> AFAICT we have 2 scenarios:
> 
> 1) Non-container scenario, where the current behaviour of glusterd persisting
> the info in .info file makes sense
> 
> 2) Container scenario, where the same image gets used as the base, hence all
> containers gets the same UUID
> For this we can have an option to tell glusterd that instructs it to refresh
> the UUID during next start.
> 
> Maybe somethign like presence of a file /var/lib/glusterd/refresh_uuid makes
> glusterd refresh the UUID in .info
> and then delete this file, that ways, Dockerfile can touch this file, post
> gluster rpm install step and things should
> work as expected ?

If container deployment needs are different it should should address issues like
above. If we start addressing glusterd's configuration handling for every
new deployment technology it would quickly become unmaintainable.
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


Re: [Gluster-devel] [Gluster-users] Gluster Docker images are available at docker hub

2015-06-30 Thread Krishnan Parthasarathi

> We do have a way to tackle this situation from the code. Raghavendra
> Talur will be sending a patch shortly.

We should fix it by undoing what daemon-refactoring did, that broke the lazy 
creation
of uuid for a node. Fixing it elsewhere is just masking the real cause.
Meanwhile 'rm' is the stop gap arrangement.
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


Re: [Gluster-devel] [Gluster-users] Gluster Docker images are available at docker hub

2015-06-30 Thread Raghavendra Talur
On Wed, Jul 1, 2015 at 11:51 AM, Krishnan Parthasarathi  wrote:

>
> > We do have a way to tackle this situation from the code. Raghavendra
> > Talur will be sending a patch shortly.
>
> We should fix it by undoing what daemon-refactoring did, that broke the
> lazy creation
> of uuid for a node. Fixing it elsewhere is just masking the real cause.
> Meanwhile 'rm' is the stop gap arrangement.
>

Agreed.
The patch I was supposed to send may not solve this issue
.
Atin understands this code well better than I and I guess would be sending
the patch
to generate uuid on first volume creation or first peer probe instead of on
first start of glusterd.



> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>



-- 
*Raghavendra Talur *
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


[Gluster-devel] Progress on adding support for SEEK_DATA and SEEK_HOLE

2015-06-30 Thread Niels de Vos
On Tue, Jun 30, 2015 at 11:48:20PM +0530, Ravishankar N wrote:
> 
> 
> On 06/22/2015 03:22 PM, Ravishankar N wrote:
> >
> >
> >On 06/22/2015 01:41 PM, Miklos Szeredi wrote:
> >>On Sun, Jun 21, 2015 at 6:20 PM, Niels de Vos  wrote:
> >>>Hi,
> >>>
> >>>it seems that there could be a reasonable benefit for virtual machine
> >>>images on a FUSE mountpoint when SEEK_DATA and SEEK_HOLE would be
> >>>available. At the moment, FUSE does not pass lseek() on to the
> >>>userspace
> >>>process that handles the I/O.
> >>>
> >>>Other filesystems that do not (need to) track the position in the
> >>>file-descriptor are starting to support SEEK_DATA/HOLE. One example is
> >>>NFS:
> >>>
> >>>https://tools.ietf.org/html/draft-ietf-nfsv4-minorversion2-38#section-15.11
> >>>
> >>>I would like to add this feature to Gluster, and am wondering if there
> >>>are any reasons why it should/could not be added to FUSE.
> >>I don't see any reason why it couldn't be added.  Please go ahead.
> >
> >Thanks for bouncing the mail to me Niels, I would be happy to work on
> >this. I'll submit a patch by Monday next.
> >
> 
> 
> Sent a patch @
> http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/14752
> I've tested it with some skeleton code in gluster-fuse to handle lseek().

Ravi also sent his patch for glusterfs-fuse:

  http://review.gluster.org/11474

I have posted my COMPLETELY UNTESTED patches to their own Gerrit topic
so that we can easily track the progress:

  
http://review.gluster.org/#/q/status:open+project:glusterfs+branch:master+topic:wip/SEEK_HOLE

My preference goes to share things early and make everyone able to
follow progress (know where to find the latest patches). Assistance in
testing, reviewing and improving is welcome! There are some outstanding
things like seek() for ec and sharding, and probably more.

This all was done as a suggestion from Christopher (kripper) Pereira,
for improving the handling of sparse files (like most VM images).

Thanks,
Niels
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel