Samba is puking, dying, or otherwise hanging

[tucansam]

This is now happening all the time.  It used to be a regular (once or twice a month) occurance, but today it has now happened three times, and I have some idea why.

 

Shares are available to Windows machines.  After a particular amount of file I/O onto the array, all shares disappear, and /mnt/user becomes unavailable with errors at the shell prompt.  /mnt/user: Transport endpoint is not connected

 

Today I am doing a lot of maintenance on my media library, and sabnzbd is downloading several terabytes of data.  It gets to a certain point, successfully, and then the aforementioned issue pops up.  Stopping and starting the array has no effect; only a reboot will bring /mnt/user back online.  Then sab will continue about its business until the next the time issue happens.  Like I said, sitting here for the last couple of hours, its now happened three time.

 

This has been an ongoing issue for me for at least a year, but today it is bad enough (and consistent) enough that I've had enough.  Diags attached.

 

 

 

ffs2-diagnostics-20231002-0945.zip

[tucansam]

Have seen similar threads going back to 2020 indicating it may be the mover.  Some users indicated that turning the mover off had no effect.  Some believe it is an issue with NFS -- I cannot turn NFS off.

 

[JorgeB]

It's this old issue:

 

[tucansam]

Is there a known fix?  Or just theories?

[JorgeB]

Some workarounds discussed in that thread, but AFAIK no definite fix since there's also no way to consistently reproduce it.

[tucansam]

I can consistently reproduce it.

 

Its just not throwing anything in syslog AFAIK.  Anywhere else I can be looking?

[JorgeB]

Can you give the steps needed so that I or someone else can reproduce it?

[tucansam]

I have 250GB of queue going in sab.

 

I have Windows Explorer open as I peruse the filesystem cleaning up old files, fixing renaming errors sonarr or sab screw up, etc.

 

Within 60 minutes of conducting both of these activities at the same time, the issue surfaces.

 

Its now happened six or seven times today.  It seems to be the consistent manipulation of the filesystem in some way (usually unpacking downloaded rar files is the instant at which it occurs).

 

It occurs when Explorer is closed and sab is the only thing messing with the filesystem (although in fairness Plex is doing its constantly watching thing in the background, indexing newly downloaded files)