Final Cut doesn't delete the .lock files when closing a project

Question

Level 1

4 points

Final Cut doesn't delete the .lock files when closing a project

I have my projects on an NFS file storage. I clearly have permissions to write to and read from these locations, but Final Cut never deletes the .lock files when I close it. Each time I open a project, I get the "<project> is already in use by <me> on <my laptop>" and I have to manually go into the project and delete the .lock files.

I can't find any information at all on this, and permissions are definitely correct. I don't need administrative permissions to delete the .lock files, so there's no reason Final Cut shouldn't be able to either. Final Cut cleanly shuts down every time, so it's not crashing and therefore not getting the opportunity to clean up after itself.

Libraries locally on my Mac are fine, so it definitely has something to do with them being on an NFS share. But that's a common use for users of Final Cut, so I don't see why that itself would be an issue.

This is the command I use to mount the NFS share on my Mac:

sudo mount -t nfs -o resvport,rw,vers=4 10.9.0.9:/mnt/storage_1/ /Volumes/storage_1

This is the /etc/exports file on the Linux machine hosting the share:

/mnt/storage_1		10.9.0.0/23(rw,sync)

Here are the files as listed on the Linux machine:

$ ls -l /mnt/storage_1
total 24
drwxr-xr-x 6  501   20  4096 Sep  4 15:36 Project.fcpbundle
drwxr-xr-x 3  501   20  4096 Sep  4 15:02 Footage
drwx------ 2 root root 16384 Sep  4 10:37 lost+found
$ ls -la /mnt/storage_1/Project.fcpbundle/
total 224
drwxr-xr-x 6  501 20   4096 Sep  4 15:36  .
drwxrwxr-x 5 root 20   4096 Sep  4 15:02  ..
drwxr-xr-x 5  501 20   4096 Sep  4 15:17  4-09-2024
-rw-r--r-- 1  501 20 188416 Sep  4 15:16  CurrentVersion.flexolibrary
-rw-r--r-- 1  501 20    152 Sep  4 15:02  .CurrentVersion.flexolibrary-conch
-rw-r--r-- 1  501 20    326 Sep  4 15:02  CurrentVersion.plist
lrwxrwxrwx 1  501 20      1 Sep  4 15:36  .fcpcache -> .
-rw-rw-rw- 1  501 20      0 Sep  4 15:36  .lock
drwxr-xr-x 2  501 20   4096 Sep  4 15:36  .lock-dir
-rw-r--r-- 1  501 20    360 Sep  4 15:36  .lock-info
drwxr-xr-x 2  501 20   4096 Sep  4 15:02 'Motion Templates.localized'
-rw-r--r-- 1  501 20    265 Sep  4 15:02  Settings.plist
-rw-r--r-- 1  501 20      0 Sep  4 15:36  __Sync__
drwxr-xr-x 2  501 20   4096 Sep  4 15:02  __Temp

I'd post Final Cut logs, but the program doesn't seem to log anything to files and it barely logs anything at all to the terminal, let alone anything useful.

Although it's fixable by manually deleting the .lock files every time, I don't like it as it's error prone and possibly indicative of some other root issue. But I can't figure out what is happening and I can't find any good results anywhere.

Posted on Sep 4, 2024 6:42 AM

Reply

Answer 1

terryb

Level 4

2,638 points

Sep 4, 2024 11:39 AM in response to Veeetle

I suggest using FCP Feedback to raise the issue. On occasion I have received a followup from the developers.

Final Cut Pro->Provide Final Cut Pro Feedback... or use this link Feedback - Final Cut Pro - Apple

In the meantime you could probably write a shell script or a cron job that runs at 3 AM to delete .lock files.

Reply

Answer 2

Tom Wolsky

Level 10

152,015 points

Sep 4, 2024 9:27 AM in response to Veeetle

FCP documentation says it requires macOS drives. Obviously I don’t know if this is the cause of the issue, but it may well affect library bundles. I know ExFAT has problems dealing them correctly.

Reply

Answer 3

Sep 4, 2024 7:23 AM in response to Veeetle

Sorry, I don't know why FCP is failing to delete the lock files.

At the moment the only suggestion that occurs to me is to try manually closing the libraries in question before quitting: either by control-clicking and choosing "Close Library <name>" or by selecting and choosing the same command from the File menu.

Does manually closing the library in the manner described above result in the correct deletion of the lock files?

Reply

Answer 4

Veeetle Author

Level 1

4 points

Sep 4, 2024 7:57 AM in response to Tom Wolsky

They are EXT4

$ lsblk -f
NAME    FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1 ext4   1.0         bc8a8689-3107-4908-8e68-c2bb8348a5bc    3.4T     1% /mnt/storage_1
nvme1n1 ext4   1.0         c9e5035d-cfb5-488f-9fff-61ea317898f4  556.3G    80% /mnt/storage_0

Reply

Answer 5

Veeetle Author

Level 1

4 points

Sep 4, 2024 9:16 AM in response to Tom Wolsky

I can't format the drives for APFS or HFS on a system running Linux. As far as I can tell, NFS is explicitly supported in Apple's documentation, and either way the underlying file system shouldn't matter to FCP when accessing a network share.

The mounted share supports Extended attributes for files and directories, so I don't see a technical reason why APFS/HFS vs. ext4 would make a difference to FCP. If the drives were formatted as NTFS or exFAT, then it would likely be a different story.

Or have I got this wrong? Is NFS not explicitly supported for shares on a Linux host? Is NFS support primarily for shares on a macOS host?

Reply

Answer 6

BenB

Level 6

12,643 points

Sep 4, 2024 10:59 AM in response to Tom Wolsky

Yes, macOS can work with NFS drives, with limits.

Individual applications have more limits than the OS does, and thus, FCP won't work properly unless it's an APFS or HFS formatted drive.

As a former IT Engineer, I can tell you there are lots and lots of technical reasons for this. Even if Linus and macOS are both just flavors of UNIX, still, not all UNIX flavors are compatible with each other, nor are their drive formats.

Reply