Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'File system journaling won't prevent all disk damage' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
File system journaling won't prevent all disk damage
Authored by: johnsawyercjs on Jan 31, '05 11:49:52PM

* The files named "ClipWorks 2.0.1.sit alias" differ at offset 2559 (09FF hex) in the RESOURCE fork.


* An error occurred while getting the location of a file being written. File system I/O error.

The errors gmachen cites in the message above, referring to resource fork errors, are references to file damage, not directory damage, except the last error, which may refer to directory damage--it's too generally worded to tell. Though directory damage can cause file damage, I'd be careful about interpreting file damage as directory damage--files can get damaged even if a volume's directory remains pristine.

[ Reply to This | # ]