Can't get exclusive lock on NAS repo lock files after upgrading to Mac OS X High Sierra

[Julius Smith]

I was cruising along great with my subversion repos on my NAS and my
working copies on Mac OS X Sierra, but after upgrading to High Sierra

svn ci -m 'update'

svn: E000045: Commit failed (details follow):
svn: E000045: Can't get exclusive lock on file
'/Volumes/Repos/SubversionRepos/svnr/scriptssvn/db/txn-current-lock':
Operation not supported

I have tried mounting the NAS using every filesystem format supported
(I have a QNAP Model TS-453 Pro), and the problem persists.

My next step is to move all the repos to an external hard drive and do
an "svn switch --relocate" on each one, but I thought I'd try this
list first to see if anyone has encountered the problem and found a
solution.

Thanks for any tips!
- Julius

[Julius Smith]

I must have overlooked something in my previous tests. I got it

Post by Julius Smith
mount

...
192.168.xxx.xxx:/SVNRepos on /Volumes/SVNRepos (nfs, asynchronous,
nodev, nosuid, mounted by me)

The failing mount protocols were SMB/CIFS and AFP. I didn't try FTP.

- Julius

Post by Julius Smith
I was cruising along great with my subversion repos on my NAS and my
working copies on Mac OS X Sierra, but after upgrading to High Sierra

svn ci -m 'update'

svn: E000045: Can't get exclusive lock on file
Operation not supported
I have tried mounting the NAS using every filesystem format supported
(I have a QNAP Model TS-453 Pro), and the problem persists.
My next step is to move all the repos to an external hard drive and do
an "svn switch --relocate" on each one, but I thought I'd try this
list first to see if anyone has encountered the problem and found a
solution.
Thanks for any tips!
- Julius

[Nathan Hartman]

Post by Julius Smith
I was cruising along great with my subversion repos on my NAS and my
working copies on Mac OS X Sierra, but after upgrading to High Sierra

svn ci -m 'update'

svn: E000045: Can't get exclusive lock on file
Operation not supported
I have tried mounting the NAS using every filesystem format supported
(I have a QNAP Model TS-453 Pro), and the problem persists.

Is your svn server process running on a different machine than the repo storage?

Did you try installing your svn server process on the NAS?

I am not familiar with your NAS but a quick google search brought this up:

http://blog.sebastian-martens.de/technology/install-svn-on-qnap/