8 Messages
•
154 Points
Tue, Mar 31, 2020 9:27 PM
Lightroom Classic: Incorrect flag: "Metadata Was Changed Externally"
I have been using Lightroom 6 on a perpetual license. I store scanned photos in TIFF format on a networked SMB share, for processing in Lightroom. Today, the photos that I had just scanned and imported into Lightroom (with the "synchronize folder" method) showed the icon in the upper right to indicate "Metadata Was Changed Externally". When I click the icon and choose "overwrite settings", the icon disappears but a little while later it appears again. In some cases, a different icon appears which indicates "Metadata has conflict". The icons pop back up like Whack-a-Mole, not on every file at once but on apparently random files.
I have been working off an SMB share for many years and never seen this behavior. I have occasionally seen a "Metadata conflict" when a file had been deleted and replaced but I just had to "overwrite" or "use metadata from disk" one time to fix the warning permanently.
I upgraded to Lightroom Classic on a subscription (v9.2) and still had the flags. After clearing them 2-3 times, they do seem to have gone away.
Any ideas about what might have caused this weirdness, and why it briefly persisted in v9.2 and then went away?
I have been working off an SMB share for many years and never seen this behavior. I have occasionally seen a "Metadata conflict" when a file had been deleted and replaced but I just had to "overwrite" or "use metadata from disk" one time to fix the warning permanently.
I upgraded to Lightroom Classic on a subscription (v9.2) and still had the flags. After clearing them 2-3 times, they do seem to have gone away.
Any ideas about what might have caused this weirdness, and why it briefly persisted in v9.2 and then went away?
Problems
•
Updated
10 months ago
68
11
Helpful Widget
How can we improve?
Tags
No tags available
Responses
john_stimson_79lmn5z4e9woe
8 Messages
•
154 Points
10 months ago
0
0
john_stimson_79lmn5z4e9woe
8 Messages
•
154 Points
10 months ago
0
0
john_stimson_79lmn5z4e9woe
8 Messages
•
154 Points
10 months ago
I do not see any metadata inconsistency flags for the folder that was copied onto the local drive. So it seems this is a problem with working over the network share.
I did upgrade the file server from a much older version of Samba and it is running on a much faster drive (nVME SSD instead of a SATA 3GB hard disk) on the ext4 file system instead of ext3. That was a month ago and I have not worked with Lightroom off the networked folders since then.
0
0
carlos_cardona_4982447
799 Messages
•
11.5K Points
10 months ago
0
0
john_stimson_79lmn5z4e9woe
8 Messages
•
154 Points
10 months ago
0
0
dan_hartford
519 Messages
•
12.6K Points
10 months ago
0
0
john_stimson_79lmn5z4e9woe
8 Messages
•
154 Points
10 months ago
When I select "save metadata to file", the flag is only temporarily cleared. Without doing any other changes, the flag reappears about a minute later. Visiting other existing folders that live on the network share, the folder initially looks clean, then within a minute, flags for out of sync metadata (both "has conflict" and "was changed externally") start to appear on files which have not been changed in months.
0
0
Pipur
7 Messages
•
168 Points
10 months ago
0
dan_hartford
519 Messages
•
12.6K Points
10 months ago
Turn off all backup and syncing tools (including Time Machine) that you may have running on your computer and see if the problem goes away or not.
0
0
john_stimson_79lmn5z4e9woe
8 Messages
•
154 Points
10 months ago
0
0
john_stimson_79lmn5z4e9woe
8 Messages
•
154 Points
10 months ago
So it look like Photoshop is not just accessing the file, but modifying its contents. When I simply open an old file in the Windows photo viewer, none of the times are altered.
Could this possibly be due to a tiny time offset between the server and the client? The client is time-synced to the server via NTP, so when I say a tiny offset, I mean tiny.
Or perhaps something is getting mucked up in the translation between the UNIX atime/ctime/mtime and whatever time attributes that Windows uses. And the default way of handling those mappings has changed between the older version of samba and the new one.
0
0