Also have Mavericks and Lion and Mountain Lion.
Testing right now to see where my wallet.dat file is stored locally. Do the folks that have seen this issue use the Filevault service? Are you encrypting the entire drive or a portion of the drive?
Likely also HFS+ Compression could increase some issues with wallet.dat corruption.
If anyone has had this issue please do the following:
Can you guys with the issue please run this on a terminal and paste the output here?
diskutil list
Please describe which disk and partition that the db / bitcoin-qt supporting files is on as well - trying to track down a bigger picture issue.
(Posted to github as well)
Additionally most folks have had this corruption issue with OSX using an SSD disk - and when their system goes to sleep or hibernate. (Again thinking along the lines of resource forks, having a file open but also writing ram to disk etc.) Please check this guide out: http://sysadmin.flakshack.com/post/9253439680/ssd-tweaks-for-mac-os-x
Attempting to disable these has saved me from getting the corruption on my SSD with OSX
Topic: How long to post a response about the bitcoin bug in OSX? (Read 614 times)
Simple fix - due to the forking file system on OSX (resource forks meta data etc) it is possible to write to a file while open and alter it in ways that can have unexpected consequences.
A work around would be to add a fat32 or ntfs partition, or an encrypted file mounted as a fat32 or ntfs as these are supported natively by OSX and won't have the resource forking problems. Once mounted copy a wallet to test corruption on this file system - it should be just fine.
See some of the most basic early Apple docs regarding resource forking - and sites like http://www.peachpit.com/articles/article.aspx?p=1762250&seqNum=5
Very easy to setup using the disk utility as well and just add an additional non OSX partition, which will not be subject to the out of ordering resource forks.
1PNzs7ErcEPt8rM6rxJ8pVh4WBPGdoE3rL if anyone wants to donate.
A work around would be to add a fat32 or ntfs partition, or an encrypted file mounted as a fat32 or ntfs as these are supported natively by OSX and won't have the resource forking problems. Once mounted copy a wallet to test corruption on this file system - it should be just fine.
See some of the most basic early Apple docs regarding resource forking - and sites like http://www.peachpit.com/articles/article.aspx?p=1762250&seqNum=5
Very easy to setup using the disk utility as well and just add an additional non OSX partition, which will not be subject to the out of ordering resource forks.
1PNzs7ErcEPt8rM6rxJ8pVh4WBPGdoE3rL if anyone wants to donate.
Jump to: