-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
External Library - Delete Library, also deletes all files on the storage #9460
Comments
There is a major update to the external library now, which is already editable. |
Yes, that's exactly the problem. External libraries are now editable, we have all been waiting for that, but if you have to delete your library for some reason and it is :rw mounted, all photos are also deleted from the storage, not just removed from Immich. Even though Immich shows the following deletion confirmation. "Are you sure you want to delete this library? This will delete all 90 contained assets from Immich and cannot be undone. Files will remain on disk." |
Happened to me today, immich wouldn't read the data in the external library, so I decided to delete it, and it erased all my pictures (11,000). I'm hoping to recover them. This needs an urgent fix! |
The PR removed the |
We are looking into this. |
The bug
If you delete an external library, not only the assets in Immich will be deleted but also all assets from /import on your storage, even if the confirmation says otherwise.
"Are you sure you want to delete this library? This will delete all 90 contained assets from Immich and cannot be undone. Files will remain on disk."
if something is missing and the problem cannot be reproduced, please let me know what else is needed.
The OS that Immich Server is running on
Unraid 6.10.12
Version of Immich Server
v1.104.0
Version of Immich Mobile App
1.103.1 build.137
Platform with the issue
Your docker-compose.yml content
.
Your .env content
.
Reproduction steps
Relevant log output
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: