Lightroom 3.6 File Corruption

Lightroom version 3.6 (on MacOSX 10.7.2 with Core2Duo and 8GB RAM) is throwing up spurious "the file appears to be unsupported or damaged" errors on files. The files in question are Canon CR2's (5DII) that were converted to DNG by Lightroom on import and are stored with the catalogue on a disk to the application. Only a comparitively small number of images appear to be affected and there is no obvious predictor as to which are affected. The files appear to break in use - some were successfully edited in LR3.6 prior to starting to generate the corruption warning.
The corruption message appears spurious: the files open correctly in other applications such as Photoshop.
Reverting to Lightroom 3.5 appears to fix the problem, but looses the new camera support in 3.6.
Unfortunately, my impression is that LR3.6 on a Mac is not fit for use. Other problems I have had in the last few days are complete application hangs, while LR also continues to completely stuff the console logs full of debug error messages. I can only assume that no QC was applied to this release. Fortunately, LR3.5 appears more reliable.

I have the same problem.
Macbook Pro 2.2 GHz Intel Core i7
8GB RAM
OSX 10.7.2
LR 3.6
Canon 5D Mark II RAW files. I'm not using DNGs.
It's fairly consistent how it happens for me. The problem surfaces if I don't allow the entire preview to render before rating the image. Then Lightroom becomes unresponsive, I get the spinning beachball, and then I have to Force Quit out of Lightroom. When I open LR backup, whatever photo I was on last is now considered damaged or corrupted. Luckily, what I'm usually doing is quickly rating the "1-Star" photos that I want to throw out anyway, so I don't really care if it's damaged at this point. Right now, the problem is merely annoying for me. However, I can think of instances when this would be extremely problematic (say, if I was trying to select my Best Picks and it resulted in corrupted files).
Would love to hear any solutions to this issue other than downgrading...

Similar Messages

Lightroom 3 Help file corrupted??? Help!

After using LR 3 since upgrade the help file says, as of today, it was improperly installed and not available.
How do I reinstall just the help??
I've checked all the possible Adobe on-line resourses and even tried to call .. wait time is beyond my capability at this time .. I am at Photoshopworld in Orlando. Johhny L, exec. Vp. of Adobe addressed us this morning but I don't think he has ever had a problem getting help from his company. the Lab guru was here with what to expect .. great show.
But, I need h-e-l-p ... please?
Ed

Ed,
If you're on windows, try uninstalling "Adobe Community Help" and reinstall it from here.
Beat

Lightroom 3 - some imported files corrupted

I recently discovered a strange problem. Every once in a while I find files imported by lightroom from my CF card are getting corrupted. Maybe corruption isn't the right word because the files are still readable, but they aren't the same as the file on the CF card. See the example screenshot below of a RAW file that shows this problem.
When I discovered this file in lightroom I went back to the CF card and copied the same file to my hard drive and imported it into lightroom and there was nothing wrong with it. This is the 2nd time this has happened to me and it is something I have only noticed within the last couple of weeks. I haven't done any updates to lightroom recently. I'm using lightroom 3.2.
To make matters even worse I just discovered today that the lightroom import is also corrupting video files only with video files it is not immediately obvious until you play them from start to finish and discover a split second smearing or glitch during playback. Just like the RAW files the damaged video files were fixed by simply copying them from the CF card and overwriting those imported by lightroom.
I compared sizes of the corrupted RAW file and good RAW file and the corrupted file was about 90 kilobytes smaller. With video files that was not the case. They were identical in size.
Is anyone else having this issue? Logically I don't see how lightroom would be causing this problem as I suspect it is only using operating system file copy functions to perform this operation, but with the corrupt versus good RAW file sizes differing it certainly points to something not being handled the same way when imported by lightroom.
Some additional details regarding my setup.
27" iMac running snow leopard 10.6.5
Image and Video files from a Canon 7D
Lexar Professional 600x 16GB CF card
Lightroom version 3.2
Mark

