Bug 1467513
Summary: | CIFS:[USS]: .snaps is not accessible from the CIFS client after volume stop/start | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Mohammed Rafi KC <rkavunga> |
Component: | snapshot | Assignee: | Mohammed Rafi KC <rkavunga> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | mainline | CC: | amukherj, asengupt, ashah, asrivast, mzywusko, rabhat, rcyriac, rhinduja, rhs-bugs, rjoseph, ssamanta |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.12.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1191480 | Environment: | |
Last Closed: | 2017-09-05 17:35:44 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1191480, 1277944 | ||
Bug Blocks: |
Comment 1
Mohammed Rafi KC
2017-07-04 06:19:29 UTC
COMMIT: https://review.gluster.org/17689 committed in master by Atin Mukherjee (amukherj) ------ commit ecd92d42bbd9249aa637b1ad3000aa242308cb04 Author: Mohammed Rafi KC <rkavunga> Date: Fri Jun 30 20:17:20 2017 +0530 svs:implement CHILD UP notify in snapview-server protocol/server expects a child up event to successfully configure the graph. In the actual brick graph, posix is the one who decide to initiate the notification to the parent that the child is up. But in snapd graph there is no posix, hence the child up notification was missing. Ideally each xlator should initiate the child up event whenever it see's that this is the last child xlator. Change-Id: Icccdb9fe920c265cadaf9f91c040a0831b4b78fc BUG: 1467513 Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: https://review.gluster.org/17689 CentOS-regression: Gluster Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Amar Tumballi <amarts> Reviewed-by: Raghavendra Bhat <raghavendra> COMMIT: https://review.gluster.org/17690 committed in master by Atin Mukherjee (amukherj) ------ commit 70a5dfdea4980dea5da5b5008a16fd155a3adf34 Author: Mohammed Rafi KC <rkavunga> Date: Mon Jul 3 12:45:38 2017 +0530 svc: send revalidate lookup on special dir .snaps directory is a virtual direcotory, that doesn't exist on the backend. Even though it is a special dentry, it doesn't have a dedicated inode. So the inode number is always random. Which means it will get different inode number when reboot happens on snapd process. Now with windows client the show-direcotry feature requires a lookup on the .snpas direcoty post readdirp on root. If the snapd restarted after a lookup, then subsequent lookup will fail, because linked inode will be stale. This patch will do a revalidate lookup with a new inode. Change-Id: If97c07ecb307cefe7c86be8ebd05e28cbf678d1f BUG: 1467513 Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: https://review.gluster.org/17690 CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Raghavendra Bhat <raghavendra> Smoke: Gluster Build System <jenkins.org> REVIEW: https://review.gluster.org/17691 (uss/svc: fix double free on xdata dictionary) posted (#2) for review on master by Atin Mukherjee (amukherj) COMMIT: https://review.gluster.org/17691 committed in master by Atin Mukherjee (amukherj) ------ commit 26241777bf59c7d64c582ce09e557bc2dc97dabb Author: Mohammed Rafi KC <rkavunga> Date: Mon Jul 3 16:37:01 2017 +0530 uss/svc: fix double free on xdata dictionary we were taking unref on wrong dictionary which results in wrong memory access. Change-Id: Ic25a6c209ecd72c9056dfcb79fabcfc650dd3c1e BUG: 1467513 Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: https://review.gluster.org/17691 CentOS-regression: Gluster Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj> 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-3.12.0, please open a new bug report. glusterfs-3.12.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/2017-September/000082.html [2] https://www.gluster.org/pipermail/gluster-users/ |