glusterfs-quota.git/xlators, branch master

cli,glusterd: Task parameters in xml output

2013-09-13T10:38:04+00:00

This patch introduces task parameters for the asynchronus task shown in
volume status. The parameters are only given for xml output. The
parameters shown currently are,
- source and destination bricks for replace-brick tasks
  ......
        
          
            Replace brick
            3d1a1005-9d2e-4ae0-bd62-577bc1d333a3
            1
            
              archm:/export/test4
              archm:/export/test-replace1
            
          
        
  ......
- list of bricks being removed for remove-brick tasks
  ......
        
          
            Remove brick
            901c20ca-0da2-41de-8669-5f0caca6b846
            1
            
              archm:/export/test2
              archm:/export/test3
            
          
        
  ......

The changes for non-xml output will be done in a subsequent patch.

Change-Id: I322afe2f83ed8adeddb99f7962c25911204dc204
BUG: 916577
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.org/5771
Reviewed-by: Vijay Bellur 
Tested-by: Vijay Bellur

qemu-block: fix building from distribution tarball when glib2-devel is installed

2013-09-12T20:45:40+00:00

Building RPMs from a 'make dist' tarball fails when qemu-block is
enabled. Enabling is done automatically when the glib2 development files
are available (enabled by ./configure).

Manual building with:

  $ ./autogen.sh && ./configure && make dist && rpmbuild -ta *.tar.gz

Building in mock works fine, glib2-devel is not installed by default so
the qemu-block xlator gets disabled. This change also adds glib2-devel
to the BuildRequires in the glusterfs.spec file, causing the qemu-block
xlator to be built by default, and included in the glusterfs RPM.

Change-Id: Ibb73628772586d9e07bbfde7a8ff2fc973489086
BUG: 986775
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/5896
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

mgmt/glusterd: Update sub_count on remove brick

2013-09-12T05:51:36+00:00

Change-Id: I7c17de39da03c6b2764790581e097936da406695
BUG: 1002556
Signed-off-by: Vijay Bellur 
Reviewed-on: http://review.gluster.org/5893
Tested-by: Gluster Build System 
Reviewed-by: Krishnan Parthasarathi 
Reviewed-by: Anand Avati

rpc/rpc-lib: rpcsvc should reply when rpc_err is set

2013-09-11T19:32:33+00:00

Problem:
When requests are received on a connection before setvolume
is done, creating frame from the requests fail because there is
no association of the transport with the conn(i.e. xl_private).
xl_private is set only on set_volume. In such cases error response
is not sent from server xlator to that request because of which
operations on mount point are hanging.

Fix:
Set actor return value to RPCSVC_ACTOR_ERROR so that response is sent
even in these cases.

Change-Id: I74d7bc6849fde6c734008d67c1f4bc9d9f7a84f9
BUG: 1006367
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/5892
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

glusterd: Allow bumping down a peer's op-version during probe

2013-09-10T16:07:56+00:00

Earlier, a peer running a higher op-version couldn't be probed into a
cluster running at a lower op-version. This created issues when trying
to expand an upgraded cluster. This patch changes this behaviour.

The cluster no longer rejects a peer being probed if its op-version is
higher than the cluster op-version. The peer will reduce its op-version
if it doesn't have any volumes. If the peer contains volumes and needs
to reduce its op-version, it fails the handshake and the probe fails.

Change-Id: I12c6c873922799e1557b7184e956baea643d0dea
BUG: 1005038
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.org/5715
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: Added missing MY_UUID conversion in gsync staging

2013-09-10T10:41:16+00:00

Change-Id: Ia4bf607e044d50636fb0a599a2ff91059f5b17aa
BUG: 1006177
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/5887
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cluster/dht: assign layout onto missing directories too

2013-09-09T21:58:09+00:00

The current self-healing algorithm is ignoring missing directories
for assigning new layout. When lookup() is racing against mkdir()
or when self-healing a half-done mkdir(), the layout assignment split
must happen based on the final number of directories, and not the
currently existing number of directories (because we finish mkdir()
of missing directories before hash layout assignment).

Without this fix, concurrent mkdir() and lookup() will step on
each others feet, create a messed up layout on disk, and end up
with different in-memory layouts.

Once two clients have different in-memory layouts, creation of
subdirectory will not arbitrate on the same hashed subvolume and will
result in GFID mismatch of the sub-directory.

Change-Id: Ia47acad67c265060405984c822b4d37512b9dbb3
BUG: 907072
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.org/5849
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Peter Portante 
Tested-by: Peter Portante

glusterfsd: Round robin DNS should not be relied upon with

2013-09-06T22:56:34+00:00

config service availability for clients.

Backupvolfile server as it stands is slow and prone to errors
with mount script and its combination with RRDNS. Instead in
theory it should use all the available nodes in 'trusted pool'
by default (Right now we don't have a mechanism in place for
this)

Nevertheless this patch provides a scenario where a list of
volfile-server can be provided on command as shown below

-----------------------------------------------------------------
$ glusterfs -s server1 .. -s serverN --volfile-id= \
      
-----------------------------------------------------------------
                   OR
-----------------------------------------------------------------
$ mount -t glusterfs -obackup-volfile-servers=: \
      :...: :/ 
-----------------------------------------------------------------

Here ':' is used as a separator for mount script parsing

Now these will be remembered and recursively attempted for
fetching vol-file until exhausted. This would ensure that the
clients get 'volume' configs in a consistent manner avoiding the
need to poll through RRDNS.

Change-Id: If808bb8a52e6034c61574cdae3ac4e7e83513a40
BUG: 986429
Signed-off-by: Harshavardhana 
Reviewed-on: http://review.gluster.org/5400
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

gfid-access: Error logs for ga_newfile_parse_args

2013-09-05T09:33:18+00:00

Change-Id: I7aab98a70793bee936272f0b795f4c22c3733dd2
BUG: 1001055
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/5705
Tested-by: Gluster Build System 
Tested-by: Venky Shankar 
Reviewed-by: Amar Tumballi

gsyncd / geo-rep: "disjoint" cascading geo-replication sessions

2013-09-05T03:49:12+00:00

Slave's xtime is now stored on the master itself (and that too only on
the root), which implies it cannot be propogated to the cascaded slave.
Thus the intermediate master now makes use of it's own volume information
to propogate volume-mark and xtime.

On starting Geo-Replication "geo-replication.ignore-pid-check" marker
option is enabled, which is an override for the client-pid check in
marker. This options triggers marker update only for geo-replication
auxillary mount (client-pid == -1). Since gsyncd not does setxattr()
directly on the bricks, this option won't trigger a chain of spurious
metadata updates that would need to be processed by gsyncd.

Change-Id: If50c5ef275dfb6b4ff4fd35be2565587e2fdf3e1
BUG: 996371
Original Author: Venky Shankar 
Signed-off-by: Venky Shankar 
Reviewed-on: http://review.gluster.org/5592
Tested-by: Gluster Build System 
Reviewed-by: Avra Sengupta 
Tested-by: Avra Sengupta 
Reviewed-by: Anand Avati