Hi,
I have discovered the same or a least a similar problem on my PC. LR3.3 says in my translated words " Photo aapears to be corruped" (Das Bild ist anscheinend beschädigt).
When searched through the Win7 foren there seem to be more people having that problem - but very little idea of a solution.
On ma PV I worked with the built-in card reader when expirienced the problem first. A short period later the system did not accept 16 GB cards. I used an external reader and everything works fine. But the problem with the corrupted files came (back) infrequently. Now I have to restart my PC before I can read CF cards and import them to LR3. Very strange.
Is there anybody haveing a glue what happens?
I would appriciate any hint.
Henry

More jpg file corruption

I've had another jpg file corrupted in the same manner as before and this time the file hasn't been touched recently by anything but LR. My second copy was also corrupt because I "back up" too often. Fortunately, it's easy for me to get files back from my internet backup, which is written only once. To get to my CDs or DVDs would require digging in a closet.
To me this brings a lot of issues to the fore with jpg handling, both what I do with them and what LR does with them. First, if you are going to rewrite files frequently (I only write metadata on demand, not automatically) then you have to know how to do it safely! On my side, it may be stupid to write it out -- nope, not, because I have to in order to edit in PS and retain the metadata. I have almost innumerable LR backups and the metadata is in there. I have considerable experience now in plopping in an absolute original file and LR happily applies everything to it. Hum. I'm forgetting the PS edits which would not be backed up with this plan.
The existence of 1 to 1 previews makes it very slow to SEE a problem in LR. I haven't used these files for months until the 9th when I started working on them. The first day or so it was grinding a lot, obviously making previews. So the good preview of this file had to be made on the 9th or a bit after so the file was OK at that time. In fact, everything looked fine until I decided to edit a copy of the file in PS. It stumbled and flickered the screen and then created a preview with only the top third or so of the file intact and the bottom part "faded." These appear to still be (almost) valid jpg file, but the content has been damaged.
I have used jpg files for years and I don't remember a time when I've had jpg file corruption. I may have forgotten an instance, but it doesn't come to mind. I've had 3 or 4 them now with LR.
These jpg files were created from scans and I have manipulated them to put the capture date, date digitized, and some global type information. I use exifer, a product that's been used for many years by many people (and not updated recently). If exifer is a problem, why only a handful of corruptions in thousands of files?
It's difficult to have a sensible backup plan except to keep the originals somewhere really safe. Even with metadata writing turned off by default, these files churn. I cannot keep every version of jpg files. And keeping the old files for a short period does not help because bad files don't show up in LR under many circumstances because of the preview files.
I don't know if this is relevant but I never had this happen with LR 1.0.
This is very worrisome and I'm going to get grouchy soon! You guys with RAW are really lucky that LR doesn't write to your files! I'd now love to have an option of a sidecar file which I could write to the jpg only when I'm ready to and have a way to check that the resulting file is still intact.
Of course I haven't proven there isn't an issue with my disk drive, but I've now proven it to myself that there's a very high probability that LR is corrupting jpg files when writing out metadata. I would like to hear if others using jpg files have had corruptions.

Hi, I too also have just experienced jpg corruption. It was a jpg that had been taken several years ago and had not been edited at all. The bottom left hand corner had been transposed from the right hand side. The result of this was the whole bottom 1/5 of the picture was shifted to the right. Also the color of the shifted portion was slightly different from the rest. This is the first jpg corruption in Lightroom I have seen. My backup was the same but fortunately I had a copy on DVD. I am using Windows version of Lightroom 1.2, tried 1.3 and decided to go back to 1.2
Does anyone know if this type of corruption only happens to jpg files. Would it be worthwhile marking them all read-only. I plan to check my other jpgs to see if there are any more corruptions. I mainly shoot RAW now and convert to DNG

Every image I have edited since upgrading to Lightroom 5 has been corrupted.

