This post is more than 5 years old
4 Posts
0
1618
August 30th, 2011 23:00
VNXe3100 unable to delete shared folder (CIFS)
Hi guys!
I noticed that one of our storage pool at an alert state as the current allocation at 100%. I decided to delete a share and recreate it with a smaller size (thin provisioning was disabled). I deleted the share, it disappeared from the Storage->Shared folders list, but storage utilization did not change, storage pool is still at alert state, and I cannot create shared folder on the same shared folder server. Besides the deleted share can be accessed on the network! We runs SP3 on the VNXe. Any help would be appreciated.
Tamas
0 events found
No Events found!
Kumar_A
2 Intern
•
727 Posts
0
September 1st, 2011 12:00
It will be difficult to diagnose the real issue on this forum. It would be better to have support involved for this.
lengyeltamas
4 Posts
0
September 2nd, 2011 02:00
Hi!
Thanks for the answer, I contacted support and the problem is solved now. It turned out that when I deleted the share it had some active connections, and the share could not be deleted but it disappeared from Unisphere. I will check this next time I want to delete share, but I think VNXe should handle this scenario. Maybe some enhancement is required here.
Tamas
Kumar_A
2 Intern
•
727 Posts
0
September 2nd, 2011 06:00
It seems this problem is not easily reproducible as I thought initially. This is what I did:
1. Created a CIFS share on a VNXe system running 2.1.0.14097 code.
2. Mounted this share on a couple of Windows hosts. Coule access the share.
3. Deleted this share through Unisphere.
4. Could not access the share through the hosts now.
Did you do anything different from what I have done here?
Kumar_A
2 Intern
•
727 Posts
0
September 2nd, 2011 06:00
Thanks for the update. I will try to reproduce this issue in my lab and follow up with Engineering on this issue.
Kumar_A
2 Intern
•
727 Posts
0
September 2nd, 2011 07:00
2.1.0.14097 is the latest code (called MR1) and it is advisable to upgrade to this code if possible. I cannot say for sure if your issue is because of the old code or not, since this was not a known issue. But as I mentioned earlier in my post, I did not see the issue that you saw in the new code.
lengyeltamas
4 Posts
0
September 2nd, 2011 07:00
Hi!
Basically I did the same, only difference I can see that at the time of deletion the version was 2.0.3.xxx.
Could it be a difference?
Tamas
lengyeltamas
4 Posts
0
September 2nd, 2011 07:00
I upgraded to MR1 and I did a second deletion today with a different share, but I closed any connection before and no problem occured.
Maybe it is corrected implicitly in the new release or my case had a difference which remained unknown.
(for instance: I did not mapped the share in windows but i had it opened with total commander).
Anyway the problem is solved, so thank you for your help!
Tamas