[Gluster-devel] Gluster Community Weekly Meeting
BEGIN:VCALENDAR PRODID:Zimbra-Calendar-Provider VERSION:2.0 METHOD:REQUEST BEGIN:VTIMEZONE TZID:Asia/Kolkata BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETTO:+0530 TZOFFSETFROM:+0530 TZNAME:IST END:STANDARD END:VTIMEZONE BEGIN:VEVENT UID:7b49ac44-ffca-4de4-a179-f9edde80bf1e RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=WE SUMMARY:Gluster Community Weekly Meeting DESCRIPTION:Greetings\,\n\nThis is the new weekly slot to discuss all aspect s concerning the Gluster community. \n\nAgenda - https://public.pad.fsfe.org /p/gluster-community-meetings \n\nPlease feel free to add your agenda items before the meeting. \n\nCheers\, \nVijay \n LOCATION:#gluster-meeting on irc.freenode.net ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:gluster -us...@gluster.org ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:gluster -de...@gluster.org ORGANIZER;CN=Vijay Bellur:mailto:vbel...@redhat.com DTSTART;TZID=Asia/Kolkata:20140820T173000 DTEND;TZID=Asia/Kolkata:20140820T183000 STATUS:CONFIRMED CLASS:PUBLIC X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY TRANSP:OPAQUE LAST-MODIFIED:20140820T101136Z DTSTAMP:20140820T101136Z SEQUENCE:6 BEGIN:VALARM ACTION:DISPLAY TRIGGER;RELATED=START:-PT5M DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] About file descriptor leak in glusterfsd daemon after network failure
Hi gluster-devel team, We are running a 2 replica volume in 2 servers. One of our service daemon open a file with 'flock' in the volume. We can see every glusterfsd daemon open the replica files in its own server(in /proc/pid/fd). When we pull off the cable of one server about 10 minutes then re-plug in. We found that the glusterfsd open a 'NEW' file descriptor while still holding the old one which is opened in the first file access. Then we stop our service daemon, but the glusterfsd(the re-plug cable one) only closes the new fd, leave the old fd open, we think that may be a fd leak issue. And we restart our service daemon. It flocked the same file, and get a flock failure. The errno is Resource Temporary Unavailable. However, this situation is not replay every time but often come out. We are still looking into the source code of glusterfsd, but it is not a easy job. So we want to look for some help in here. Here are our questions: 1. Has this issue been solved? Or is it a known issue? 2. Does anyone know the file descriptor maintenance logic in glusterfsd(server-side)? When the fd will be closed or held? Thank you very much. -- Best regards, Jaden Liang ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] reviews of cppcheck for Ubuntu fixes needed.
Hi, Three changes are in desperate need of review. FWIW, Ubuntu would not update to a recent release of GlusterFS without these fixes, so we finessed these into 3.4.x (i.e. we did not wait for them on the master branch) but the same fixes are needed in the the other branches, including the master branch. In some sense these are probably vulnerabilities that are potentially exploitable. Please let's get these reviewed and merged ASAP. + master http://review.gluster.org/8064, has +1, needs +2 + release-3.6 http://review.gluster.org/8351, needs +1, +2 + release-3.5 http://review.gluster.org/7605 has +2, waiting for merging the change in master I even offer bribes, subject to me actually getting to your location to make good on the bribe. But don't let my ability to deliver bribes slow you down. Review early, review often. Please be diligent and make certain they are good reviews -- no rubber stamp reviews please. Thanks. -- Kaleb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] About file descriptor leak in glusterfsd daemon after network failure
On Wed, Aug 20, 2014 at 07:16:16PM +0800, Jaden Liang wrote: Hi gluster-devel team, We are running a 2 replica volume in 2 servers. One of our service daemon open a file with 'flock' in the volume. We can see every glusterfsd daemon open the replica files in its own server(in /proc/pid/fd). When we pull off the cable of one server about 10 minutes then re-plug in. We found that the glusterfsd open a 'NEW' file descriptor while still holding the old one which is opened in the first file access. Then we stop our service daemon, but the glusterfsd(the re-plug cable one) only closes the new fd, leave the old fd open, we think that may be a fd leak issue. And we restart our service daemon. It flocked the same file, and get a flock failure. The errno is Resource Temporary Unavailable. However, this situation is not replay every time but often come out. We are still looking into the source code of glusterfsd, but it is not a easy job. So we want to look for some help in here. Here are our questions: 1. Has this issue been solved? Or is it a known issue? 2. Does anyone know the file descriptor maintenance logic in glusterfsd(server-side)? When the fd will be closed or held? I think you are hitting bug 1129787: - https://bugzilla.redhat.com/show_bug.cgi?id=1129787 file locks are not released within an acceptable time when a fuse-client uncleanly disconnects There has been a (short) discussion about this earlier, see http://supercolony.gluster.org/pipermail/gluster-devel/2014-May/040748.html Updating the proposed change is on my TODO list, in the end, the network.ping-timeout option should be used to define the timeout towards storage servers (like it is now) and the timeout from storage server to GlusterFS-client. You can try out the patch at http://review.gluster.org/8065 and see if the network.tcp-timeout option works for you. Just remember that the option will get fold into the network.ping-timeout one later on. If you are interested in sending an updated patch, let me know :) Cheers, Niels ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] NetBSD patch backlog
Hi I accumulated a few NetBSD patches that were all validated but still await review. Anyone would like to help moving them forward? Everything is there: http://review.gluster.org/#/q/owner:%22Emmanuel+Dreyfus%22+status:open,n,z -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz m...@netbsd.org ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] NetBSD patch backlog
On 20/08/2014, at 9:30 PM, Harshavardhana wrote: Should we be aiming to get these into 3.6, in time for the upcoming test Yes we should, the real issue is the amount of reviews they are pending. btw when was 3.6 test day decided? We're waiting for some other fixes for 3.6 to go in first (dht and afrv2) before it can go ahead. So, it'll probably be sometime next week. + 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://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] update-link-count-parent POSIX xlator parameter
What is update-link-count-parent POSIX xlator parameter for? Is it ever set by anyone and why? It appears to be off by default. Didn't see this documented, but the log message in posix.c says: update-link-count-parent is enabled. Thus for each file an extended attribute representing the number of hardlinks for that file within the same parent directory is set. Why would this be necessary? background: I'm trying to see where various xattr calls per file read are coming from. ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] update-link-count-parent POSIX xlator parameter
On Wed, Aug 20, 2014 at 1:55 PM, Ben England bengl...@redhat.com wrote: What is update-link-count-parent POSIX xlator parameter for? Is it ever set by anyone and why? It appears to be off by default. Didn't see this documented, but the log message in posix.c says: update-link-count-parent is enabled. Thus for each file an extended attribute representing the number of hardlinks for that file within the same parent directory is set. Why would this be necessary? It was supposed to be used by Quota or it uses it internally i am not sure for ancestry paths and gfid to path conversion - AFAIK # gluster volume set volname build-pgfid on Enables this feature. Never tested it personally. -- Religious confuse piety with mere ritual, the virtuous confuse regulation with outcomes ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Change in glusterfs[master]: Regression test portability: mktemp
Again with the unpack issue with git Build Failed http://build.gluster.org/job/glusterfs-rpms/556/ : SUCCESS http://build.gluster.org/job/glusterfs-rpms-el6/556/ : FAILURE Receiving objects: 2% (2239/81742), 579.83 KiB | 854.00 KiB/s Receiving objects: 3% (2453/81742), 579.83 KiB | 854.00 KiB/s remote: internal server error Receiving objects: 4% (3270/81742), 579.83 KiB | 854.00 KiB/s fatal: early EOF fatal: index-pack failed at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:774) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clone(CliGitAPIImpl.java:218) ... 11 more Trying next repository ERROR: Could not clone repository ... ... ... Finished: FAILURE If you remember this bogged us while setting up FreeBSD ?? - there seems something going wrong we have to verify as it may be disastrous in future. Perhaps a 'git gc' and we have to see if the git packs on the git.gluster.org are not corrupted. -- Religious confuse piety with mere ritual, the virtuous confuse regulation with outcomes ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] Fwd: Change in glusterfs[master]: Regression test portability: mktemp
Any ideas? + Justin Begin forwarded message: From: Harshavardhana har...@harshavardhana.net Subject: Re: Change in glusterfs[master]: Regression test portability: mktemp Date: 20 August 2014 10:30:29 PM GMT+01:00 To: Justin Clift jus...@gluster.org, Vijay Bellur vbel...@redhat.com, Gluster Devel gluster-devel@gluster.org Again with the unpack issue with git Build Failed http://build.gluster.org/job/glusterfs-rpms/556/ : SUCCESS http://build.gluster.org/job/glusterfs-rpms-el6/556/ : FAILURE Receiving objects: 2% (2239/81742), 579.83 KiB | 854.00 KiB/s Receiving objects: 3% (2453/81742), 579.83 KiB | 854.00 KiB/s remote: internal server error Receiving objects: 4% (3270/81742), 579.83 KiB | 854.00 KiB/s fatal: early EOF fatal: index-pack failed at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:774) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clone(CliGitAPIImpl.java:218) ... 11 more Trying next repository ERROR: Could not clone repository ... ... ... Finished: FAILURE If you remember this bogged us while setting up FreeBSD ?? - there seems something going wrong we have to verify as it may be disastrous in future. Perhaps a 'git gc' and we have to see if the git packs on the git.gluster.org are not corrupted. -- Religious confuse piety with mere ritual, the virtuous confuse regulation with outcomes -- 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://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Fwd: Change in glusterfs[master]: Regression test portability: mktemp
On Wed, Aug 20, 2014 at 2:49 PM, Justin Clift jus...@gluster.org wrote: Any ideas? Avati just fixed it We had to run 'git gc' directly on the gerrit server - gerrit gc failed (could be a gerrit bug). Suspecting the EOF unpack errors to be gerrit bug as well, we should be updating it to latest release perhaps? Thanks -- Religious confuse piety with mere ritual, the virtuous confuse regulation with outcomes ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Change in glusterfs[master]: Regression test portability: mktemp
Harshavardhana har...@harshavardhana.net wrote: ERROR: Could not clone repository Using git over ssh often fails, is it the same problem? I never investigated, but using HTTP is reliable. I often have to run rfc.sh three or four times before it works. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz m...@netbsd.org ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] about split-brain
hi all: I have a problem about split-brain, details as below: PC1 and PC2 is AFR, stored a file 1.txt 1. write 123 to 1.txt, then 1.txt in pc1 is same with 1.txt in PC2, content is 123 2. PC1 network disconnect, write 45 to 1.txt, then content of 1.txt in pc1 is 123, content of 1.txt in pc2 is 12345 3. PC2 network disconnect, but PC1 network is good, write 67 to 1.txt, then content of 1.txt in pc1 is 12367, content of 1.txt in pc1 is 12345 4. so split brain occur is this a bug or design this? how glusterfs avoid this? Have some ways to solve? this is my questions. thank you everybody_en...@163.com ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Change in glusterfs[master]: Regression test portability: mktemp
Using git over ssh often fails, is it the same problem? I never investigated, but using HTTP is reliable. I often have to run rfc.sh three or four times before it works. It seems like a 'gerrit' bug at the moment, its fixed with 'git gc' on the server no corruption reported :-). -- Religious confuse piety with mere ritual, the virtuous confuse regulation with outcomes ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] about split-brain
On 08/21/2014 08:23 AM, everybody_en...@163.com wrote: hi all: I have a problem about split-brain, details as below: PC1 and PC2 is AFR, stored a file 1.txt 1. write 123 to 1.txt, then 1.txt in pc1 is same with 1.txt in PC2, content is 123 2. PC1 network disconnect, write 45 to 1.txt, then content of 1.txt in pc1 is 123, content of 1.txt in pc2 is 12345 3. PC2 network disconnect, but PC1 network is good, write 67 to 1.txt, then content of 1.txt in pc1 is 12367, content of 1.txt in pc1 is 12345 4. so split brain occur is this a bug or design this? The steps you have described is exactly how data split-brain occurs. how glusterfs avoid this? Have some ways to solve? this is my questions. thank you As of today, glusterfs gives EIO (input/output error) when you try to access a split-brained file. You need to resolve the split-brain [1] before the file becomes accessible again. If you want to *avoid* split-brain, you need to enable quorum [2]. [1] https://github.com/gluster/glusterfs/blob/master/doc/split-brain.md [2] https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.1/html/Administration_Guide/ch10s10.html https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.0/html/Administration_Guide/sect-User_Guide-Managing_Volumes-Quorum.html Hope this helps. everybody_en...@163.com ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] update-link-count-parent POSIX xlator parameter
Hi, I recently came across this when I was looking for various ways to convert GFID to Path[1]. I have tested build-pgfid option for basic sanity. It's documented in the commit msg of change[2]. Found one small issue[3]. There could be others. Users should be aware that these xattrs generated only for newly created dirs/files and are not built for already existing dirs/files. [1]: https://github.com/prashanthpai/sof-object-listing/blob/master/changelog/gfid-to-path.md [2]: http://review.gluster.org/5951 [3]: http://review.gluster.org/8352 Regards, -Prashanth Pai - Original Message - From: Harshavardhana har...@harshavardhana.net To: Ben England bengl...@redhat.com Cc: gluster-devel gluster-devel@gluster.org Sent: Thursday, August 21, 2014 2:57:25 AM Subject: Re: [Gluster-devel] update-link-count-parent POSIX xlator parameter On Wed, Aug 20, 2014 at 1:55 PM, Ben England bengl...@redhat.com wrote: What is update-link-count-parent POSIX xlator parameter for? Is it ever set by anyone and why? It appears to be off by default. Didn't see this documented, but the log message in posix.c says: update-link-count-parent is enabled. Thus for each file an extended attribute representing the number of hardlinks for that file within the same parent directory is set. Why would this be necessary? It was supposed to be used by Quota or it uses it internally i am not sure for ancestry paths and gfid to path conversion - AFAIK # gluster volume set volname build-pgfid on Enables this feature. Never tested it personally. -- Religious confuse piety with mere ritual, the virtuous confuse regulation with outcomes ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
