glusterfs.git/configure.ac, branch v3.7.0beta1

build: configure: automake defaults to max filename length=99 chars

2015-04-28T04:58:20+00:00

automake's default rule for making tar files invokes tar with options
to use Unix V7 tar file format, which has a maximum FQ pathname length
of 99 characters. Some of the new tests in .../tests/bugs/... have names
that are longer than 99 chars. These files are dropped from the dist
tarfile.

automake can be configured to use a newer (POSIX 2001) tar format that
does not have limits on the length of file names.

Change-Id: I8c178880ebce7d83277ba2ee133f161036958785
BUG: 1215488
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/10393
Tested-by: NetBSD Build System
Tested-by: Gluster Build System 
Reviewed-by: Justin Clift 
Reviewed-by: Niels de Vos

build: correct the version in glusterfs-api.pc

2015-04-24T11:49:41+00:00

The version in glusterfs-api.pc has moved backwards, breaking existing
versioned dependencies in QEMU. The following table contains the
GlusterFS version and the version for glusterfs-api.pc:

    .------------------------.
    | GlusterFS | pkg-config |
    |-----------+------------|
    |   3.4.x   |   4.3.4.x  |
    |   3.5.x   |   6.3.5.x  |
    |   3.6.x   |   7.3.6.x  |
    |   3.7.x   |   7.3.7.x  |
    |   master  |   7.x.y.z  |
    '------------------------'

BUG: 1211837
Change-Id: I62168a0ab4f0c78e61987371ae75a0d2dd56ced8
URL: http://thread.gmane.org/gmane.comp.emulators.qemu/330176
Reported-by: Andreas Färber 
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/10309
Reviewed-by: Kaleb KEITHLEY 
Tested-by: NetBSD Build System
Reviewed-by: Vijay Bellur 
Tested-by: Vijay Bellur

configure.ac: print yes/no instead of 1/0 in output

2015-04-13T05:38:24+00:00

POSIX_ACLS support in output of configure shows
0/1 instead of no/yes.

Added BUILD_POSIX_ACLS to make value consistent.

Change-Id: Ife728d0d03ff0eb03d4389fefc04507a76205ccd
BUG: 1185654
Signed-off-by: Raghavendra Talur 
Reviewed-on: http://review.gluster.org/9848
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Niels de Vos 
Tested-by: NetBSD Build System

build: make contrib/uuid dependency optional

2015-04-10T11:39:52+00:00

On Linux systems we should use the libuuid from the distribution and not
bundle and statically link the contrib/uuid/ bits.

libglusterfs/src/compat-uuid.h has been introduced and should become an
abstraction layer for different UUID APIs. Non-Linux operating systems
should implement their compatibility layer there.

Once all operating systems have an implementation in compat-uuid.h, we
can remove contrib/uuid/ from the repository completely.

Change-Id: I345e5357644be2521685e00358bb8c83c4ea0577
BUG: 1206587
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/10129
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

build: require cmocka >= 1.0.1

2015-03-31T11:11:17+00:00

Our mem-pool unit test does a funky realloc(ptr, 0) as an alternative to
free(ptr). cmocka 1.0.0 has a bug where this is not handled correctly
and thinks to detect a memory leak. The next cmocka release will have
this bug fixed, making our unit tests require cmocka >= 1.0.1.

URL: https://cmocka.org/archive/cmocka/2015-02/0000059.html
Change-Id: I3d7f9b4cf7ace3f958158425ecbcc8f176579122
BUG: 1067059
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/9801
Tested-by: Gluster Build System 
Reviewed-by: Andreas Schneider 
Tested-by: Andreas Schneider 
Reviewed-by: Kaleb KEITHLEY

build:change dependency for librdmacm to version >= 1.0.15

2015-03-30T16:45:10+00:00

Thanks to Niels for the fix