Every image I have edited since upgrading to Lightroom 5 has been corrupted. First I was shooting in RAW and there was an issuw with my operating system. I upgraded to Maverick and it was supposedly fixed. Then there was an issue because LR didn't work with my camera (Nikon D90) and an update supposedly fixed that. So I finally started shooting JPEGs to try to avoid the RAW issue altogether... Now even the JPEGs say they are corrupted. I am at my wits end! Somebody please help me figure out why I can't seem to do ANYTHING anymore!

>When I go to the files in finder, the corrupted NEFs are not able to be
seen, but the corrupted JPEGs are!
They don't open or do you get a blank screen when you try to open them or
do the files not have icons? It's a good sign that your jpegs are visible
though. That does make me think the preview database or catalog in
Lightroom is screwed up.
>When I try to plug the camera into the computer with a USB cord it doesn't
recognize it
What happens when you plug the camera in turn it on and select import
photos in Lightroom? You should get to see the images on the camera. Try
different USB cables if it doesn't work. Also try changing the USB mode on
your camera. I think the old Nikons had a setting to change between PtP and
Mass storage mode. Just changing it might make it work. This all does smell
a little like the USB ports are bad on the computer something they should
be able to diagnose at the Apple Store but you might want to ask about.
On Mon, Jul 28, 2014 at 3:29 PM, MommaPotts <[email protected]>

Why have all my Lightroom and Photoshop files just developped an awful colour shift? how do I correc

Why have all my Lightroom and Photogshop files suddenly developped an awful colour shift when they did not have this a week ago? I can open them in other applications and they view correctly. How can I correct this in Lightroom? HELP urgent!!

Antonia,
Probably your monitor profile is corrupt.
If you're on Windows, see here:
http://www.lightroomforums.net/showthread.php?14070-How-to-assign-an-sRGB-ICC-Profile-to-y our-monitor-%28Windows%29
If you're on a Mac, you'll need to try something similar to set your monitor profile to sRGB. NOTE: this is merely a temporary fix. You need to acquire a hardware calibrator (decent ones can be had for around $100) and calibrate your monitor with it.
Hal

Canon 7D Imported Files Corrupted.

Every now and them when I import files created with a Canon 7D they show up as corrupted in Lightroom.
I can read and process the files using Canon's Digital Photo Professional. The last time this happened
I deleted the files from the LR catalog then re-imported them and they were ok. This time that does not
seem to be working. I've tried to import the files from two different hard drives. The files were copied
directly from the card to the two hard drives.
I've used digestIT to calculate the MD5 Hash of the files files on the card and after copying them to the
hard drives. The hashes are the same so I'm assuming that the file copy did not corrupt the files.
I've also import the files directly from the card. When I did this only two of the files showed up
as corrupted.
Finally I import the files using the same card and card reader using my laptop. Every thing works, no
file corruption. The laptop is running Windows 7 Home Premium 32 bit and LR 3.3 32 bit.
Any ideas of what may be causing this problem? How do I fix it?
System details:
LR: 3.3 64 bit
OS: Windows 7 Home Premium 64 bit.
Canon 7D: Firmware 1.0.9
LR Cat: New catalog create with LR 3.3 64 bit.
Below are images of what the files look like in LR and DPP. The last images is what happened
when I imported the files directly from the card.
Thanks

martin-s and DdeGannes thanks.
I think I have a better handle on what's happening. I think my storage device is the problem. I guess it could still be
the memory but I would expect the system to be unstable if this were the case.
I imported another set of photos today from a different card. Sure enough one of the files showed up as corrupted in LR. I then
did the following:
1. Attempted to open the file using DPP. The file also showed up as corrupted.
2. Checked the MD5 hash of the file on the drobo against the file on the card. The hashes were different.
     This means that the file copy was bad.
3. Removed the file from the LH catalog.
4. Deleted the file from the storage device.
5. Copied it from the card.
6. Check the hashes to make sure the copy was good.
7. Imported the file into LR.   The preview JPG still showed up as corrupted.
8. I then attempted to open the file in the develop module. It opened ok. Made some adjustments
   then when back to the library module and the preview JPG now looked fine.
