-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Managed to "conflict on lock" while updating zarr dandisets #42
Labels
bug:crash report
Issue describing an undesirable failure of backups2datalad
zarrs
Handling of Zarr assets
Comments
result of check /reset of zarrs
|
rerun seems to fail on pushing some zarrs
and 000026 remained dirty upon this
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug:crash report
Issue describing an undesirable failure of backups2datalad
zarrs
Handling of Zarr assets
not yet sure what/why but during one of the recent updates of 000026 we got into failed state
fatal: Unable to create '/mnt/backup/dandi/dandizarrs/fa9baf63-da85-4623-b84c-551ff510574b/.git/index.lock': File exists.
I double checked that that zarr is from 000026
I now reset (
git reset --hard; git clean -dfx
)dandi@drogon:/mnt/backup/dandi/dandizarrs/fa9baf63-da85-4623-b84c-551ff510574b$ git reset --hard ; git clean -dfx Updating files: 100% (10241/10241), done. HEAD is now at 1a537c8 Exclude .dandi/ from git-annex Removing 0/ Removing 1/ Removing 2/ Removing 3/ Removing 4/
will check recent zarrs (Disabled cron) and will reset 000026 and redo cron...
The text was updated successfully, but these errors were encountered: