Well, it's been up for well over a day now so it appears moving the folder solved the issue.

Thanks everyone. 

Well, so far it's been working ok, but it doesn't mean it's fixed.  The amount of time it takes did vary some before, though right now it's lasted more than 12 hours and is still going strong.

Guess I'll let it run still, see how it goes.

Thanks for the help so far, everyone. 

Oh, and just another odd tidbit of info.  I compared when Bitnodes said it "stalled" to the log entries above.  According to the log it stopped at midnight, but according to Bitnodes it was still working and responding to queries up to 3am.  5 hours later it shows when it came back after I restarted it just after 8am.

Seems it worked from memory for those three hours after the logged error.

I moved it from /storage/Backups/bitcoin to /storage/bitcoin.  I also changed the owner/group to my own, still with the rwxrwxrwx permissions.  I really need the folder to stay in that raid array, since I don't have that much room in the root filesystem.  But where it is now is not shared, so guess we'll see what happens overnight.

The only cron job I can think of is the indexing done for all files, not just the shared folders.  Thing is it was the same thing happening on Windows, on a drive and folder that wasn't shared.  That would only happen with the 64-bit one, it would quit after a while, usually with the same error as in the title, sometimes with other weird errors.  32-bit would work fine.

I can move the folder to somewhere that is not part of the SMB share just to test it though.

Yes, I do.  ;-)

Permissions on the folder has a special group, since some of these folders are shared through SMB, of group smbusers and user smbguest (smbguest is the owner).  My account is a member of smbusers.  The permissions are rwxrwxrwx for all files in the folder, and the sticky bit is set for the group so it inherits automatically for any file or folder made inside it.

Like I said earlier, what doesn't make sense is I can click that error message from bitcoin-qt, which then closes the window, then immediately double-click the desktop icon to start it back up and it works fine again, for at least 8-12 hours.

It's done the same thing every day since I set up the 64-bit version.

I can't get the 32-bit one to even start up (doesn't even get to start checking the Blockchain), since there are some 32-bit libraries missing from the Centos install (I set it up as pure 64-bit to start with).  When I tried running it the first complaint was it couldn't find libfontconfig.so (might have been .so.0 on the end, not sure now).  So I installed the 32-bit package for that, which cleared that error.  But then it says it cannot find a file, but doesn't say what file, so I can't go any farther with it.  That's why I went with the 64-bit version when I set it up under Centos this time.  I would give the 32-bit one a try to see if it is stable like it's been everywhere else, but there is nothing in the docs that says what the software dependencies are.