I guess removing an images from the catalog does not remove the preview JPG from the catalog. Which
means that if the image is added back to the catalog the old LR generated preview may get reused.

Is there a cure for persistent file corruptions across the suite?

i am having terrible and consistent problems with file corruptions across the suite. for example…
1: i collected for output (indesign) – corrupted over 100 small images that were linked.
2: opened an indesign job and all linked files failed to update and could not be imported (simply would not import those files and were all corrupted).
3: had a hang in photoshop followed by a 150:30 error (would not open any of my applications). this prompted a clean install of system and adobe cs4 see below
4: most recently, had a hang in photoshop (photoshop will also no "force quit") whilst indesign was open. two of my image files corrupted and, most surprisingly, all my illustrator files that i had placed also corrupted (will not even open in illustrator any more). illustrator was not even running at the time, so, get this – a hang in photoshop destroys illustrator files simply because they are placed in indesign.
this last event has made me more certain than ever that there is a fundamental problem at the cs4 core.
can anyone help?
please note the following:
i am running a macintosh imac, 2.66 GHz Intel Core 2 Duo (latest imac), with 4 GB 1067 MHz DDR3 ram.
before this last disaster, i had reloaded the system software (archive and install), and updated it all the way to version 10.5.8
i then uninstalled the creative suite, ran the cleanscript from adobe, reloaded the creative suite, downloaded all the cs4 updates
(so, latest mac, latest system, latest cs4 – all clean installs).
is there something i can do? or is this just a very unstable and disappointing upgrade – i have had nothing but problems from day one!
many thanks if anyone has any advice.

Re: 150:30 error:
Please try this KB article's solutions, and report back on how it went for you. If you can provide details about any recent OS updates, backups, or migrations, that would help is nail down the root cause of the new rash of this error for Mac users recently:
http://kb2.adobe.com/cps/512/cpsid_51260.html

Downlaoded .exe for Firefox5 gives "file corrupted" error when I try to open it

I am running Windows XP on Parallels 5 on top of MAC OSX on an iMac24.
I have no problems downloading Firefox 5 on OSX for Mac, nor for downloading Thunderbird on WinXP/Parallels5.
Just Firefox5.exe comes up "file corrupted" when I try to run it or open it on WinXP/Parallels5.

Post in Microsoft's Powerpoint (Mac) message boards.

Sync File Corruption with 64-bit Vista/iTunes

I'm getting some file corruption problems when trying to sync my new 16GB iPhone with the latest 64-bit iTunes (7.6.0.29). "yes I have the 64-bit version".
The sync seems to go correctly, but I have yet to be able to play any videos all the way through. Videos purchased from iTunes as well as self encoded files. All said files were working on my 60GB iPod Video with previous versions of iTunes on the same 64-bit Vista machine.
The videos will start playing fine, but will eventually reach a point in the file that was corrupted during transfer, the audio will drop out and the video will distort, then it exits from the video as if it reached the end of the file. No error messages or anything. If I play the file again, it will do the same thing at the exact same spot, so its a problem in the file. Now, if I remove the file and add it back, the file still has the same problem, but in a different location, which means the source is fine, but the copy to the device during the sync is the issue.
To test, I synced the exact same content from my notebook which is 32-bit XP, and zero problems. So I'm currently just using my notebook for syncing at the moment.
Anyone else with 64-bit Vista have a similar issue?

Hello
I have a couple troubleshooting steps I would like you to try. I myself do not have a 64 bit Vista so I can not test this to confirm if the same issue occurs or not.
1. Attempt to Sync content using each of the USB Ports. See if all USB Ports pose the same issue with the video. Or if you found when where it does not occur.
2. Test on a new user on the Vista Machine. If possible take at least one or 2 movies and copy them onto a flash drive or something. And bring them into iTunes on a new user account. You may need to Authorize that user and De-authorize when your done. Does the same issue occur?
3. If you perform a reboot on the iPhone, Then Sync Data over. Does the same issue occur?
4. If possible could you restore the iPhone. Then Re-sync and see if same issue occurs.
5. Is this happening with all videos? or only certain ones? Does the corruption occur at the same time frame every time? If so is it the same time frame for all videos or slightly different?
6. Perform an Uninstall and Reinstall of iTunes on your system, See if same issue occurs.
Let us know how it goes.

