glusterfs.git/libglusterfs, branch v3.3.0.5rhs-39

Rebase commit #2

2012-12-12T08:24:00+00:00

Change-Id: Ie983d0b9862cc1401187532ed896e57bd3488e2b
BUG: 871323
Reviewed-on: https://code.engineering.redhat.com/gerrit/1893
Reviewed-by: Vijay Bellur 
Tested-by: Vijay Bellur

core/statedump: statedump enahancements

2012-12-12T05:14:29+00:00

* append timestamp to the statedump filename to prevent old files
  getting over written
* Add start and end markers to statedump to indicate beginning and
  finishing of statedump information
* Make glusterfs take options through /tmp/glusterdump.options file and
  treating those options with higher prioriry
* do not dump the entire inode table in the statedump. Instead just dump
  the ltable and the fdtable

Change-Id: I9a56a5be9970b58d08de509916f88aa2be56d864
Signed-off-by: Raghavendra Bhat 
Reviewed-on: https://code.engineering.redhat.com/gerrit/1861
Reviewed-by: Vijay Bellur 
Tested-by: Vijay Bellur

fuse: make background queue length configurable

2012-12-12T05:14:14+00:00

* also make 'congestion_threshold' an option
* make 'congestion_threshold' as 75% of background queue length if
  not explicitely specified
* in glusterfsd.c, moved all the fuse option dictionary setting
  code to separate function

Change-Id: Ie1680eefaed9377720770a09222282321bd4132e
Signed-off-by: Amar Tumballi 
BUG: 845214
Reviewed-on: https://code.engineering.redhat.com/gerrit/1860
Reviewed-by: Vijay Bellur 
Tested-by: Vijay Bellur

libglusterfs,mount/fuse: implement gidcache mechanism in fuse-bridge

2012-12-12T05:12:01+00:00

This change genericizes the cache mechanism implemented in commit
8efd2845 into libglusterfs/src/gidcache.[ch] and adds fuse-bridge as
a client. The cache mechanism is fundamentally equivalent, with some
minor changes:

  - Change cache key from uid_t to uint64_t.
  - Modify the cache add logic to locate and use an entry with a
    matching ID, should it already exist. This addresses a bug in
    the existing mechanism where an expired entry supercedes a newly
    added entry in lookup, causing repeated adds and flushing of a
    cache bucket.

The fuse group cache is disabled by default. It can be enabled via
the 'gid-timeout' fuse-bridge translator option and accompanying
mount option (i.e., '-o gid-timeout=1' for a 1s entry timeout).

BUG: 800892
Change-Id: I0b34a2263ca48dbb154790a4a44fc70b733e9114
Signed-off-by: Brian Foster 
Reviewed-on: https://code.engineering.redhat.com/gerrit/1853
Reviewed-by: Vijay Bellur 
Tested-by: Vijay Bellur

mount/fuse: add mount-option "enable-ino32" for the native client

2012-11-19T09:03:08+00:00

From upstream commit c13823bd16b26bc471d3efb15f63b76fbfdf0309:

> By default the GlusterFS-native client uses 64-bit inodes. Some 32-bit
> applications can not handle these correctly. Introduce a client-side
> mount option "enable-ino32" which causes the FUSE-client to squash the
> 64-bit inodes into a 32-bit value.
>
> Change-Id: I3296d16528bfb50457b9675f6b8701234ed82ff0
> BUG: 850352
> Signed-off-by: Niels de Vos 
> Reviewed-on: http://review.gluster.org/3885
> Tested-by: Gluster Build System 
> Reviewed-by: Anand Avati 
> Signed-off-by: Niels de Vos 

BUG: 876679
Change-Id: Ie52ebc7d08f69a11cfa892a057bc9faf71446dcc
Signed-off-by: Niels de Vos 
Reviewed-on: https://code.engineering.redhat.com/gerrit/1585
Reviewed-by: Vijay Bellur 
Tested-by: Vijay Bellur

NFS is picking up geo-rep's already open (read-only) file descriptor

2012-11-14T18:13:04+00:00

Add anonymous member to fd_t and use it instead of over-loading pid for
geo-rep and self heal

Change-Id: I53a3becb6ee72498bab889654547ca7422bc0a59
Signed-off-by: Kaleb S. KEITHLEY 
BUG: 874272
Reviewed-on: https://code.engineering.redhat.com/gerrit/1531
Reviewed-by: Vijay Bellur 
Tested-by: Vijay Bellur

glusterfs: add gf_mkostemp api and use it instead of mkostemp if libc

2012-10-19T12:25:02+00:00

Change-Id: I6d72be95d304d2506204159f6533a8e3d6631cc2
BUG: 852041
Signed-off-by: Raghavendra Bhat 
Reviewed-on: https://code.engineering.redhat.com/gerrit/121
Reviewed-by: Vijay Bellur 
Tested-by: Vijay Bellur

core/statedump: dump the information in a temporary file and

2012-10-19T12:24:14+00:00

                then rename

Change-Id: Id35fd5b3801f46db75660a26d1f3011883c293a7
BUG: 852041
Signed-off-by: Raghavendra Bhat 
Reviewed-on: https://code.engineering.redhat.com/gerrit/120
Reviewed-by: Vijay Bellur 
Tested-by: Vijay Bellur

common-utils: valid_host_name() should allow (sub)domains starting/ending with a digit

2012-10-10T05:10:46+00:00

Some (sub)domains start or end with a digit. If this is the case, it
will not be possible to 'gluster peer probe' hosts in that (sub)domain.
This is overly restrictive, and RFC 1912 contains a note that describes
the common use of start/end digits in (sub)domains:
>
> Allowable characters in a label for a host name are only ASCII
> letters, digits, and the `-' character.  Labels may not be all
> numbers, but may have a leading digit  (e.g., 3com.com).  Labels must
> end and begin only with a letter or digit.  See [RFC 1035] and [RFC
> 1123].  (Labels were initially restricted in [RFC 1035] to start with
> a letter, and some older hosts still reportedly have problems with
> the relaxation in [RFC 1123].)  Note there are some Internet
> hostnames which violate this rule (411.org, 1776.com).
>

This change will also allow (sub)domains to consist out of digits only,
like the example of 411.org above. It is still not allowed to start or
and a (sub)domain with a `-' (dash) character.

Change-Id: Ia2b338b1f727c86ffcc3984d877b63c8476367e7
BUG: 863908
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/4017
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Jeff Darcy 
Reviewed-by: Anand Avati 
Reviewed-on: https://code.engineering.redhat.com/gerrit/60
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur 
Tested-by: Vijay Bellur

mgmt/glusterd: Implementation of server-side quorum.

2012-09-27T05:11:19+00:00

Feature-page:
http://www.gluster.org/community/documentation/index.php/Features/Server-quorum

Change-Id: Ifec0f1a697d390a29ba447a09750602fea1b3a4b
BUG: 840122
Signed-off-by: Pranith Kumar K