Hello Everyone,

I wanted to post another update on my adventures with SBBS and Shared Storage with CIFS/NFS on Synology NAS.

I wanted to give everyone my latest stable fstab:
//nas/bbs /mnt/bbs cifs credentials=/root/.cifscreds,vers=3.0,uid=uid#,gid=gid#,exec 0 0

By switching from version 3.1.1 to 3.0, I was able to renable opportunistic locks and SMB durable handles.
To make all of this work, I did have to adjust the adv. CIFS setting on the Synology for encryption from FORCE to AUTO, as opportunistic locks and encryption seem to mutually exclusive.

I still haven't been able to resolve the issues I've had with SBBS locking chat.dab. Once a split-screen chat is initiated from umonitor or gtkmonitor, the user is brought into chat, and the user's chat echos, but not echos in umonitor or gtkmonitor and the applications lock until their process is killed. Once, the process is killed, generally some random characters are echoed back to the initiating shell. There are no permission issues. I am stumped whether or not this is a problem local to my Synology CIFS backend or general SAMBA, as this problem doesn't exist when the chat.dab is created on local disk or on an iscsi volume off of the Synology.

In the interest of my sanity, I've taken a break from trying to troubleshoot running Linux-based SBBS entirely off of a Synology-backed CIFS share in favor of iSCSI, but I would still be willing to test any recommended config changes.

The main reason for wanting to use CIFS was to lower complexity and
have the ability to divide SBBS nodes between discrete hardware, while also leveraging the RAID protection on the Synology, but HW locking has been challenging to resolve.

So far, CIFS is much faster and reliable than any of the configuration attempts on NFS, but until I can get around the file locking issue, it's getting shelved. If anyone has solved this problem, I'd be interested in their solution.

Thanks,
-WitNik
---
■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net