glusterfs.git/xlators/mgmt/glusterd/src/glusterd-volgen.c, branch v3.7.0beta1

tiering: skip CTR-xlator and config options when disabled

2015-04-26T14:35:34+00:00

When compiling with --disable-tiering, GlusterD should not contain any
references to the ChangeTimeRecorder xlator or any of the data tiering
options.

Cherry picked from commit a675ab96b917fc48fc3d7ca035590ebd7cf102bd:
> BUG: 1213125
> Change-Id: Idb46fb80f0ca8b66115e06841d9ec15ba14c24a0
> Signed-off-by: Niels de Vos 
> Reviewed-on: http://review.gluster.org/10296
> Reviewed-by: Dan Lambright 
> Tested-by: Gluster Build System 

BUG: 1215382
Change-Id: Idb46fb80f0ca8b66115e06841d9ec15ba14c24a0
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/10378
Tested-by: Gluster Build System 
Reviewed-by: Dan Lambright

bitrot/glusterd: Scrubber should not crawl bricks if bitrot is not enable

2015-04-13T08:43:52+00:00

If user create multiple volume and user enable bitrot only for few
volume then scrubber should not crawl bricks of volume on which bitrot
is not enable.
Fix is while volfile generation check whether bitrot is enable on that
particular volume or not. If bitrot is enable then only it add bricks of
that volume in scrubber volfile.

Change-Id: I53687c8e1acb39f8e4a712028b73f0b7006122b9
BUG: 1207547
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/10190
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Reviewed-by: Venky Shankar 
Tested-by: Venky Shankar

glusterd: Support distributed replicated volumes on hot tier

2015-04-08T07:28:21+00:00

We did not set up the graph properly for hot tiers with replicated
subvolumes. Also add check that the file has not already been moved
by another replicated brick on the same node.

Change-Id: I9adef565ab60f6774810962d912168b77a6032fa
BUG: 1206517
Signed-off-by: Dan Lambright 
Reviewed-on: http://review.gluster.org/10054
Reviewed-by: Joseph Fernandes 
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY

Avoid conflict between contrib/uuid and system uuid

2015-04-04T17:48:35+00:00

glusterfs relies on Linux uuid implementation, which
API is incompatible with most other systems's uuid. As
a result, libglusterfs has to embed contrib/uuid,
which is the Linux implementation, on non Linux systems.
This implementation is incompatible with systtem's
built in, but the symbols have the same names.

Usually this is not a problem because when we link
with -lglusterfs, libc's symbols are trumped. However
there is a problem when a program not linked with
-lglusterfs will dlopen() glusterfs component. In
such a case, libc's uuid implementation is already
loaded in the calling program, and it will be used
instead of libglusterfs's implementation, causing
crashes.

A possible workaround is to use pre-load libglusterfs
in the calling program (using LD_PRELOAD on NetBSD for
instance), but such a mechanism is not portable, nor
is it flexible. A much better approach is to rename
libglusterfs's uuid_* functions to gf_uuid_* to avoid
any possible conflict. This is what this change attempts.

BUG: 1206587
Change-Id: I9ccd3e13afed1c7fc18508e92c7beb0f5d49f31a
Signed-off-by: Emmanuel Dreyfus 
Reviewed-on: http://review.gluster.org/10017
Tested-by: Gluster Build System 
Reviewed-by: Niels de Vos

cli/glusterd: CLI interface for BitRot detection

2015-03-24T17:26:15+00:00

* BitRot enable/disable CLI per volume
* Volfile generation for Scrubber
* Relevant glusterd infrastructure

Change-Id: I1212af63f93ecc52b22ee6da920e1664f66a1e39
BUG: 1170075
Original-Author: Raghavendra Bhat 
Original-Author: Venky Shankar 
Original-Author: Gaurav Kumar Garg 
Original-Author: Anand Nekkunti 
Reviewed-on: http://review.gluster.org/9986
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

mgmt/glusterd: generate volfile for BitD

2015-03-24T14:56:32+00:00

* Implement the skeleton of bit-rot xlator.

Original-Author: Raghavendra Bhat 
Signed-off-by: Venky Shankar 
Signed-off-by: Gaurav Kumar Garg 
Signed-off-by: Anand Nekkunti 
Change-Id: If33218bdc694f5f09cb7b8097c4fdb74d7a23b2d
BUG: 1170075
Reviewed-on: http://review.gluster.org/9710
Reviewed-by: Vijay Bellur 
Tested-by: Vijay Bellur

read-only: read-only/worm translator should be in brick graph by default

2015-03-24T13:53:11+00:00

Problem:
read-only/worm translator is not loaded by default in brick graph because of which
when read-only option is set through volume set volume still remains writable
untill the bricks are restarted as the translator does not have an inmemory flag
to decide whether the read-only/worm option is turned or not.

Solution:
read-only/worm should be loaded by default in brick graph and the read-only/worm
option can be toggled through volume set command. read-only/worm translator now'
has an in-memory flag to decide whether the volume is read-only or not and based
on that either reject the fop or proceed.

Change-Id: Ic79328698f6a72c50433cff15ecadb1a92acc643
BUG: 1134822
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/8571
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