Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. With quota disabled; nfs client mount nfs-ganesha share, and do 'll' in the testing directory. 2. Enable quota; getfattr: Removing leading '/' from absolute path names trusted.gfid=0xe2edaac0eca8420ebbbcba7e56bbd240 trusted.gfid2path.b3250af8fa558e66=0x39663134343566662d653530332d343831352d396635312d3236633565366332633137642f7465737466696c653932 trusted.glusterfs.quota.9f1445ff-e503-4815-9f51-26c5e6c2c17d.contri.3=0x00000000000002000000000000000001 Notice: testfile92 without trusted.pgfid xattr. 3. restart glusterfs volume by "gluster volume stop/start gvtest" 4. echo somedata > testfile92 5. ll testfile92 -rw-r--r-- 1 root root 0 Mar 6 21:43 testfile92 Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/19706 (quota: allow writes when with EINVAL on pgfid isnot exist) posted (#3) for review on master by Kinglong Mee
COMMIT: https://review.gluster.org/19706 committed in master by "Kinglong Mee" <kinglongmee> with a commit message- quota: allow writes when with EINVAL on pgfid isnot exist NFS client gets "Invalid argument" when writing file through nfs-ganesha. 1. With quota disabled; nfs client mount nfs-ganesha share, and do 'll' in the testing directory. 2. Enable quota; getfattr: Removing leading '/' from absolute path names trusted.gfid=0xe2edaac0eca8420ebbbcba7e56bbd240 trusted.gfid2path.b3250af8fa558e66=0x39663134343566662d653530332d343831352d396635312d3236633565366332633137642f7465737466696c653932 trusted.glusterfs.quota.9f1445ff-e503-4815-9f51-26c5e6c2c17d.contri.3=0x00000000000002000000000000000001 Notice: testfile92 without trusted.pgfid xattr. 3. restart glusterfs volume by "gluster volume stop/start gvtest" 4. echo somedata > testfile92 5. ll testfile92 -rw-r--r-- 1 root root 0 Mar 6 21:43 testfile92 BUG: 1560319 Change-Id: Iaa4dd1e891c99069fb85b7b11bb0482cbf2303b1 fixes: bz#1560319 Signed-off-by: Kinglong Mee <mijinlong>
REVIEW: https://review.gluster.org/19837 (storage/posix: add pgfid in readdirp if needed) posted (#1) for review on master by Kinglong Mee
COMMIT: https://review.gluster.org/19837 committed in master by "Kinglong Mee" <kinglongmee> with a commit message- storage/posix: add pgfid in readdirp if needed Change-Id: I6745428fd9d4e402bf2cad52cee8ab46b7fd822f fixes: bz#1560319 Signed-off-by: Kinglong Mee <mijinlong>
I'm moving this back to POST as this patch is causing failures of tests/features/trash.t in upstream CI. I'm going to mark the trash.t bad with this same bug id till this is addressed. Given we're nearing GlusterFS 4.1 branching, lot of critical patches are stuck in regression pipeline queue and we need to make a move on.
REVIEW: https://review.gluster.org/19894 (tests: mark trash.t as bad) posted (#1) for review on master by Atin Mukherjee
REVIEW: https://review.gluster.org/19896 (Revert \"storage/posix: add pgfid in readdirp if needed\") posted (#1) for review on master by Nigel Babu
COMMIT: https://review.gluster.org/19896 committed in master by "Nigel Babu" <nigelb> with a commit message- Revert "storage/posix: add pgfid in readdirp if needed" This reverts commit d206fab73f6815c927a84171ee9361c9b31557b1. Change-Id: I5b43fdcf916bc844437c9d60f6957bc40936e3c2 Updates: bz#1560319 Signed-off-by: Nigel Babu <nigelb>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-v4.1.0, please open a new bug report. glusterfs-v4.1.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2018-June/000102.html [2] https://www.gluster.org/pipermail/gluster-users/