When editing the configuration of an existing share using SWAT, a second share with the same name will be created.
Reverting commit f76614169 (v3-3-test (fixes the creation of the first share using SWAT)) fixes the problem for me.
This issue exists in 3.2 also.
Created attachment 5023 [details]
Proposed patch created by Volker
(In reply to comment #1)
> Created an attachment (id=5023) [details]
> Proposed patch created by Volker
Patch fixes the issue in my setup.
Any volunteer for patch review?
Patch already upstream.
Closing out bug report.