When I had it running on my Windows 7 computer, I had the 64-bit installed first (since it was 64-bit Windows).  Since it was REALLY unstable (wouldn't go more than 12 hours without crashing, sometimes corrupting the database and redownloading the blockchain) I then loaded the 32-bit and made sure it loaded the old data files (which were working in the 64-bit version when I shut it down).  That worked solid, no problems for at least a month.

I kinda doubt there might be an issue with the files between 32 and 64 bit, at least for Windows anyway.  Maybe for Linux though.

When I set up the Fedora VM, I made it 32-bit from the start since I didn't want to mess with the stability issues like I saw with the Windows 64-bit version.  That install had been there for months, starting with the data files that the Windows box had (copied them over and replaced the contents of the Data folder in the linux install).

Hmm, this is odd.  Here's the three lines in debug.log from around when it happened:
2015-12-21 06:00:05 LevelDB read failure: IO error: /storage/Backups/bitcoin/data/chainstate/3047481.ldb: Permission denied
2015-12-21 06:00:05 IO error: /storage/Backups/bitcoin/data/chainstate/3047481.ldb: Permission denied
2015-12-21 14:06:29 Error reading from database: Database I/O error

Interesting that it doesn't record the error that is prompted until I clicked it this morning (just after 8am CST US time, which matches up to the last time stamp since that is UTC shown).

The line just before the LevelDB entry is from normal operation (lots of entries about the rate limiter kicking in on a free transaction).  Not sure why it thinks there is a permission denied issue, since immediately restarting the client works fine.

For reference, the /storage folder is a mount point for a software RAID5 array of four 2 TB drives, formatted EXT4. I've got others things (like a Windows VM running in Virtualbox) that have data files stored on that same volume, which were all working fine at the same time this happened.

I checked the kernel's messages log at midnight, matching up to that time stamp, and there's nothing odd listed.

Forgot to mention, this is the tgz download of the compiled core.  I can try compiling from source if needed.

Lately I changed where my Bitcoin Core install was located, moving the data out from a Fedora VM to the host system and setting up Bitcoin Core 0.11.2 64-bit.  The host system is running 64-bit Centos 6 (whatever latest is, kept up to date against repos) on a Core2Quad 2.4 GHz CPU with 8GB RAM in an old Optiplex 755 (server is stable, up 24/7 and rarely gets rebooted).  In the 32-bit Fedora VM on the same computer I ran the 32-bit version, and it ran for months without issues.  Since moving the data out to the host and loading the client, I can't get it to stay up for more than 24 hours.

I've got the node linked to Bitnodes so I know when it goes up or down, and it's been very consistent.  Data shows steady response times for anywhere from 12-16 hours, then it will either say it stalled or is down.  When I check the client, it shows the error "Error reading from database, shutting down".  When I ok that, it closes the client immediately.

Odd bit is I can immediately reopen the client and it loads and works (after syncing that is).  Granted, I never seem to catch it when it happens, so can't say if there is anything else that happens just before the error.  This Centos box is my home network server, so it's not monitored unless something isn't working.

Is there a problem in the 64-bit version?  Since I had a similar issue on Windows when trying this (64-bit was seriously not stable with the same error and worked fine after restarting it, 32-bit worked fine for weeks) I tried running the 32-bit version, but can't figure out what 32-bit packages I need to install to get it working.  The Bitcoin Core documentation is seriously lacking in what software requirements there are for Linux machines and the messages I get do not point to specific modules or libs.

So, any ideas on how to fix this?

In the sense that Bitcoins as supposed to be usable "like cash", I can see where someone might want to be anonymous.

Would it make sense to require someone to produce an ID at a local convenience store when paying with FIAT cash? I for one would not go back to a store that required me to do that when paying with cash to buy a soda or some snacks. 

Bitcoins should be usable the same way for most things.  However, some Bitcoin-FIAT transactions may need ID due to the law, so one cannot expect to be able to do that with anyone who has a high visibility (such as an exchange site).

FTFY.  :-)

And I agree, there are many stupid laws like that out there, that all they do is further restrict our freedoms.

Sounds like a nice idea and would be fairly fast, wouldn't need to carry around the cash.

However, I get a feeling that this would not be an option for someone that wants to try and stay anonymous, so that no one besides the buyer and seller know what is going on with the transaction....

Yes, it is very important to say where you are, because no two countries/states have the same tax laws 100%.  There's always something different between them. 

For example, in the USA on the federal tax return you would have to report the mined bitcoin as of the day you received it as income.  So if it was $450 when you received it, you report $450 income and pay regular income tax on that amount.  Then if you sell it at $490, since you already paid taxes on the $450 you don't pay taxes on that part but pay cap gains taxes on the profit of $40.

I think you misunderstood the concept. 

The idea is:
Employee gets paid in FIAT
Employee goes to ATM machine and trades FIAT for bitcoins
Employee sends bitcoins to family member through Bitcoin network like any other bitcoin payment
Family member takes bitcoins and trades for local FIAT

That's the whole process as I would understand it, especially since sending FIAT directly means things like Wire Transfers, international money orders, etc, which get pretty costly at times compared to Bitcoin transfers. 

Wow, need a math lesson much?   

The correct answer is 99900% profit

Cost = 145
Sold for = 145000
Profit = Sold for - Cost = 144855
Profit % = Profit / Cost * 100 = 99900%

You are right, it's not fair. They have protections built in to the law such that even if the allegations are false, I cannot even try to sue them for it. 

