[Bugs] [Bug 1251106] sharding - Renames on non-sharded files failing with ENOMEM
bugzilla at redhat.com
bugzilla at redhat.com
Wed Aug 12 12:11:18 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1251106
--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11866 committed in release-3.7 by Raghavendra
G (rgowdapp at redhat.com)
------
commit e4726e843574c0db108fce1fc375241b72d7aed4
Author: Krutika Dhananjay <kdhananj at redhat.com>
Date: Thu Aug 6 12:19:23 2015 +0530
features/shard: Fill inode ctx in readdir(p) callback too
Backport of: http://review.gluster.org/#/c/11854/
The only place where shard translator was initialising inode ctx
was lookup callback. But if the inodes are created and linked through
readdirp, shard_lookup() path _may_ not be exercised before FUSE
winds other fops on them. Since shard translator does an
inode_ctx_get() first thing in most fops, an uninitialised ctx could
cause it to fail the operation with ENOMEM.
The solution would be to also initialise inode ctx if it has not been
done already in readdir(p) callback.
Change-Id: I6384e2d4c6b443c02c6620bbbc38279ddfad18ae
BUG: 1251106
Signed-off-by: Krutika Dhananjay <kdhananj at redhat.com>
Reviewed-on: http://review.gluster.org/11866
Tested-by: NetBSD Build System <jenkins at build.gluster.org>
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
More information about the Bugs
mailing list