#52 git-annex: openFile: resource busy (file is locked)

Closed
opened 2 years ago by pgoltstein · 3 comments

Hi,

Thanks for gin.g-node, I really like it for sharing my data! Usually I use the web interface, but just now, I tried using the CLI client as I like make use of the functionality of syncing a local repo with the online repo.

Unfortunately I get an error from git-annex when using 'gin upload', or 'gin commit': "git-annex: openFile: resource busy (file is locked)"

I tried removing the .lck files in the git/annex folder, but that did not help.

I'm working on a MacBook Pro (late 2017), OS X version 11.4 (Big Sur) Versions: GIN command line client 1.12 Build 001474, git: 2.14.1, git-annex: 8.20210428

Any help would be welcome, hope it can be solved, looking forward to using the command line tool :-)

Cheers, Pieter

Hi, Thanks for gin.g-node, I really like it for sharing my data! Usually I use the web interface, but just now, I tried using the CLI client as I like make use of the functionality of syncing a local repo with the online repo. Unfortunately I get an error from git-annex when using 'gin upload', or 'gin commit': "git-annex: openFile: resource busy (file is locked)" I tried removing the .lck files in the git/annex folder, but that did not help. I'm working on a MacBook Pro (late 2017), OS X version 11.4 (Big Sur) Versions: GIN command line client 1.12 Build 001474, git: 2.14.1, git-annex: 8.20210428 Any help would be welcome, hope it can be solved, looking forward to using the command line tool :-) Cheers, Pieter
Achilleas Koutsou commented 2 years ago
Owner

This doesn't seem to be related to the .lck files. It appears it's an OS level error message that comes from trying to write to a file that's already in use and locked. But it's also strange that it doesn't name the file (see for instance this old discussion on the git-annex site).

Are any of the files in the repository open in a different application?

This doesn't seem to be related to the .lck files. It appears it's an OS level error message that comes from trying to write to a file that's already in use and locked. But it's also strange that it doesn't name the file (see for instance [this old discussion](https://git-annex.branchable.com/forum/git-annex__58___openFile__58___resource_busy___40__file_is_locked__41__/) on the git-annex site). Are any of the files in the repository open in a different application?
Pieter Goltstein commented 2 years ago
Poster

Thanks, that helped .. somewhat ;-) It seems to be an issue related to that I had the data on an external ExFAT formatted drive, and was trying to upload it using my MacBook.

The CLI works indeed otherwise fine with repos that are on my main drive (which has an APFS file system) and also on a windows computer that has an NTFS file system.

In any case, thanks for directing me to the git-annex discussion, as a workaround, if the repo would be too large for my internal drive, I guess I can get an extra external drive and format it as APFS then.

Thanks, that helped .. somewhat ;-) It seems to be an issue related to that I had the data on an external ExFAT formatted drive, and was trying to upload it using my MacBook. The CLI works indeed otherwise fine with repos that are on my main drive (which has an APFS file system) and also on a windows computer that has an NTFS file system. In any case, thanks for directing me to the git-annex discussion, as a workaround, if the repo would be too large for my internal drive, I guess I can get an extra external drive and format it as APFS then.
Achilleas Koutsou commented 2 years ago
Owner

Thank you for letting me know what the issue was in the end. Not sure there's anything we can do about it currently, but it's good to be aware in case it crops up again.

Thank you for letting me know what the issue was in the end. Not sure there's anything we can do about it currently, but it's good to be aware in case it crops up again.
Sign in to join this conversation.
No Milestone
No assignee
2 Participants
Loading...
Cancel
Save
There is no content yet.