Integration breaks for all projects when a CVSROOT path is changed to a symbolic link

We have integrated several different and independent CVS repositories into their corresponding categories/projects.

Recently, one of our CVS repositories had to be moved due to space limitations. In order to ensure our users were not impacted by this we made the old repository location a symbolic link to the new location.

i.e. For all users the CVSROOT path remained as: ':ext:<username>@<servername>:/var/lib/cvs'
but now '/var/lib/cvs' is a symbolic link to '/the/new/location/here'.

Upon doing this, CVS integration broke for all projects, and all CVS repositories (despite the other repositories not being moved).

Under the version control tab for all projects we were seeing:
An unknown error occurred - actions == null.

And when testing the configuration we were seeing the error:

Error obating lock.
com.atlassian.jira.util.LockException: Could not obtain lock '/var/jira/logs/cvslog.write.lock' in 10000 msecs.
at com.atlassian.jira.vcs.cvsimpl.CvsRepositoryUtilImpl.updateCvs(CvsRepositoryUtilImpl.java:246)
...

Upon removing the cvslog.write.lock this error disappeared for the other repositories, and it wasn't until I added the aboslute new path to the repository we moved, that things started behaving correctly again.