Worse yet, it's not a criminal case, but civil.  So the good old "beyond a reasonable doubt" doesn't apply.  All that matters is who has the preponderance of evidence. 

And most in the USA are not aware of how bad it is, because this is done in "Family Court" and each case is handled such that only parties involved in the case can be in the courtroom (not necessarily any real public oversight).  Everyone I've ever explained this to is shocked by the reality, because they have not had to go through it.  Only those that go through it know, but they also are typically like me (poor or unable to fight back in the right way due to lack of money).  They rarely drag anyone into this situation that can actually afford to fight it.

Anyway, don't want to drag this off topic, but I think I'd consider myself to be a Bitocoin "loser" right now due to my situation.  Though I am working on changing that. 

And be glad you aren't in my situation. I'm making US$20 an hour at my day job, but I'm behind on ALL my bills such that late fees on bills and overdraft charges at the bank mean I waste $200 a month just trying not to "drown" financially.  Life savings = 0, and has been for at least 7 years now.

All this after several things that I had no control over happened to me and my family.  First was the Kansas state "social services" agency getting it stuck in their head the wife and I were neglecting our kids.  We weren't but they later made it true because we kept having to spend money we could not afford to spare on lawyers and other issues related to them dragging us into court several times for a few years just before 2007.  Then the child support they forced us to pay (both of us, and my wife has not had a job in years and can't get one) pretty much ruined any chance of keeping the home we had bought trying to fix the issues they kept throwing at us.  Then what life savings I had (about $25000) we had to cash out in order to pay the back child support just to keep us out of jail.  Then in 2008, a board of directors change pushed out the President of the company I worked at, and the new guy did a 20% employee cut.  Of course I was one of those.

Ever since then I have not been able to get steady year-round employment in this city, because there just wasn't that many openings during the recession.  Then the seasonal jobs I was getting dried up in 2012 and I was unemployed for a year living off some money a relative had until I could get a job.  When I did get this job, it was just after that money ran out and I got behind on a couple bills.  Due to their policies on utility disconnection, the only option I had was to sacrifice payment of all other bills so we could keep the gas and electric on.  Because of that I have not paid a bill or rent on time since 12 months ago.  Every week when I get my paycheck, I have to go to the ATM machine to get all of it out as cash, overdrafting the account in the process to limit it to just one overdraft fee per week, just to pay what bills we can and try to put food on the table for another week.

I would LOVE to start buying and selling Bitcoins, but the money just isn't there to do it with.  Really kicking myself for not getting in to it back in 2010 when I first heard of it. 

I did start getting in to it in early 2013 and had been mining with my video cards, but that wasn't much for about 1.5 months worth of computer time and electricity.  At most I had about 1.2 BTC from mining, but had to cash it out due to a lack of cash again.  No more mining after that as the difficulty started going up a lot faster then due to ASICs for mining.  Now I have about 0.03 BTC left, sitting at CampBX, waiting for me to get some time to write my trading bot (since no one seems to really support CampBX anyway).

Anyway, there are likely a lot of people here who are very interested in Bitcoin and what it means for personal freedom and society in general who can't do much but read about it and hope they can get started on improving their personal situation.

Though I do have a possibility to start participating soon, I hope.  I'm getting closer to being able to get out from under these late fees, and the current job is still going, even through it's contract.  I've got a good chance that it will become full-time year-round and non-contract.  Once that happens I'll be getting higher pay than now, so I know I'll be able to start doing more with Bitcoin. 

While Josh is still an a-hole, he is right that it won't fly in court.  But he is wrong about the reason.

You have to claim ACTUAL damages, not what you might have earned.  Every court in the nation will either throw out the suit due to lack of a claim, or will require the claim to be changed to reflect actual damages before it can continue.

Which works fine, so long as you also aren't a US citizen.

Unfortunately, US citizens pay taxes whether they are in the US or not, according to the "law". 

Hmm, strange to see a simple and no-nonsense bill in the US Congress.