Why files in Lightroom mobile and files in the creative clouds not the same?

Why files in Lightroom mobile and files in the creative clouds not the same?
Idea was to store date in one place. I have subscribed to photographer option

Do you mean you are trying to sync files from Creative Cloud to mobile and it doesn't work? I don't know much about Lightroom. It's better to ask your question at Photoshop Lightroom.

Why files in Lightroom mobile and files in the creative cloud not the same? idea- one place(stored date) for all application ??????

Why files in Lightroom mobile and files in the creative cloud not the same? idea- one place(stored date) for all application ??????

Lightroom Mobile is not a cloud storage service. You shouldn't treat it as a way of backing up your files. You are merely storing Smart Previews of your files in the cloud space, high-quality JPEGs of your files regardless of their original format on your desktop. The point is that they are there so you can continue editing them in a Lightroom-like environment even while away from your desktop/laptop computer. The files in Lightroom Mobile can only be used in Lightroom Mobile.
This is very different from what is offered by the Creative Cloud storage, which can be used to synchronize your files between any device (that can support the individual files).
The vast difference in how each service works and its intended use is why they are separate.

Transaction log shipping restore with standby failed: log file corrupted

Restore transaction log failed and I get this error: for only 04 no of database in same SQL server, renaming are working fine.
Date
9/10/2014 6:09:27 AM
Log
Job History (LSRestore_DATA_TPSSYS)
Step ID
1
Server
DATADR
Job Name
LSRestore_DATA_TPSSYS
Step Name
Log shipping restore log job step.
Duration
00:00:03
Sql Severity        0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted
0
Message
2014-09-10 06:09:30.37 *** Error: Could not apply log backup file '\\10.227.32.27\LsSecondery\TPSSYS\TPSSYS_20140910003724.trn' to secondary database 'TPSSYS'.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: An error occurred while processing the log for database 'TPSSYS'.
If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
An error occurred during recovery, preventing the database 'TPSSYS' (13:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
RESTORE LOG is terminating abnormally.
Processed 0 pages for database 'TPSSYS', file 'TPSSYS' on file 1.
Processed 1 pages for database 'TPSSYS', file 'TPSSYS_log' on file 1.(.Net SqlClient Data Provider) ***
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 Skipping log backup file '\\10.227.32.27\LsSecondery\TPSSYS\TPSSYS_20140910003724.trn' for secondary database 'TPSSYS' because the file could not be verified.
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 *** Error: An error occurred restoring the database access mode.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteScalar requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 *** Error: An error occurred restoring the database access mode.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteScalar requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 Deleting old log backup files. Primary Database: 'TPSSYS'
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 The restore operation completed with errors. Secondary ID: 'dd25135a-24dd-4642-83d2-424f29e9e04c'
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 *** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.38 ----- END OF TRANSACTION LOG RESTORE
Exit Status: 1 (Error)

I Have restore the database to new server and check with new log shipping but its give this same error again, If it is network issue i believe issue need to occur on every database in that server with log shipping configuration
error :
Message
2014-09-12 10:50:03.18   *** Error: Could not apply log backup file 'E:\LsSecondery\EAPDAT\EAPDAT_20140912051511.trn' to secondary database 'EAPDAT'.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-12 10:50:03.18   *** Error: An error occurred while processing the log for database 'EAPDAT'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
An error occurred during recovery, preventing the database 'EAPDAT' (8:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
RESTORE LOG is terminating abnormally.
can this happened due to data base or log file corruption, if so how can i check on that to verify the issue
Its not necessary if the issue is with network it would happen every day IMO it basically happens when load on network is high and you transfer log file which is big in size.
As per message database engine was not able to restore log backup and said that you must rebuild log because it did not find out log to be consistent. From here it seems log corruption.
Is it the same log file you restored ? if that is the case since log file was corrupt it would ofcourse give error on wehatever server you restore.
Can you try creating logshipping on new server by taking fresh full and log backup and see if you get issue there as well. I would also say you to raise case with Microsoft and let them tell what is root cause to this problem
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

"FILE CORRUPTED" error message on N 78

My phone is a Nokia N78 and my problem is as followed:
Before updating the firmware from version 12 to version 20, I had google maps installed. After updating over the air, google maps (and also several other apps) got removed. When i tried to download and install google maps again and tried to install it again, it keeps saying "file corrupted". The same goes with other apps i try to download and install. But I have no trouble installing java apps.
I am wondering if anyone knows how to solve this problem?
Solved!
Go to Solution.

you are very welcome i am so glad that you got your issues sorted. i know how frustrating it can be to have a phone and potentially no 'way out'. been there and done that, that is why i joined this forum i wanted to learn more and find more answers to some questions. technology in general can be frustrating and its ever changing so we have to keep up or we will drown in frustration be well, rad.
ps. and you are correct, i am no expert, my solution is not expert either more of a been down this road solution. i am just another user on this forum that sometimes gets the right answer
Message Edited by radical24 on 19-Jan-2009 07:54 PM
You know what I love about you the most, the fact that you are not me ! In love with technology and all that it can offer. Join me in discovery....

File corruption on SDCard when multiple files are being written from WinCE 6.0R3

We currently have file corruption problems which we have been able to reproduce on our system which uses WinCE 6.0R3. We have an SDCard in our system which is mounted as the root FS. When multiple files are being written to the file system we occasionally
see file corruption with data destined from one file, ending up in another file, or in another location in the same file. We have already written test SW that we have been able to use to reproduce the problem, and have worked with the SDCard vendor to
check that the memory controller on the card is not the source of the problems.
We know that the data we send to WriteFile() is correct, and that the data which eventually gets sent through the SDCard driver to the SD card is already corrupted.
We believe that the problem is somewhere in the microsoft private sources between the high level filesystem API calls and the low level device calls that get the data onto the HW.
We have confirmed that the cards that get corrupted are all good and this is not a case ofpoor quality flash memory in the cards. The same cards that fail under WinCE 6.0R3 never fail under the same types of testing on Windows, Mac OX, or linux. We
can hammer the cards with single files writes over and over, but as soon as multiple threads are writing multiple files it is only a matter of time before a corruption occurs.
One of the big problems is that we are using the sqlcompact DB for storing some data and this DB uses a cache which get's flushed on it's own schedule. Often the DB gets corrupted because other files are being written when the DB decides to flush.
So we can reproduce the error (with enough time), and we know that data into the windows CE stack of code is good, but it comes out to the SDcard driver corrupted. We have tried to minimize writes to the file system, but so far we have not found a
way to make sure only one file can be written at once. Is there a setting or an API call that we can make to force the OS into only allowing one file write at a time, or a way of seeing how the multiple files are managed in the private sources?
Thanks
Peter

All QFE's have been applied we are building the image so we have some control.
I have build an image which used the debug DLL's of the FATFS and I have enabled all of the DebugZones. The problem is still happening. From the timings in the debug logs and the timestamps in the data which corrupts the test file I have been able
to see that the file is corrupted AFTER the write is complete. Or at least that's how it seems.
We finished writing the file and closed the handle. Then more data is written to other files. When we get around to verifying the file it now contains data from the files that were subsequently written.
What I think I need to do is figure out in detail how the two files were "laid down" onto the SDCard. If the system used the same cluster to write the 2 files then that would explain the issue.

Lightroom 3.6 File Corruption

Similar Messages

Maybe you are looking for