{"push_id":910468002,"size":9,"distinct_size":4,"ref":"refs/heads/mand-lock","head":"9fe116729ba92cd29263eda791c8a6b1d7fad3e2","before":"b533cfe9f9244daa0bcdf885d327215df8496101","commits":[{"sha":"3151194fad1aed3ab340b53aeeb4e8d131538d12","author":{"email":"8c581b930d4e467db7caf29db13010a40a93b692@redhat.com","name":"Aravinda VK"},"message":"geo-rep: Symlink Rename issue\n\nIf ENTRY creation failed for symlink in Slave and symlink\nrenamed in Master. If Source not exists to Rename in Slave\nGeo-rep interprets as Create of Target file. Geo-rep sends blob\nof regular file to create symlink instead of sending blob of\nsymlink.\n\nWith this patch, Geo-rep identifies symlink and sends respective\nblob.\n\nBUG: 1289859\nChange-Id: If9351974d1945141a1d3abb838b7d0de7591e48e\nSigned-off-by: Aravinda VK <avishwan@redhat.com>\nReviewed-on: http://review.gluster.org/12917\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Kotresh HR <khiremat@redhat.com>\nReviewed-by: Milind Changire <mchangir@redhat.com>\nTested-by: Milind Changire <mchangir@redhat.com>\nTested-by: NetBSD Build System <jenkins@build.gluster.org>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/3151194fad1aed3ab340b53aeeb4e8d131538d12"},{"sha":"9644769ea174646eaf18b8a41873f67928be9c8d","author":{"email":"c76ab867872ae894584851095ba033ec647884ae@redhat.com","name":"Dan Lambright"},"message":"cluster/tier: fix tier-max-files bookeeping and help\n\nThe option tier-max-files represents the maximum number\nof files trasferred by a node in a gives cycle. Fix help message\nto reflect the \"per node\" aspect. The code transferred one\nmore file per cycle than the given value.\n\nAlso change the default values of max file and max bytes to\nvery large values, effectively we will not throttle migration\nunless the administrator requests it via CLI.\n\nChange-Id: Ic2949ed3d8c35afe7c9ae4db72195603cfb2e28f\nBUG: 1292671\nSigned-off-by: Dan Lambright <dlambrig@redhat.com>\nReviewed-on: http://review.gluster.org/12984\nTested-by: NetBSD Build System <jenkins@build.gluster.org>\nTested-by: Gluster Build System <jenkins@build.gluster.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/9644769ea174646eaf18b8a41873f67928be9c8d"},{"sha":"d5a9e765543fd6eec5d522e4f3f062bef97aefed","author":{"email":"10460665c63c1e41b922ea2cdf63084aa1a91e2a@redhat.com","name":"Ravishankar N"},"message":"afr: refresh inode using fstat\n\nFor fd based operations (fgetxattr, readv etc.) if an inode refresh is\nrequired, do so using fstat instead of lookup. This is because the file\nmight have been deleted by another client before refresh but posix\nmandates that FOPS using already open fds must still succeed.\n\nChange-Id: Id5f71c3af4892b648eb747f363dffe6208e7ac09\nBUG: 1285230\nSigned-off-by: Ravishankar N <ravishankar@redhat.com>\nReviewed-on: http://review.gluster.org/12894\nReviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nTested-by: NetBSD Build System <jenkins@build.gluster.org>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/d5a9e765543fd6eec5d522e4f3f062bef97aefed"},{"sha":"a99bbccbb5e3087b9b8b687ee2be8887eeac0d08","author":{"email":"145615fbac7c5189e559d92d352779af072b5c5f@redhat.com","name":"Anuradha Talur"},"message":"heal : Do not print heal count on ENOTCONN\n\nWhen a brick is not reachable due to ENOTCONN,\nthere are no entries gathered and this information\nshould not be printed.\nIt is a bug intorduced due to commit\n9c378026e9561595586a817fee0b439e2c863a22, fixing it.\n\nChange-Id: I45559a9560c297854ea6b4177f86e0be30dc6b78\nBUG: 1250803\nSigned-off-by: Anuradha Talur <atalur@redhat.com>\nReviewed-on: http://review.gluster.org/12919\nTested-by: NetBSD Build System <jenkins@build.gluster.org>\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/a99bbccbb5e3087b9b8b687ee2be8887eeac0d08"},{"sha":"2b7226f9d3470d8fe4c98c1fddb06e7f641e364d","author":{"email":"10460665c63c1e41b922ea2cdf63084aa1a91e2a@redhat.com","name":"Ravishankar N"},"message":"afr: handle bad objects during lookup/inode_refresh\n\nIf an object (file) is marked bad by bitrot, do not consider the brick\non which the object is present  as a potential read subvolume for AFR\nirrespective of the pending xattr values.\n\nAlso do not consider the brick containing the bad object while\nperforming afr_accuse_smallfiles(). Otherwise if the bad object's size\nis bigger, we may end up considering that as the source.\n\nChange-Id: I4abc68e51e5c43c5adfa56e1c00b46db22c88cf7\nBUG: 1290965\nSigned-off-by: Ravishankar N <ravishankar@redhat.com>\nReviewed-on: http://review.gluster.org/12955\nReviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>\nTested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/2b7226f9d3470d8fe4c98c1fddb06e7f641e364d"},{"sha":"55b8e16420635e70333466767bda7c1ac8882049","author":{"email":"52add29bc15c0f3832a373982b132796d33ff6c3@redhat.com","name":"Anoop C S"},"message":"features/locks: Fixing mandatory-locking code path\n\nThis is the initial change to fix/enable the mandatory\nlocking support in GlusterFS as per the following\ndesign doc:\n\nhttps://review.gluster.org/#/c/12014/\n\nAccordingly 'locks.mandatory-locking' option is available as\npart of this change which will accept one among the following\nvalues:\n\n* off\n* file\n* forced\n* optimal\n\nChange-Id: I14c489b3f8af5ebcbfa155a03f0c175e9558ac46\nBUG: 762184\nSigned-off-by: Anoop C S <anoopcs@redhat.com>","distinct":true,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/55b8e16420635e70333466767bda7c1ac8882049"},{"sha":"2fe9b51982a2f757e71c79296f2d7dfb15421680","author":{"email":"52add29bc15c0f3832a373982b132796d33ff6c3@redhat.com","name":"Anoop C S"},"message":"features/locks: Include zerofill fop in locks translator\n\nAs of now zerofill call is not considered inside locks\ntranslator. But when mandatory-locking is enabled for a\nvolume, then we may need to check for conflicting locks\nbefore performing zerofill operation on a particular\nfile. This patch is intended to include zerofill fop\ninside locks translator.\n\nChange-Id: I2d6de45f9f3e58865a8ff31c0d1a53dc5be15aff\nBUG: 762184\nSigned-off-by: Anoop C S <anoopcs@redhat.com>","distinct":true,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/2fe9b51982a2f757e71c79296f2d7dfb15421680"},{"sha":"4bc9d7b0903b0f962ded3de4ad8b741362275e03","author":{"email":"52add29bc15c0f3832a373982b132796d33ff6c3@redhat.com","name":"Anoop C S"},"message":"gfapi: Add API support for applying mandatory-locks\n\nThe current API for byte-range locks[glfs_posix_lock()]\ndoesn't allow applications to specify whether it is\nadvisory or mandatory type locks. This particular change\nis to introduce an extended byte-range lock API with\nadditional arguments for including the byte-range lock\nmode to be one among advisory(default) or mandatory.\n\nChange-Id: Ia09042c755d891895d96da857321abc4ce03e20c\nBUG: 762184\nSigned-off-by: Anoop C S <anoopcs@redhat.com>","distinct":true,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/4bc9d7b0903b0f962ded3de4ad8b741362275e03"},{"sha":"9fe116729ba92cd29263eda791c8a6b1d7fad3e2","author":{"email":"52add29bc15c0f3832a373982b132796d33ff6c3@redhat.com","name":"Anoop C S"},"message":"tests: Add libgfapi test case for mandatory locks\n\nChange-Id: I93a8324649751d1ff4f076cc76c66943ac994da2\nSigned-off-by: Anoop C S <anoopcs@redhat.com>","distinct":true,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/9fe116729ba92cd29263eda791c8a6b1d7fad3e2"}]}