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

Aw, crap! | 50 comments | Create New Account
Click here to return to the 'Aw, crap!' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Aw, crap!
Authored by: derrickbass on Oct 11, '04 08:25:50PM

I have no experience with Windows (thank goodness), but Mac OS is definitely more prone to disk damage (the software kind) than other UNIX-like OS's I've used.

For example, even though all of my drives are journaled, I occasionally scan them with DW or DU and sometimes find problems (always minor, so far). That should NEVER happen on a journaled disk and the fact that it does indicates a problem with the OS.

Another example: if you run LimeWire on a nearly full disk or from an encrypted sparse image (e.g. Apple's FileVault), you may end up with overlapping files (which, by the way, DW takes FOREVER (i.e. days) to repair). Since programs not running as root can only access the disk structures via the OS, it cannot be the fault of those programs; there must be a bug in Mac OS X somewhere (presumably a race condition allowing overlapping allocations when two threads request disk blocks nearly simultaneously).

[ Reply to This | # ]