#Re-upload not possible (works as designed)

1 messages · Page 1 of 1 (latest)

tulip comet
#

I´ve uploaded a bunch of files from my DSLR. Afterwards I modified the GPS location for each file and uploaded the same pictures again. They are now doubled inside immich. Is this works as designed or should the existing files have been replaced (or is there any option to do so)?

tender walrusBOT
#

:wave: Hey @tulip comet,

Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich immich.

References

#

Checklist

I have...

  1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: read applicable release notes.
  3. :blue_square: reviewed the FAQs for known issues.
  4. :blue_square: reviewed Github for known issues.
  5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: uploaded the relevant information (see below).
  7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

Information

In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:

  • Your docker-compose.yml and .env files.
  • Logs from all the containers and their status (see above).
  • All the troubleshooting steps you've tried so far.
  • Any recent changes you've made to Immich or your system.
  • Details about your system (both software/OS and hardware).
  • Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
  • The version of the Immich server, mobile app, and other relevant pieces.
  • Any other information that you think might be relevant.

Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

glacial sequoia
#

It's not the same file after you modified it, so it's working as it should

tulip comet
#

The file hash might be different, but the file itself isn't.

glacial sequoia
#

??? that's a contradictory statement lol

#

If the hash is different then the file certainly is too

tulip comet
#

From the database perspective, true. How about replacing the same file IMGP3668.JPG with a newer version (by date). This way the respective files could be replaced!?

lavish sorrel
#

I don't understand your question. If the file has changed it would be a new asset. You could certainly delete the original upload

tulip comet
#

OK, on a picture by picture base, that would certainly be no issue. But when modifiing a lot of files, this is not handy any more.

#

How about modifing a file which is already in the database? When going to the original file location and let´s say edit the GPS location of a file missing GPS...., what would happen then?

lavish sorrel
#

That might work, but we provide no guarantees as to if it might break immich either now or in the future

#

Mostly because that will change the file checksum which we do track

#

Everything in UPLOAD_LOCATION should be read only