glusterfs.git/xlators, branch v3.4.0qa3

cluster/dht: send ACCESS call on dir to first_up_subvol if cached is down

2012-11-29T10:26:18+00:00

Change-Id: I4f518a969bbe3a11075e7c9ae10bd21bf059d5f3
BUG: 867253
Signed-off-by: shishir gowda 
Reviewed-on: http://review.gluster.org/4240
Reviewed-by: Jeff Darcy 
Tested-by: Gluster Build System

geo-rep / gsyncd,glusterd: do not hardcode socket path

2012-11-29T00:54:07+00:00

... in gsyncd python code. Indeed, use the configuration
mechanism to set it suitably from glusterd.

Change-Id: I9fe2088b14d28588d1e64fe892740cc5755b8365
BUG: 868877
Signed-off-by: Csaba Henk 
Reviewed-on: http://review.gluster.org/4143
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

glusterd, cli: implement gluster system uuid reset command

2012-11-29T00:28:55+00:00

A commonly faced problem among glusterfs users is: after a fresh
installation of glusterfs in a virtual machine, the VM image is
cloned to make multiple instances of the server. This breaks
glusterd because right after glusterfs installation on the first
boot glusterd would have created the node UUID and this gets
inherited into the clone. The result is wierd behavior at the time
of peer probe where glusterd does not (yet) deal with UUID
collisions in a user friendly way.

To handle it gluster peer reset command is implemented which upon
execution changes the uuid of local glusterd.

Change-Id: If207dd2ad93ab94ef1a3253f409c21c442975f87
BUG: 811493
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.org/3637
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

glusterd: Protected conf->xprt_list racy access.

2012-11-29T00:27:01+00:00

- epoll on RPCSVC_EVENT_ACCEPT would add corresponding xprt
  onto the xprt_list. Concurrently, synctask thread (volume op)
  would call into glusterd_fetchspec_notify which iterates on
  the xprt_list. Added a mutex to protect such a racy access of
  the list.

Change-Id: Idc51b4bdb1c814dfab7790e1c899d6977f7640f2
BUG: 878873
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.org/4241
Reviewed-by: Raghavendra G 
Reviewed-by: Jeff Darcy 
Tested-by: Gluster Build System

geo-replication: catch select.error on select()

2012-11-29T00:23:49+00:00

tailer() in resource.py does not correctly catch exceptions from
select(). select() can raise an instance of the select.error class and
the current expression only catches ValueError (and the instance will
have reference called selecterror).

The geo-rep log contains a call trace like this:
> E [syncdutils:190:log_raise_exception] : FAIL:
> Traceback (most recent call last):
> File "/usr/libexec/glusterfs/python/syncdaemon/syncdutils.py", line 216, in twrap
> tf(*aa)
> File "/usr/libexec/glusterfs/python/syncdaemon/resource.py", line 123, in tailer
> poe, _ ,_ = select([po.stderr for po in errstore], [], [], 1)
> File "/usr/libexec/glusterfs/python/syncdaemon/syncdutils.py", line 276, in select
> return eintr_wrap(oselect.select, oselect.error, *a)
> File "/usr/libexec/glusterfs/python/syncdaemon/syncdutils.py", line 269, in eintr_wrap
> return func(*a)
> error: (9, 'Bad file descriptor')

BUG: 880308
Change-Id: I2babe42918950d0e9ddb3d08fa21aa3548ccf7c5
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/4233
Reviewed-by: Peter Portante 
Reviewed-by: Csaba Henk 
Tested-by: Gluster Build System

protocol/client: add an option to filter O_DIRECT flag in open

2012-11-28T11:37:03+00:00

with the option, the idea is all client-side caching will be disabled,
where as on server side process, the fd will be treated as a regular
fd, thus helping the performance better.

"gluster volume set  remote-dio enable" would set
this option in client protocol volumes.

Change-Id: Id2255a167137f8fee20849513e3011274dc829b4
Signed-off-by: Amar Tumballi 
BUG: 845213
Reviewed-on: http://review.gluster.org/4206
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: volume-sync shouldn't validate volume-id

2012-11-28T07:28:00+00:00

- volume sync would overwrite volume information on local node
  from the hostname supplied. This warning is provided to the user.

- Also fixed a double free in volume-sync handler.

Change-Id: Icc68d9d563fb50ca58d5880921f063692e1e6882
BUG: 865700
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.org/4188
Reviewed-by: Vijay Bellur 
Tested-by: Gluster Build System

features/locks: implement fgetxattr and fsetxattr

2012-11-28T06:54:27+00:00

implement xattrs for GF_XATTR_LOCKINFO_KEY, which will be used
for posix-locks migration from old to new graph after a switch.

fgetxattr (fd, GF_XATTR_LOCKINFO_KEY) will return a dict.
This dict has a serialized dict stored for key
GF_XATTR_LOCKINFO_KEY. This serialized dict in turn has fdnum
value of locks acquired on this fd with modified pathinfo
(containing hostname and base directory components) as key.

fsetxattr (newfd, GF_XATTR_LOCKINFO_KEY, dict) has following
semantics. dict can be the result of a previous fgetxattr with
GF_XATTR_LOCKINFO_KEY. In that case, a dict_get on dict
constructed using serialized buffer is done on modified pathinfo
as key. If a value is got, that value is treated as fdnum and for
every lock l on newfd->inode we do,
      if (l->fdnum == fdnum) {
         l->fdnum = fd_fdnum (newfd);
         l->transport = ;
      }

Signed-off-by: Raghavendra G 
Change-Id: I73a8f43aa0b6077bc19f8de52205ba748f2d8bbe
BUG: 808400
Reviewed-on: http://review.gluster.org/4120
Reviewed-by: Vijay Bellur 
Tested-by: Vijay Bellur

cluster/stripe: handle GF_XATTR_LOCKINFO_KEY in f(get)(set)xattr

2012-11-28T06:44:40+00:00

Change-Id: I4463006a7f54c05e757d877c56e1330fd91aec45
BUG: 808400
Signed-off-by: Raghavendra 
Reviewed-on: http://review.gluster.org/4125
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cluster/distribute: send getxattr on LOCKINFO to only cached subvolumes.

2012-11-28T06:43:57+00:00

lk is sent to only cached subvolume. Hence there is no point in
sending LOCKINFO to other children (even in case of directories).

Change-Id: Ia20fc358dfa84cee9a52d1f613564ff6f25aa0c9
BUG: 808400
Signed-off-by: Raghavendra 
Reviewed-on: http://review.gluster.org/4123
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur