Bug 1001102
Summary: | Stale smb share still shows up after deleting the gluster volume | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Lalatendu Mohanty <lmohanty> |
Component: | samba | Assignee: | Raghavendra Talur <rtalur> |
Status: | CLOSED EOL | QA Contact: | Lalatendu Mohanty <lmohanty> |
Severity: | unspecified | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | dpal, jarrpa, pgurusid, rjoseph, rwheeler, spalai |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | core | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-03 17:11:07 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: |
Description
Lalatendu Mohanty
2013-08-26 13:51:13 UTC
Try the following command: smbcontrol all reload-config When run from the root account, that command should cause all Samba daemons (including winbindd) to immediately reload the smb.conf configuration files. Note that the Samba daemons will eventually reload the configuration file on their own, but it may be a minutes before the automatic reload occurs. Chris, "smbcontrol all reload-config" works fine. May be hook script change will do the job. Is there any smb.conf parameter which does this job of reading smb.conf file ? Currently in the hook script we are sending a SIGHUP to smbd daemon. But for windows client to reload the smb.conf we have to send SIGHUP to winbindd ,which I think will fix this issue. Chris , I tested the for SAMBA+XFS just to confirm that whether glusterfs plays any role in it. And I am finding the same issue of stale shares. And "smbconbtrol all reload-config" doesn't work always. I think the reloading of smb-conf is confined to the smbd process only and the client does not go for refresh. I think we can document the above findings if needed. Also we observe that, when the gluster volume is stopped, the "smbclient -L" does not show any entry for the volume stopped, but the volume still continues to appear in the windows client. I filed a bug in SAMBA Bugzilla for this. Here is the link : https://bugzilla.samba.org/show_bug.cgi?id=10156 Their resolution is ---> restart smbd. See if this will help: https://lists.samba.org/archive/samba/2010-August/157687.html The command in question is "smbcontrol close-share", and should be done BEFORE the volume is stopped. Note the concerns that the email author brings up, but I don't think they impact us. Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/ If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release. |