No, not filevault. However when I first set up the client on version 0.6.3 I moved the contents of the Bitcoin directory into an encrypted disc image and hard linked the contents back into the original location. This meant that every time I needed to run Bitcoin-Qt I had to open the disc image first.

Of course now that I have encountered this error and looked into the file structure again I realise that it has changed. Doh. Oh well, this has still worked faultlessly until now.

Since posting about the error I have restored all the files to the Bitcoin directory from a backup and also restored the 0.8.4 application. I ran it with the checklevel=2 commandline option. It is now stuck at the "Verifying blocks..." stage and has been for more than 30 hours. It seems to be creating and removing files ending in .sst in the "chainstate" directory (for example 068675.sst) continuously. This seems like a very long time, and a little concerning tbh. I'm starting to wonder if it might be better to simply delete the Bitcoin directory, re-download the blockchain, then copy the wallet.dat file back when it's finished 

I have just encountered this error since I downloaded Bitcoin-Qt version 0.8.5 for OSX running on Mountain Lion, having replaced version 0.8.4 which I downloaded just a few days ago, and am seeing this when I attempt to run it: "Error opening block database. Do you want to rebuild the block database now?". I did not see this error when I ran 0.8.4.

Should I click "Ok" and allow the rebuild of the block database to proceed? Or would it be wise to stick to 0.8.4 for the time being?

Never mind, I see this is a duplicate of the thread here: https://bitcointalk.org/index.php?topic=155140.0 so I'll repost this there

I have just downloaded Bitcoin-Qt version 0.8.5 for OSX running on Mountain Lion, having replaced version 0.8.4 which I downloaded just a few days ago, and am seeing the following error when I attempt to run it: "Error opening block database. Do you want to rebuild the block database now?". I did not see this error when I ran 0.8.4.

Should I click "Ok" and allow the rebuild of the block database to proceed? Or would it be wise to stick to 0.8.4 for the time being?

Boom!  $144.9999

edit:  I wonder if these buy-ups lately are someone, or some group, stacking coins in preparation for an upcoming business venture? Perhaps a new financial service of some kind?

This reminded me of this guy's post 

Not sure this is the right thread for this but here goes anyway....

I saw this article on Zerohedge (http://www.zerohedge.com/news/2013-09-05/bullrun-nsas-infatuation-back-door-penetration). The phrase that stood out for me was "What happened next is unclear, but it is safe to say the NSA can now hack virtually everything but the highest (512+ bit: assume AES-256 is now terminally violated) cipher with impunity."

I sense a degree of fear-mongering to the article but was wondering how accurate it is and if it has any bearing on the security of the Bitcoin network?

iFLfFG4rfreEHprT2FksnTPP6pqCYNfAS2

Thanks! 

Or they simply store the coins outside the exchanges until the storm settles

+1  exactly what I was thinking. The timing after the conference today is very interesting

I agree, it will be interesting to see where this goes. I think the information that TORMail was included in the compromise will be giving a few people some anxious moments

Should we tender our shares to AMCTENDER1 on btct.co now and send the email if we are transferring them to the new btct.co stock? Or should we wait until the new stock is approved? The reason I ask is because I'll have very patchy internet access for the next few weeks and I don't want to miss the deadline

 

I'm all for this. I'll be overseas until the 30th so will only have intermittent internet access. Just bad timing for me

It's odd that if you narrow the range to that day only that there is no large volume spike at that time but about 1/2 an hour later. Glitch?

That's a grab from bitcoin.clarkmoody.com

It's clear the wall served its purpose