top | item 8910629

(no title)

rab_oof | 11 years ago

Update: I forgot the worst. FileVault 2 + HFS+ corrupting metadata and becoming un-fsck-able (Repair). TimeMachine restore and 5 hours loss per incident.

Also Xcode 6.1 took a week to fix a docset feed bug that they duplicated a docset dmg url. I found the exact correct dmg url, and it still took 3 days to fix. Everyone had broken Xcode Tools docsets until they fixed it. (!)

iBooks can use 100% CPU trying to connect to the (nonexistent) internet when reading an ePub.

All-in-all, these aren't show stoppers, just a collection of things to whine about. It would cause more happiness if they were fixed, but they're mostly navigable.

discuss

order

Flow|11 years ago

Regarding your app corruption, docset bug, filesystem corruption and general filesystem slowness, are you sure you don't have a bad SSD/HD or bad RAM?

rab_oof|11 years ago

Definitely not, it's 2 years old and memtest86+, prime95, iozone and iperf for 24 hours each. These are all independent soft errors. Furthermore, I'm continually running stuff that is doing gpg signing/verification and sha256 checksums in VMs... They would fail. Also, there would be kernel panics... I've had zero.

- App Store likely has a problem with storeaccountd / installer framework from the exception traces I've seen (debug menu on).

- HFS+ can corrupt itself irreparably (it's not ZFS). BTDTBTTS.