Weird SMB Share Problem

We had a weird problem last week where the servers that would normally connect to the file share on our FS7610 were not able to connect. We'd get errors like insufficient resources when trying to connect. Finally, we found a workaround by changing the ip addresses on the clients. We then troubleshot further by using the affected IP addresses on other VMs and physical servers and still could not connect with those ip addresses. Has anyone seen anything like this? Is there a way to reboot the 7610?

TIA

Troy

Responses(1)

A

anonymous_coward

7 Posts

0

June 18th, 2019 11:00

When a client connects for the first time, FluidFS assigns client mac (and possibly IPs) to certain FSD (file system daemon). There are as many FSDs running on each controller as there are CPU cores in one. I'd a controller/FSD for whatever reason is running out of resources and the macs/IPs assigned to that are freaking out. To free up resources you might want to reboot controllers one after another (this is NOT a recommended way of doing that; tech support would try to investigate what's hogging the resources and can restart just the SMB server on the NAS instead of rebooting controllers, if the issue is something like SMB server memory leak). Don't reboot both controllers at the same time! Reboot one, let it boot for like 10 minutes, let it settle down for 10 minutes and then reboot the other one. Then redistribute the clients among controllers in Group Manager. I'd recommend doing this during off-peak hours. That should help. If not, you are looking at asking tech support for help. If I were you, I'd talk to tech support before taking my advice here. ;)

View All

No Events found!