Error, then LOTS of edits lost (sort of)

Status
Not open for further replies.

Linwood Ferguson

Linwood Ferguson
Lightroom Guru
Premium Classic Member
Premium Cloud Member
Joined
Jan 18, 2009
Messages
2,620
Location
Fort Myers, FL
Lightroom Experience
Advanced
Lightroom Version
Classic
I had a strange event today.

I am running 2.3 (final), on Vista, 4G memory, fast raid disks.

I occasionally get errors in lightroom. I spent about 7 hours on it today, and got two persistent out-of-memory error (red letters in image pane). Each time I exited lightroom, restarted, went back to work. No big deal.

The second time when I came back up I had a very strange problem. First time ever.

First let me say that my understanding, and experience, is that when LR dies, it has committed whatever the last function was to the database and you lose only what you were immediately doing, plus some context (I think it only takes you back to the shot you were on and context you were in during the last normal shutdown).

This time... not so much. This time when LR came back up instead of the roughly 6' shots I should have had in that folder, I was up around 3''. It had forgotten that I had deleted hundreds of shots (via reject then delete-rejected-photos). Note that before the first crash I went from about 49' shots to around 3''. The second time from about 3'' to 6'.

Of course they were really gone -- the thumbnails and frames were empty (emphasis on thumbnails were gone also). The disk files deleted (correctly). It gave the error about "cannot locate". It was exactly the right set of shots, i.e. all the empty slots were ones I deleted, but the catalog thought I had not deleted them even though gone from disk.

Then I manually deleted each of these empty thumbnails by selecting them and deleting them from lightroom, thinking "strange" and moving on. But...

I noticed a LOT of edits missing, crops, adjustments. Hmmm.... then I notice one of the ones I just touched saying it had a metadata conflict (I keep XMP files on disk also). So, with a bit of fear, I do a synchronize...

It finds no missing shots (i.e. images not in catalog), so I leave the metadata checked and continue. And slowly all the thumbnails start popping back to having my edits in them.

Apparently the catalog had lost hours of both picture deletes, AND edits.

After the import, all the remaining shots looked OK, just the history was gone. Darn good thing I kept the XMP files on disk as well, saved me a LOT of recovery.

I did a check integrity on the catalog (no errors). And have edited a few hours since. I am slightly annoyed by the lightroom occasional crashes, but until today I had never had it lose anything but the last edit.

Anyone else ever see this?

It's remotely similar to the "undo" problem I had back in 2.mumble, a while ago, where a whole session was undone unstead of the last operation. But I did NOT hit Control-Z.

I think somehow it rolled back everything updated in the catalog since the beginning of the session. Possible? Anything I did? Or could do to prevent? Or could have done to fix?

Thank goodness for XMP files!
 
Linwood, Yikes! That's truly weird (not to say disconcerting). No, I haven't heard of anything similar, that didn't involve a) the Windows only Ctrl-Z bug (which was identified as repaired in 2.3) or b) some sketchy operator errors. Sounds like you didn't invoke the a) and have a pretty good grasp on avoiding b).

Please, if you would file a bug report, highlighting the facts and step-wise process as well as you can. There's a link at the top of the thread.
 
Brad Snyder;4'4'5 said:
Please, if you would file a bug report, highlighting the facts and step-wise process as well as you can. There's a link at the top of the thread.

Yeah, I do photography for fun, computers for a living. Bug reports you can't repeat aren't a lot of use. One reason why these forum reports are sometimes helpful -- maybe someone else experiencing it will add something, and a pattern noticed.

Or maybe it was a cosmic ray. :?

But now I'm a definite convert to using XMP files! I originally did it in case I wanted to go back to Bridge (I never did). Now I can just think of them as suspenders.
 
Ferguson;4'422 said:
But now I'm a definite convert to using XMP files! I originally did it in case I wanted to go back to Bridge (I never did). Now I can just think of them as suspenders.

Me too. :) Although forum guru Mark Sirota, another IT guy, considers it a workflow complication and performance waster, and relies on his impeccable backup hygiene. (I'm sure he can speak for himself, but he hasn't posted for a couple of days, so he might be vacationing :) or working :( or something.)
 
Wait... I lied. Much earlier in the day (but I think in the same session) I remember hitting control-Z when editing. But it seemed to have worked (on that image) and I put it out of my mind, mentally slapping myself as I had tried to never do that.

I was in the process of individually going through each shot while in develop, and much later it got the out of memory and I exited. That's when I restarted it and it came back with everything restored.

So it is POSSIBLE that the event that triggered this was actually the control-Z. Maybe.

When I get some time I am going to set up a new catalog and experiment, see if I can reproduce the control-Z failure. I do recall it was when using an adjustment brush that I used it (and it apparently worked). Maybe it un-did a lot more, and I didn't notice for the next hour or so. Maybe.
 
Brad Snyder;4'425 said:
Me too. :) Although forum guru Mark Sirota, another IT guy, considers it a workflow complication and performance waster, and relies on his impeccable backup hygiene.

I like to think I have a pretty impeccable backup process also, but it doesn't involve backup DURING my editing sessions. That's what was so disturbing about this, it was a loss of a lot of work (or almost was absent XMP's) during one multi-hour session.

Databases should be "safe" at least as long as I can sit in one place working. :x

More if I get time and a bit of luck to reproduce an "undo" problem.
 
I'm with you, the DB should be bulletproof while open, at most one operation at risk. I know there's some sort of journaling going on, but apparently it's not foolproof....
 
Brad Snyder;4'425 said:
Although forum guru Mark Sirota, another IT guy, considers it a workflow complication and performance waster, and relies on his impeccable backup hygiene. (I'm sure he can speak for himself, but he hasn't posted for a couple of days, so he might be vacationing :) or working :( or something.)

I was indeed off on an amazing photography workshop in Savannah, but I'm back now.

That's a wonderfully concise explanation of my position, Brad. But my approach is only valid if the software also does its job; in this case Lightroom or SQLite or something related failed, and so in this case belt-and-suspenders was clearly a big win.
 
I created a new catalog and spent some time trying to make un-do misbehave, or make LR "forget" some edits by exiting, combinations of it and undo.

Everything worked perfectly. I wasn't patient enough to try it after hours of editing, which is what I was doing when this happened.

Sigh.

The more I think about this, I am betting it is not a broken database but some kind of mis-handled feature of the database where LR rolled back changes too far. Like a transactional context never closed (e.g. if you nested transactions in a database, and started 3 and committed 2, one is still out there hanging and might be rolled back by accident, like an unexpected abort).

I have no evidence, but that is what it 'feels' like. It loses count, then when something else happens, it rolls back too far.
 
Don't you just hate things like that.... however hard you try, you can't figure out what happened! Well let's hope it doesn't happen again!
 
Status
Not open for further replies.
Back
Top