Hi Michael and forum members-
I’ve been testing Eaglefiler since just after Christmas, and loving it so far. I’m enjoying using the software, and I’ve also been very impressed at the breadth and helpfulness of the information in the forum.
But last night I got an alarming message warning me files were corrupted. Today I researched in this forum and the manual, which led me to find the Eaglefiler Log (I’ll excerpt below) which did indicate some corruption. I also discovered Verify, and when I tried it on all the records in the 2 libraries I’ve created so far, all but one file tested OK (i.e. failures were 0 except for that one). Oddly, that file is not in the library listed in the log as having a problem; it’s in the other one.
I’m not terribly technically savvy, so please forgive any inadvertent misuse of terms. What I’d like to know is the following:
1 - Do I have a problem with corrupted files, or if they test out okay with Verify have they somehow repaired themselves? (and I don’t need to worry about it).
2 - Is it possible to tell from the log how they became corrupted, and if so, was it something I did (and can avoid in future)?
The library is still very small–I could either start from scratch to rebuild it, or could follow the directions in the 10/08 discussion about corrupted files from davet (which was VERY informative)–but obviously I’m concerned about how quickly and easily I managed to screw it up. I’d very much appreciate your thoughts on how I could prevent doing this in future, because I really like the way Eaglefiler works and could quickly come to depend on it.
Thank you in advance for your help.
Dinah
I’m running 10.4.11 on an eMac. Eaglefiler is on the main computer, but the libraries are both on an external hard drive. So far, I have only received the one alert about corruption. Eaglefiler seems to be running fine, and closes and reopens normally.
Here is yesterday’s activity from the Log. There are some previous entries referring to corrupt files from earlier in the week, but this was the first time I got an actual error message on screen:
2009-01-03 23:35:34,533 - documents.pyc:81 willPresentError: <NSError Domain=com.c-command.EagleFiler Code=0 UserInfo={
NSLocalizedDescription = “Could Not Save Library”;
NSLocalizedRecoverySuggestion = "error: NSInternalInconsistencyException - Fatal error. The database at /Volumes/External HD/Library-First and General/Library-First and General.eflibrary/Contents.db is corrupted. SQLite error code:1
com.c-command.EagleFiler: 0";
traceback = “Traceback (most recent call last):
File “wash/documents.pyc”, line 171, in writeSafelyToURL_ofType_forSaveOperation_error_
File “wash/library.pyc”, line 940, in save
File “wash/storage.pyc”, line 909, in save
File “wash/storage.pyc”, line 659, in propagateChangesToManagedObjects
error: NSInternalInconsistencyException - Fatal error. The database at /Volumes/External HD/Library-First and General/Library-First and General.eflibrary/Contents.db is corrupted. SQLite error code:1”;
}>
2009-01-04 20:28:42,050 - appcontroller.pyc:139 Launched EagleFiler 1.4.3 (on Mac OS X 10.4.11) at 2009-01-04 20:28:42 -0800