|
|
File system journaling won't prevent all disk damage
> I'm sorry, but as an enterprise unix user for over 10 years I can't accept this.
File system journaling won't prevent all disk damage
If I was getting 5 or six errors on a backup, I would be tearing my system apart looking for bad hardware.
File system journaling won't prevent all disk damage
> If I was getting 5 or six errors on a backup, I would be tearing my system apart looking for bad hardware.
File system journaling won't prevent all disk damage
Don't get me wrong, I'm not doubting that you have file system corruption, I'm just peeved at what I see is an attitude among many Mac users at just accepting that such things are a fact of life and working around it. This may not apply to you, but certainly does to many others. Maybe it's what they've been used to in Classic MacOS, but in this day and age it's not good enough.
File system journaling won't prevent all disk damage
* The files named "ClipWorks 2.0.1.sit alias" differ at offset 2559 (09FF hex) in the RESOURCE fork. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.17 seconds |
|