Re-Index files with missing meta-data only?

[srett]

So, I've not payed attention and the drive where the permanent storage of Photoprism is located filled up.

This happened when I added about 3000 photos and started indexing, this went well for a for a while but eventually the storage dir was full and the log got spammed with entries like

level=info msg="metadata: failed parsing GPS coordinates in IMG_20151110_140440.jpg (exif)"
level=error msg="mkdir /photoprism/.photoprism/storage/cache/thumbnails/e/0/3: no space left on device"
level=error msg="media: failed creating thumbnail for IMG_20151110_140440.jpg (mkdir /photoprism/.photoprism/storage/cache/thumbnails/e/0/3: no space left on device)"
level=error msg="mkdir /photoprism/.photoprism/storage/cache/thumbnails/e/0/3: no space left on device"
level=error msg="media: failed creating thumbnail for IMG_20151110_140440.jpg (mkdir /photoprism/.photoprism/storage/cache/thumbnails/e/0/3: no space left on device)"
level=error msg="index: media: failed creating thumbnail for IMG_20151110_140440.jpg (mkdir /photoprism/.photoprism/storage/cache/thumbnails/e/0/3: no space left on device) in 2015/11/10/IMG_20151110_140440.jpg (detect colors)"
level=info msg="media: IMG_20151110_140440.jpg was taken at 2015-11-10 14:04:40 +0000 UTC (meta)"
level=error msg="mkdir /photoprism/.photoprism/storage/cache/thumbnails/e/0/3: no space left on device"
level=error msg="media: failed creating thumbnail for IMG_20151110_140440.jpg (mkdir /photoprism/.photoprism/storage/cache/thumbnails/e/0/3: no space left on device)"
level=error msg="mkdir /photoprism/.photoprism/storage/cache/thumbnails/e/0/3: no space left on device"
level=error msg="media: failed creating thumbnail for IMG_20151110_140440.jpg (mkdir /photoprism/.photoprism/storage/cache/thumbnails/e/0/3: no space left on device)"
level=error msg="mkdir /photoprism/.photoprism/storage/cache/thumbnails/e/0/3: no space left on device"
level=error msg="media: failed creating thumbnail for IMG_20151110_140440.jpg (mkdir /photoprism/.photoprism/storage/cache/thumbnails/e/0/3: no space left on device)"
Sep 29 07:02:18 schublade systemd-nspawn[27822]: mkdir /photoprism/.photoprism/storage/sidecar/2015: no space left on device
level=error msg="index: open : no such file or directory in 2015/11/10/IMG_20151110_140440.jpg (update yaml)"
level=error msg="media: failed creating fit_2048 (mkdir /photoprism/.photoprism/storage/cache/thumbnails/e/0/3: no space left on device)"
level=error msg="index: failed creating thumbs for IMG_20151110_140440.jpg (mkdir /photoprism/.photoprism/storage/cache/thumbnails/e/0/3: no space left on device)"
level=info msg="index: added main jpg file 2015/11/10/IMG_20151110_140440.jpg"

Now all affected files are somehow considered indexed but don't appear in most (all?) views and don't have thumbnails. Is there a way to re-index those affected files? I'm afraid a complete rescan would take days if not weeks...

On a side note: I couldn't even log in to the webgui when there was no space left, this is how I actually noticed something was wrong, but lead me into a completely wrong direction, since all requests to /api/v1/photos resulted in "400 Bad Request". I thought my nginx config was to blame that I actually updated just before I started the import...

[lastzero]

You can reindex a particular folder incl subfolders. Since PhotoPrism indexes in deterministic order, this should work if errors started at a specific point.

[srett]

Thanks; it's a merged directory structure so it will reindex some old photos, but I think that's bearable in my case, it affects only about two years.

EDIT: This was already half done, but I found a simple hack:
UPDATE files SET mod_time = 1 WHERE file_error LIKE '%no space%';
And then do a normal rescan.

EDIT2: This still left some photos improperly indexed, with errors like:

2021-10-02 10:52:00 ERRO index: image: unknown format in 2011/04/10/CIMG6218.JPG (detect colors)
2021-10-02 10:52:00 WARN metadata: unknown json in 2bd1ea7ebd7c595cf2465634227362a8d33c7803_exiftool.json

Which could be fixed by doing find /photoprism/storage/ -type f -size 0 -delete and rescanning once again.