[Bugs] [Bug 1357257] observing " Too many levels of symbolic links" after adding bricks and then issuing a replace brick
bugzilla at redhat.com
bugzilla at redhat.com
Mon Jul 18 20:56:23 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1357257
--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14941 committed in release-3.8 by Kaleb
KEITHLEY (kkeithle at redhat.com)
------
commit 951aa4d0837007249046b8ca8362d0d2024cb252
Author: Soumya Koduri <skoduri at redhat.com>
Date: Wed Jul 13 16:24:31 2016 +0530
nfs: Reset cs->resolvedhard while resolving an entry
If an entry is not found in the inode table, nfs xlator should be
resolving it by sending an explicit lookup to the brick process.
But currently its broken in case of NFS3_LOOKUP fop where in the server
bails out early resulting in sending pargfid attributes to the client.
To fix the same reset 'cs->resolvedhard' so that an explicit lookup
is done for the entry in the resume_fn "nfs3_lookup_resume()".
This is backport of the below mainline patch -
http://review.gluster.org/14911
BUG: 1357257
>Change-Id: I999f8bca7ad008526c174d13f69886dc809d9552
>Signed-off-by: Soumya Koduri <skoduri at redhat.com>
>BUG: 1356068
>Reviewed-on: http://review.gluster.org/14911
>CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
>NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
>Smoke: Gluster Build System <jenkins at build.gluster.org>
>Reviewed-by: Niels de Vos <ndevos at redhat.com>
>(cherry picked from commit 3c485cb896837c8e362fd0b094325002ce806ac4)
Change-Id: Ifeb21887810115369ca2ae6c8c3d3619d4e6c066
Reviewed-on: http://review.gluster.org/14941
Reviewed-by: Kaleb KEITHLEY <kkeithle at redhat.com>
Tested-by: soumya k <skoduri at redhat.com>
Reviewed-by: jiademing.dd <iesool at 126.com>
Smoke: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=hx81NIwypu&a=cc_unsubscribe
More information about the Bugs
mailing list