Contributors FAQ

From GlusterDocumentation

1 How do I checkout the source?
2 How to write a GlusterFS translator?
3 How to write a GlusterFS scheduler?
4 How to submit a bug?
5 How to submit a patch?
6 How to debug GlusterFS?
7 How to be in touch?

How do I checkout the source?

GNU Arch Source Repository

$ tla register-archive http://arch.savannah.gnu.org/archives/gluster/
$ tla get -A gluster@sv.gnu.org glusterfs--mainline--BRANCH glusterfs

After getting the source, do the following so that you wont violate the namespace of tla.

$ cd glusterfs
$ ./autogen.sh    
$ mkdir build
$ cd build
$ ../configure # may be some options, if required
$ make install > /dev/null

So, by maintaining a seperate build directory, for further checkouts you can do just

$ tla update

Also few 'tla' commands which may help you

$ tla changelog | less   # checkout the changelog of the latest patch
$ tla tree-id            # shows latest patch number

See Gluster Download Page for latest branch-id.

[edit]

How to write a GlusterFS translator?

Copy the xlators/debug/trace translator and start replacing the file system operations that are specific to your translator only. Unmodified functions when deleted, will be set to default files system operations automatically.

[edit]

How to write a GlusterFS scheduler?

random is a simple enough translator to understand and start with.

[edit]

How to submit a bug?

File a bug report at https://savannah.nongnu.org/bugs/?group=gluster Please include trace file, hardware configuration, OS version, client/server volume spec files and info about how to reproduce the bug.

[edit]

How to submit a patch?

# diff -pruN glusterfs glusterfs-hacked > glusterfs-$VERSION-$PATCH_NAME

Mail the patch as inline mail message to gluster-devel mailing-list with subject: [PATCH: glusterfs] actual subject. Include Changelog contents in the body and not in patch.

[edit]

How to debug GlusterFS?

GlusterFS debug/trace translator when enabled provides a very detailed log of all internal operations with complete decoding of values. If you still can't locate the bug, you can try GNU gdb and debug GlusterFS code like any other application. GlusterFS runs entirely in user-space.

[edit]