Welcome to the MacNN Forums.

Vanquish · Feb 10, 2003, 12:34 PM

I was using My Ti867 without Journaling enabled because the first time I enabled it on my Ti it made the system go into a crawl (back when I had only 256MB of RAM, when I just bought it), I had it enabled on my PowerMac G4/400 without a performance hit, but now I have 1GB (well already for a long time...) but I never tried to enable it again. And a few days ago my book refused to go to sleep when I closed the lid and it crashed. So I force rebooted it and I discoverd that a bunch of PSD's were corrupted !

(the colors were all deformed). So anyway, now I activated Journaling and I don't really notice a performance hit. Anyway, this was the first time *ever* I suffered file corruption.

So: moral of the story: yay for journaling !

-Q- · Feb 10, 2003, 02:59 PM

Journaling sounds great. I just need a faster machine so I won't notice the performance hit.

Until then, yay for daily backups!

Vanquish · Feb 11, 2003, 09:59 AM

So, what's you backup-method Q ?

someone_else · Feb 11, 2003, 04:31 PM

Originally posted by Vanquish:
And a few days ago my book refused to go to sleep when I closed the lid and it crashed. So I force rebooted it and I discoverd that a bunch of PSD's were corrupted ! (the colors were all deformed). So anyway, now I activated Journaling and I don't really notice a performance hit. Anyway, this was the first time *ever* I suffered file corruption.

So: moral of the story: yay for journaling !

Journaling won't prevent file corruption. It will only *reduce the risk* of *file system* corruption. The two are totally seaparate. File corruption occurs when a file was not properly saved (because you crashed, or the program just went wonky). File system corruption is usually worse because some (or all) of the pointers the OS uses to find your files have been corrupted. The file data is still intact, it just can't be found.

Journaling is a good idea, and it may help. But it should not be thought of a a panacea for general file problems. You should use journaling in conjunction with a good backup plan.

HTH.

rlmorel · Feb 11, 2003, 05:25 PM

Personally, I do not back up every day. I back up every few weeks. I guess it is what your tolerance is for data loss. I purchased a 120 GB FW External Drive, and I use Carbon Copy Cloner every few weeks. I guess if I crash, I might lose a little, I just don't want to lose everything.

Adam Betts · Feb 11, 2003, 05:44 PM

Originally posted by someone_else:
The file data is still intact, it just can't be found.

Is there any way to recover the file data? My bro was using a FCP and it crashed. All of his movie editing files was missing but the hard drive size show that it's still around but not visible.

Do you recommend any disk utilites to recover the data? Any help is appreciated.

Drizzt · Feb 11, 2003, 06:20 PM

for the knowers..

I did a cron job that backups all my data to my Server..

it could have been a HD.. but it's a server

So.. if anyone needs an idea.. I got a daily backup running

(and not needing me to be beside)

Vanquish · Feb 12, 2003, 11:01 AM

By someone_else:
File corruption occurs when a file was not properly saved (because you crashed, or the program just went wonky).

It has to be the file system that coruppted those PSD's, because they weren't opened, hell even Photoshop wasn't runnig at the time.

someone_else · Feb 12, 2003, 05:40 PM

Originally posted by Adam Betts:
Is there any way to recover the file data? My bro was using a FCP and it crashed. All of his movie editing files was missing but the hard drive size show that it's still around but not visible.

Do you recommend any disk utilites to recover the data? Any help is appreciated.

Prosoft's Data Recovery MAY be able to work. As long as the files were never actually deleted. I'd give it a try. There is a demo that will let you see recoverable files, but not actually recover them.

HTH.

someone_else · Feb 12, 2003, 06:46 PM

Originally posted by Vanquish:
It has to be the file system that coruppted those PSD's, because they weren't opened, hell even Photoshop wasn't runnig at the time.

Yes, that is possible. If the file is fragmented, then it is represented by multiple file allocation pointers (known as inodes in Unix parlance). If the FS was corrupted and some of the file's pointers were lost, then the file itself would be corrupted. But, the data is still intact (just lost) so technically it's not the file that is corrupted but the file system. Semantics, I know, but semantics are important when dealing with computers.