Change-Id: I0954b6f498461dde2b986da9e0e45775175249c9
BUG: 1206744
Signed-off-by: Mohammed Rafi KC 
Reviewed-on: http://review.gluster.org/10028
Reviewed-by: Niels de Vos 
Reviewed-by: Humble Devassy Chirammal 
Reviewed-by: Kaleb KEITHLEY 
Tested-by: Gluster Build System

features/bit-rot: Implementation of bit-rot xlator

2015-03-24T17:55:32+00:00

This is the "Signer" -- responsible for signing files with their
checksums upon last file descriptor close (last release()).
The event notification facility provided by the changelog xlator
is made use of.

Moreover, checksums are as of now SHA256 hash of the object data
and is the only available hash at this point of time. Therefore,
there is no special "what hash to use" type check, although it's
does not take much to add various hashing algorithms to sign
objects with. Signatures are stored in extended attributes of the
objects along with the the type of hashing used to calculate the
signature. This makes thing future proof when other hash types
are added. The signature  infrastructure is provided by bitrot
stub: a little piece of code that sits over the POSIX xlator
providing interfaces to "get or set" objects signature and it's
staleness.

Since objects are signed upon receiving release() notification,
pre-existing data which are "never" modified would never be
signed. To counter this, an initial crawler thread is spawned
The crawler scans the entire brick for objects that are unsigned
or "missed" signing due to the server going offline (node reboots,
crashes, etc..) and triggers an explicit sign. This would also
sign objects when bit-rot is enabled for a volume and/or after
upgrade.

Change-Id: I1d9a98bee6cad1c39c35c53c8fb0fc4bad2bf67b
BUG: 1170075
Original-Author: Raghavendra Bhat 
Signed-off-by: Venky Shankar 
Reviewed-on: http://review.gluster.org/9711
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

Bitrot Stub

2015-03-24T13:37:19+00:00

Bitrot stub implements object versioning required for identifying
signature freshness. More details about versioning is explained
as a part of the "bitrot feature documentation" patch.

Change-Id: I2ad70d9eb109ba4a12148ab8d81336afda529ad9
BUG: 1170075
Signed-off-by: Venky Shankar 
Reviewed-on: http://review.gluster.org/9709
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

features/shard: Introducing sharding translator

2015-03-19T17:59:31+00:00

Based on the high-level design by Anand V. Avati which can be found @
https://gist.github.com/avati/af04f1030dcf52e16535#sharding-xlator-stripe-20

Still to-do:
        * complete implementation of inode write fops - [f]truncate,
          zerofill, fallocate, discard
        * introduce transaction mechanism in inode write fops
        * complete readv
        * Handle open with O_TRUNC
        * Handle unlinking of all shards during unlink/rename
        * Compute total ia_size and ia_blocks in lookup, readdirp, etc
        * wind fsync/flush on all shards

        Note: Most of the items above are related. Once we come up
        with a clean way to determine the last shard/shard count for
        a file/file size and the mgmt of sparse regions of the file,
        implementing them becomes trivial.

Change-Id: Id871379b53a4a916e4baa2e06f197dd8c0043b0f
BUG: 1200082
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/9841
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

afr: arbiter xlator

2015-03-19T17:45:49+00:00

This patch adds the arbiter translator into the tree. This is a server
side xlator used for replica 3 volumes. It sits above posix and will be
loaded on the 3rd (last) brick of every afr subvolume in a replica 3
configuration. It intercepts inode read/write operations: reads are
unwound with ENOTCONN, inode writes are unwound with success without
actually passing them down to posix. Metadata operations are allowed to
pass through.

The CLI for creating a 3 way replica with arbiter is also added but kept
disabled (A 'normal' 3 way replica is created instead).

This patch is a part of the arbiter logic implementation for 3 way AFR,
details of which can be found at http://review.gluster.org/#/c/9656/

Change-Id: I395b81f49d5da52c466daf5c8518f1bbad9c16fa
BUG: 1199985
Signed-off-by: Ravishankar N 
Reviewed-on: http://review.gluster.org/9840
Tested-by: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri 
Reviewed-by: Vijay Bellur