glusterfs.git/xlators/features/shard/src/shard.c, branch v3.7.0beta2

features/shard: Implement [f]truncate fops

2015-05-08T11:49:54+00:00

        Backport of: http://review.gluster.org/10631
To-Do:
* Make ftruncate work even in the absence of path
* Aggregate and update ia_blocks appropriately when a file is
  truncated to a lower size.

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

features/shard: Implement readv() fop

2015-05-06T08:11:39+00:00

        Backport of: http://review.gluster.org/#/c/10528/

Change-Id: I3ff03d146a8d49cc11e7bf22ffbf830b4dd1e9f1
BUG: 1214247
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/10569
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System
Reviewed-by: Pranith Kumar Karampuri

features/shard: Take hole size into account while computing ia_size

2015-05-03T18:15:09+00:00

        Backport of: http://review.gluster.org/10446

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

features/shard: Add "is-directory" checks in stat/fstat

2015-05-03T18:12:56+00:00

        Backport of: http://review.gluster.org/10427

During mount, NFS directly calls stat on the root of the volume
without sending a lookup on it. This was causing inode_ctx_get_block_size()
to fail on /. A check is now added in [f]stat which would ensure no action
is taken by shard xlator when the operation is on a directory.

Change-Id: I8645b7fe58b2d44b5f527d50c1c7102de44acc00
BUG: 1214247
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/10509
Tested-by: NetBSD Build System
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

features/shard: Implement rename() fop

2015-04-30T19:10:54+00:00

        Backport of: http://review.gluster.org/10373

Change-Id: I15867667d50b2b4aad0ee3738a29f7a410d61ef4
BUG: 1214247
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/10455
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System
Reviewed-by: Vijay Bellur

features/shard: Implement unlink fop

2015-04-27T05:08:54+00:00

        Backport of: http://review.gluster.org/10249

Change-Id: I01761721224c4efbbc5e4992e70ecf68b3868d63
BUG: 1214247
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/10377
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System
Reviewed-by: Vijay Bellur

features/shard: Consume size and block count in metadata read ops

2015-04-26T07:04:58+00:00

        Backport of : http://review.gluster.org/10098

Metadata read fops like lookup, stat etc will now fetch the xattr that
holds the size and block count information, extract the size and block
count fields and set them in respective stbuf before unwinding the
resultant iatt to the parent xlator.

Change-Id: If7d2c4af886f8d70dc69d7cb09f1f66be391f198
BUG: 1214248
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/10331
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: NetBSD Build System
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

features/shard: Introduce file size xattr

2015-04-08T15:23:29+00:00

With each inode write FOP, the size and block count of the file will be
updated within the xattr. There are two 64 byte fields that are
intentionally left blank for now for future use when consistency
guarantee is introduced later in sharding.

Change-Id: I40a2e700150c1f199a6bf87909f063c84ab7bb43
BUG: 1207603
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/10097
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System

features/shard: Refactor code

2015-04-07T06:09:28+00:00

* Renamed shard_writev_create_write_shards() to shard_common_resolve_shards()
  to appropriately reflect its functionality and for reuse in other fops too.

* Move code common to MKNOD and CREATE into a macro.

* Cut down on if nesting in shard_lookup_cbk()

Change-Id: I488255499673accd426390c6d42f2b39bab3d637
BUG: 1205661
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/10096
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

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