Re: [Gluster-devel] FS Sanity daily results.
On 07/06/2014 07:58 PM, Pranith Kumar Karampuri wrote: On 07/06/2014 02:53 AM, Benjamin Turner wrote: Hi all. I have been running FS sanity on daily builds(glusterfs mounts only at this point) for a few days for a few days and I have been hitting a couple of problems: final pass/fail report = Test Date: Sat Jul 5 01:53:00 EDT 2014 Total : [44] Passed: [41] Failed: [3] Abort : [0] Crash : [0] - [ PASS ] FS Sanity Setup [ PASS ] Running tests. [ PASS ] FS SANITY TEST - arequal [ PASS ] FS SANITY LOG SCAN - arequal [ PASS ] FS SANITY LOG SCAN - bonnie [ PASS ] FS SANITY TEST - glusterfs_build [ PASS ] FS SANITY LOG SCAN - glusterfs_build [ PASS ] FS SANITY TEST - compile_kernel [ PASS ] FS SANITY LOG SCAN - compile_kernel [ PASS ] FS SANITY TEST - dbench [ PASS ] FS SANITY LOG SCAN - dbench [ PASS ] FS SANITY TEST - dd [ PASS ] FS SANITY LOG SCAN - dd [ PASS ] FS SANITY TEST - ffsb [ PASS ] FS SANITY LOG SCAN - ffsb [ PASS ] FS SANITY TEST - fileop [ PASS ] FS SANITY LOG SCAN - fileop [ PASS ] FS SANITY TEST - fsx [ PASS ] FS SANITY LOG SCAN - fsx [ PASS ] FS SANITY LOG SCAN - fs_mark [ PASS ] FS SANITY TEST - iozone [ PASS ] FS SANITY LOG SCAN - iozone [ PASS ] FS SANITY TEST - locks [ PASS ] FS SANITY LOG SCAN - locks [ PASS ] FS SANITY TEST - ltp [ PASS ] FS SANITY LOG SCAN - ltp [ PASS ] FS SANITY TEST - multiple_files [ PASS ] FS SANITY LOG SCAN - multiple_files [ PASS ] FS SANITY TEST - posix_compliance [ PASS ] FS SANITY LOG SCAN - posix_compliance [ PASS ] FS SANITY TEST - postmark [ PASS ] FS SANITY LOG SCAN - postmark [ PASS ] FS SANITY TEST - read_large [ PASS ] FS SANITY LOG SCAN - read_large [ PASS ] FS SANITY TEST - rpc [ PASS ] FS SANITY LOG SCAN - rpc [ PASS ] FS SANITY TEST - syscallbench [ PASS ] FS SANITY LOG SCAN - syscallbench [ PASS ] FS SANITY TEST - tiobench [ PASS ] FS SANITY LOG SCAN - tiobench [ PASS ] FS Sanity Cleanup [ FAIL ] FS SANITY TEST - bonnie [ FAIL ] FS SANITY TEST - fs_mark [ FAIL ] /rhs-tests/beaker/rhs/auto-tests/components/sanity/fs-sanity-tests-v2 Bonnie++ is just very slow(running for 10+ hours on 1 16 GB file) and FS mark has been failing. The bonnie slowness is in re read, here is the best explanation I can find on it: https://blogs.oracle.com/roch/entry/decoding_bonnie *Rewriting...done* This gets a little interesting. It actually reads 8K, lseek back to the start of the block, overwrites the 8K with new data and loops. (see article for more.). On FS mark I am seeing: # fs_mark -d . -D 4 -t 4 -S 5 # Version 3.3, 4 thread(s) starting at Sat Jul 5 00:54:00 2014 # Sync method: POST: Reopen and fsync() each file in order after main write loop. # Directories: Time based hash between directories across 4 subdirectories with 180 seconds per subdirectory. # File names: 40 bytes long, (16 initial bytes of time stamp with 24 random bytes at end of name) # Files info: size 51200 bytes, written with an IO size of 16384 bytes per write # App overhead is time in microseconds spent in the test not doing file writing related system calls. FSUse%Count SizeFiles/sec App Overhead Error in unlink of ./00/53b784e8SKZ0QS9BO7O2EG1DIFQLRDYY : No such file or directory fopen failed to open: fs_log.txt.26676 fs-mark pass # 5 failed I am working on reporting so look for a daily status report email from my jenkins server soon. How do we want to handle failures like this moving forward? Should I just open a BZ after I triage? Do you guys do a new BZ for every failure in the normal regressions tests? Yes bz would be great with all the logs. For spurious regressions at least I just opened one bz and fixed all the bugs reported by Justin against that one. Ben, Did you get a chance to raise the bug? Pranith Pranith -b ___ 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] regarding spurious failure tests/bugs/bug-1112559.t
In the test case, we are checking gluster snap status to see if all the bricks are alive. One of the snap bricks fail to start up, and hence we see the failure. The brick fails to bind with Address already in use error. But if we see clearly that same log also says binding to failed, where the address is missing. So it might be trying to bind to the wrong(or empty) address. Following are the brick logs for the same: [2014-07-07 11:20:15.662573] I [rpcsvc.c:2142:rpcsvc_set_outstanding_rpc_limit] 0-rpc-service: Configured rpc.outstanding-rpc-limit with value 64 [2014-07-07 11:20:15.662634] W [options.c:898:xl_opt_validate] 0-ad94478591fc41648c9674b10143e3d2-server: option 'listen-port' is deprecated, preferred is 'transport.socket.listen-port', continuing with correction [2014-07-07 11:20:15.662758] E [socket.c:710:__socket_server_bind] 0-tcp.ad94478591fc41648c9674b10143e3d2-server: binding to failed: Address already in use [2014-07-07 11:20:15.662776] E [socket.c:713:__socket_server_bind] 0-tcp.ad94478591fc41648c9674b10143e3d2-server: Port is already in use [2014-07-07 11:20:15.662795] W [rpcsvc.c:1531:rpcsvc_transport_create] 0-rpc-service: listening on transport failed [2014-07-07 11:20:15.662810] W [server.c:920:init] 0-ad94478591fc41648c9674b10143e3d2-server: creation of listener failed [2014-07-07 11:20:15.662821] E [xlator.c:425:xlator_init] 0-ad94478591fc41648c9674b10143e3d2-server: Initialization of volume 'ad94478591fc41648c9674b10143e3d2-server' failed, review your volfile again [2014-07-07 11:20:15.662836] E [graph.c:322:glusterfs_graph_init] 0-ad94478591fc41648c9674b10143e3d2-server: initializing translator failed [2014-07-07 11:20:15.662847] E [graph.c:525:glusterfs_graph_activate] 0-graph: init failed [2014-07-07 11:20:15.664283] W [glusterfsd.c:1182:cleanup_and_exit] (-- 0-: received signum (0), shutting down Regards, Avra On 07/08/2014 11:28 AM, Joseph Fernandes wrote: Hi Pranith, I am looking into this issue. Will keep you posted on the process by EOD Regards, ~Joe - Original Message - From: Pranith Kumar Karampuri pkara...@redhat.com To: josfe...@redhat.com Cc: Gluster Devel gluster-devel@gluster.org, Rajesh Joseph rjos...@redhat.com, Sachin Pandit span...@redhat.com, aseng...@redhat.com Sent: Monday, July 7, 2014 8:42:24 PM Subject: Re: [Gluster-devel] regarding spurious failure tests/bugs/bug-1112559.t On 07/07/2014 06:18 PM, Pranith Kumar Karampuri wrote: Joseph, Any updates on this? It failed 5 regressions today. http://build.gluster.org/job/rackspace-regression-2GB/541/consoleFull http://build.gluster.org/job/rackspace-regression-2GB-triggered/175/consoleFull http://build.gluster.org/job/rackspace-regression-2GB-triggered/173/consoleFull http://build.gluster.org/job/rackspace-regression-2GB-triggered/166/consoleFull http://build.gluster.org/job/rackspace-regression-2GB-triggered/172/consoleFull One more : http://build.gluster.org/job/rackspace-regression-2GB/543/console Pranith CC some more folks who work on snapshot. Pranith On 07/05/2014 11:19 AM, Pranith Kumar Karampuri wrote: hi Joseph, The test above failed on a documentation patch, so it has got to be a spurious failure. Check http://build.gluster.org/job/rackspace-regression-2GB-triggered/150/consoleFull for more information Pranith ___ 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] regarding spurious failure tests/bugs/bug-1112559.t
Adding rhs-gabbar On 07/08/2014 01:54 PM, Avra Sengupta wrote: In the test case, we are checking gluster snap status to see if all the bricks are alive. One of the snap bricks fail to start up, and hence we see the failure. The brick fails to bind with Address already in use error. But if we see clearly that same log also says binding to failed, where the address is missing. So it might be trying to bind to the wrong(or empty) address. Following are the brick logs for the same: [2014-07-07 11:20:15.662573] I [rpcsvc.c:2142:rpcsvc_set_outstanding_rpc_limit] 0-rpc-service: Configured rpc.outstanding-rpc-limit with value 64 [2014-07-07 11:20:15.662634] W [options.c:898:xl_opt_validate] 0-ad94478591fc41648c9674b10143e3d2-server: option 'listen-port' is deprecated, preferred is 'transport.socket.listen-port', continuing with correction [2014-07-07 11:20:15.662758] E [socket.c:710:__socket_server_bind] 0-tcp.ad94478591fc41648c9674b10143e3d2-server: binding to failed: Address already in use [2014-07-07 11:20:15.662776] E [socket.c:713:__socket_server_bind] 0-tcp.ad94478591fc41648c9674b10143e3d2-server: Port is already in use [2014-07-07 11:20:15.662795] W [rpcsvc.c:1531:rpcsvc_transport_create] 0-rpc-service: listening on transport failed [2014-07-07 11:20:15.662810] W [server.c:920:init] 0-ad94478591fc41648c9674b10143e3d2-server: creation of listener failed [2014-07-07 11:20:15.662821] E [xlator.c:425:xlator_init] 0-ad94478591fc41648c9674b10143e3d2-server: Initialization of volume 'ad94478591fc41648c9674b10143e3d2-server' failed, review your volfile again [2014-07-07 11:20:15.662836] E [graph.c:322:glusterfs_graph_init] 0-ad94478591fc41648c9674b10143e3d2-server: initializing translator failed [2014-07-07 11:20:15.662847] E [graph.c:525:glusterfs_graph_activate] 0-graph: init failed [2014-07-07 11:20:15.664283] W [glusterfsd.c:1182:cleanup_and_exit] (-- 0-: received signum (0), shutting down Regards, Avra On 07/08/2014 11:28 AM, Joseph Fernandes wrote: Hi Pranith, I am looking into this issue. Will keep you posted on the process by EOD Regards, ~Joe - Original Message - From: Pranith Kumar Karampuri pkara...@redhat.com To: josfe...@redhat.com Cc: Gluster Devel gluster-devel@gluster.org, Rajesh Joseph rjos...@redhat.com, Sachin Pandit span...@redhat.com, aseng...@redhat.com Sent: Monday, July 7, 2014 8:42:24 PM Subject: Re: [Gluster-devel] regarding spurious failure tests/bugs/bug-1112559.t On 07/07/2014 06:18 PM, Pranith Kumar Karampuri wrote: Joseph, Any updates on this? It failed 5 regressions today. http://build.gluster.org/job/rackspace-regression-2GB/541/consoleFull http://build.gluster.org/job/rackspace-regression-2GB-triggered/175/consoleFull http://build.gluster.org/job/rackspace-regression-2GB-triggered/173/consoleFull http://build.gluster.org/job/rackspace-regression-2GB-triggered/166/consoleFull http://build.gluster.org/job/rackspace-regression-2GB-triggered/172/consoleFull One more : http://build.gluster.org/job/rackspace-regression-2GB/543/console Pranith CC some more folks who work on snapshot. Pranith On 07/05/2014 11:19 AM, Pranith Kumar Karampuri wrote: hi Joseph, The test above failed on a documentation patch, so it has got to be a spurious failure. Check http://build.gluster.org/job/rackspace-regression-2GB-triggered/150/consoleFull for more information Pranith ___ 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 ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-users] RPM's for latest glusterfs does not install on Fedora-20
On 2014-07-07 21:13, Niels de Vos wrote: On Mon, Jul 07, 2014 at 07:29:15PM +0200, Anders Blomdell wrote: On 2014-07-07 18:17, Niels de Vos wrote: On Mon, Jul 07, 2014 at 04:48:18PM +0200, Anders Blomdell wrote: On 2014-07-07 15:08, Lalatendu Mohanty wrote: # rpm -U ./glusterfs-server-3.5qa2-0.722.git2c5eb5c.fc20.x86_64.rpm ./glusterfs-fuse-3.5qa2-0.722.git2c5eb5c.fc20.x86_64.rpm ./glusterfs-cli-3.5qa2-0.722.git2c5eb5c.fc20.x86_64.rpm ./glusterfs-libs-3.5qa2-0.722.git2c5eb5c.fc20.x86_64.rpm ./glusterfs-3.5qa2-0.722.git2c5eb5c.fc20.x86_64.rpm ./glusterfs-api-3.5qa2-0.722.git2c5eb5c.fc20.x86_64.rpm error: Failed dependencies: libgfapi.so.0()(64bit) is needed by (installed) qemu-common-2:1.6.2-6.fc20.x86_64 libgfapi.so.0()(64bit) is needed by (installed) qemu-system-x86-2:1.6.2-6.fc20.x86_64 libgfapi.so.0()(64bit) is needed by (installed) qemu-img-2:1.6.2-6.fc20.x86_64 Feature or bug? /Anders Hey Anders, You should not see this issue as glusterfs-api provides /usr/lib64/libgfapi.so.0 . $rpm -ql glusterfs-api /usr/lib/python2.7/site-packages/gluster/__init__.py /usr/lib/python2.7/site-packages/gluster/__init__.pyc /usr/lib/python2.7/site-packages/gluster/__init__.pyo /usr/lib/python2.7/site-packages/gluster/gfapi.py /usr/lib/python2.7/site-packages/gluster/gfapi.pyc /usr/lib/python2.7/site-packages/gluster/gfapi.pyo /usr/lib/python2.7/site-packages/glusterfs_api-3.5.0-py2.7.egg-info /usr/lib64/glusterfs/3.5.0/xlator/mount/api.so /usr/lib64/libgfapi.so.0 /usr/lib64/libgfapi.so.0.0.0 True for branch release-3.5 from git://git.gluster.org/glusterfs.git, but not for master. Indeed, the master branch uses SONAME-versioning. Any applications (like qemu) using libgfapi.so need to get re-compiled to use the update. Can do without these for my current testing :-) Of course, removing packages you don't need is a nice workaround :) Is there any specific reason you want to use glusterfs-server-3.5qa2-0.722.git2c5eb5c.fc20.x86_64.rpm? because 3.5.1 is available in fedora 20 in update repo . So if you do yum update it i.e. yum update glusterfs-server you should get glusterfs 3.5.1 GA version which like to be stable than glusterfs-server-3.5qa2-0.722. I would like to track progress of the fixing of my bugs and at the same time experiment with reverting 3dc56cbd16b1074d7ca1a4fe4c5bf44400eb63ff to re-add IPv6 support, and I figured that the master is what will eventually become 3.6.0 Yes, you are correct. The master branch will become glusterfs-3.6. You should be able to recompile qemu (and other?) packages on a system that has glusterfs-devel-3.6 installed. I can also recommend the use of 'mockchain' (from the 'mock' package) for rebuilding glusterfs and other dependent packages. I'll keep tracking master (exposing as many bugs as I can), I'll redirect followups to gluster-devel@gluster.org and drop gluster-us...@gluster.org after this message. Great, thanks for the testing! Will hopefully get me a better product in the end :-) A few questions: 1. Should bugs/patches be posted on the list or should I file a BugZilla for each? 2. What are the rules for marking a bug as blocking the trackers (can't find one for 3.6.0 yet, so currently a moot point). 3. Given that my understanding of gluster innards is very limited, my guess is that the 'GlusterFS Development Workflow' is a overkill, but please correct me if I'm wrong. /Anders -- Anders Blomdell Email: anders.blomd...@control.lth.se Department of Automatic Control Lund University Phone:+46 46 222 4625 P.O. Box 118 Fax: +46 46 138118 SE-221 00 Lund, Sweden ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-users] RPM's for latest glusterfs does not install on Fedora-20
On 08/07/2014, at 9:53 AM, Anders Blomdell wrote: snip 2. What are the rules for marking a bug as blocking the trackers (can't find one for 3.6.0 yet, so currently a moot point). We should probably create an alias thing for 3.6.0, like we have for 3.5.2: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.5.2 Not sure who does that, maybe Vijay (CC'd)? + 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] Building rpms for master
It seems like http://www.gluster.org/community/documentation/index.php/CompilingRPMS is missing one crucial step: $ ./autogen.sh $ ./configure --enable-fusermount $ make dist ... $ cd extras/LinuxRPM $ make glusterrpms should be: $ rm -f ./autom4te.cache/* # make sure to use current # './build-aux/pkg-version --release' $ ./autogen.sh $ ./configure --enable-fusermount $ make dist ... $ cd extras/LinuxRPM $ make glusterrpms Otherwise the rpm's wont pick the correct releaseversion, i.e. ./autogen.sh will pickup the result of './build-aux/pkg-version --release' from the cache instead of figure out where HEAD is currently located. Even nicer would be if '(cd extras/LinuxRPM ; make glusterrpms)' did the right thing. /Anders -- Anders Blomdell Email: anders.blomd...@control.lth.se Department of Automatic Control Lund University Phone:+46 46 222 4625 P.O. Box 118 Fax: +46 46 138118 SE-221 00 Lund, Sweden ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] Call for Topics: Gluster Usage and Development
Greetings, At one point earlier this year, we had a good cadence producing online hangouts with Gluster experts: https://www.youtube.com/user/GlusterCommunity/videos There were some really good ones, but we stopped doing them due to resources and time. However, we'd like to relaunch the program, and this time we'll add a social media push and accompanying blog posts for each video. Here are some ideas on things that would be useful to cover: - Gluster performance at scale - GFAPI tips - GlusterFS as object storage backend - Geo-replication - New features coming in 3.6 Here's what I need from you: 1. vote on the topics above. If you don't like the topics, feel free to add one (or a few) 2. nominate experts to cover the above. This could be anyone, from members of the developer team to yourself 3. got tips and tricks you've discovered for your deployment? Please share them by adding your name and topic to the list above. With luck, we can start to produce these once a week and add to the Gluster spotlight that we started at the beginning of the year. Thanks! JM ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-users] Call for Topics: Gluster Usage and Development
- Original Message - On Tue, Jul 8, 2014 at 11:33 AM, John Mark Walker jowal...@redhat.com wrote: Here's what I need from you: 1. vote on the topics above. If you don't like the topics, feel free to add one (or a few) * NSR I would love a session on NSR. Oh Jeff... And AFR2, for that matter. In fact, we could have a great session comparing the two. * SSL +1 * 4.0 Eh... perhaps later. Although it would be good to at some point talk about what may be part of 4.0. Just don't know if it needs to be very soon - can probably wait for some other burning topics. * ARM Could be interesting, but my understanding is that it doesn't require much to be done. * Btrfs Does anyone actually use BtrFS? * Erasure coding Yes, +1. Xavi? And if you have new developments with puppet-gluster, it might be useful to have another session on that. -JM ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Initiative to increase developer participation
On 05/30/2014 01:16 PM, Niels de Vos wrote: snip Documentation in the wiki, mainly these pages: - http://www.gluster.org/community/documentation/index.php/Main_Page#Developers - http://www.gluster.org/community/documentation/index.php/Developers - Over time make these new comers as experienced developers in glusterfs :-) Maintainers, Could you please come up with the initial list of bugs by next Wednesday before community meeting? If we mark bugs with the EasyFix keyword (see below), all bugs can get listed with a simple Bugzilla query: - https://bugzilla.redhat.com/buglist.cgi?bug_status=NEWkeywords=EasyFixproduct=GlusterFS Niels, Could you send out the guideline to mark the bugs as easy fix. Also the wiki link for backports. To mark a bug as Easy to Fix, open the Bug, and add in 'EasyFix' in the 'Keywords' field. Of course, it would help any newcomer if there is a comment on where (i.e. which source file, function) the changes are needed. For example, https://bugzilla.redhat.com/1100204 contains a clear description what is needed, and where. For the stable branches (release-3.4 and release-3.5 in the git repository), it often is needed to 'backport' a change from the current development branch (master). Backporting is for many changes relatively easy and we have started to document the steps here: - http://www.gluster.org/community/documentation/index.php/Backport_Guidelines The Backport Wishlist is a list of patches/bugs that are proposed candidates for backporting. When a backport request has been filed, a bug for this backport and the release-version should be created. Depending on the change, the EasyFix keyword could be set by the person creating the bug (or by a developer or sub-maintainer after a review). snip We have started a page in gluster wiki about easyfix bugs [1]. It contains the initial information for developers who want to fix easy bugs in GlusterFS. [1] http://www.gluster.org/community/documentation/index.php/EasyFix_Bugs Happy hacking!! Thanks, Lala ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] glusterfs-3.4.5beta2 released
SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.4.5beta2.tar.gz This release is made off jenkins-release-80 -- Gluster Build System ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-users] GlusterFS libgfapi
On 07/09/2014 10:09 AM, Viktor Villafuerte wrote: Hi all, On Gluster website I can see section Language bindings for the libgfapi C library for Java/Python/.. However I cannot find any documentation of the interface itself. Are there any docs on how to use libgfapi using C? The api header is relatively well documented [1]. Do let us know if you need more than what is available there. api/examples does contain a sample implementation in C. You can also look up that for reference. Regards, Vijay [1] https://github.com/gluster/glusterfs/blob/master/api/src/glfs.h ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-users] GlusterFS libgfapi
some more bits about libgfapi can be fetched from https://github.com/gluster/glusterfs/blob/master/doc/features/libgfapi.md --Humble On Wed, Jul 9, 2014 at 10:27 AM, Vijay Bellur vbel...@redhat.com wrote: On 07/09/2014 10:09 AM, Viktor Villafuerte wrote: Hi all, On Gluster website I can see section Language bindings for the libgfapi C library for Java/Python/.. However I cannot find any documentation of the interface itself. Are there any docs on how to use libgfapi using C? The api header is relatively well documented [1]. Do let us know if you need more than what is available there. api/examples does contain a sample implementation in C. You can also look up that for reference. Regards, Vijay [1] https://github.com/gluster/glusterfs/blob/master/api/src/glfs.h ___ 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
