By in Persona Paper

Crisis Adverted

I wanted to take a second to post about the issues that have been on the site recently. Let me summarize this post in just one sentence: All issues with the ads/images/database weirdness should be fixed.

So what was the actual issue?

We had an issue on our server where it was complaining about disk space. However, we were only using about 50% of the disk space so this required some investigation. After a few minutes, we discovered that we had actually ran out of inodes (which of course is on a different screen than the actual disk space). I'll spare the technical details but suffice it to say, we had a lot of very small files that were taking up inode entries. Remove files, inodes available, all is well again.

How did you not know?

We have a few key items that we are monitoring that I receive a direct email alarm if it happens. Things like the site going down, running out of disk space, database not responding, etc. Keeping track of inodes was not among that list. But it is something we know to look for in the future. The good part is that we learned something from this, and as long as we walk away with a little more knowledge then that helps everyone.

What was affected?

Anything that involved writing something to the disk was affected. The database was only partially affected. The biggest part that was affected was the view check and image uploading. So it is possible that views came in, and not properly checked or accounted for. Images could not be upload either. Even though we do not store images on our server directly, we have to put them there temporarily to send them elsewhere. Since that temporary write failed, the entire process fails.


Like I said before, so long as something was learned from the process then we can all gain from it. All should be back to normal now. And I'll be checking those inode reports more often now :)

Image Credit » Created and Owned by Persona Paper

You will need an account to comment - feel free to register or login.


VinceSummers wrote on May 8, 2015, 6:07 PM

Great. Glad I'm not running the show.

Soonerdad3 wrote on May 8, 2015, 6:11 PM

Thanks for update of the site issues.

xstitcher wrote on May 8, 2015, 6:38 PM

I have no idea what most of that meant, but I'm glad that you do. :)

MelissaE wrote on May 8, 2015, 6:56 PM

Thank you for the update.

bestwriter wrote on May 8, 2015, 7:08 PM

I did have both the image and views issues. The views are still zero on a post about which I had alerted 'contact'. I have yet to try uploading images.

CoralLevang wrote on May 8, 2015, 7:29 PM

Thank you for fixing the issues and for the update!!

wolfgirl569 wrote on May 8, 2015, 8:34 PM

You lost me after hard drive lol But glad you know what to look for

agvulpes wrote on May 8, 2015, 9:04 PM

Wow who would have thought that something so 'simple'? could cause such mayhem. lol
We can all now just settle down and go post some pictures :)

Bensen32 wrote on May 8, 2015, 11:02 PM

Thanks for the update now maybe I can add my photo to my past post. I'll give it a try and see how it goes, Thanks again.

CalmGemini wrote on May 8, 2015, 11:56 PM

Glad to know these issues have been solved.

allen0187 wrote on May 9, 2015, 12:16 AM

Glad that this was spotted early on. Good job as always!


MegL wrote on May 9, 2015, 3:54 AM

I never heard of inodes until a few months ago. I ran out of them on one of my blogs because of the amount of spam and had to find a way to clear thousands of spam messages. I was annoyed with my host at the time because they did not let me know until AFTER they suspended my blog. Letting me know a little earlier would have been more helpful. They did apologise and I hope that they have now implemented an early warning system for others. I now check the spam and delete it more regularly.

HappyLady wrote on May 9, 2015, 4:16 AM

What i like about this site is that you keep us in the loop. I have no idea what an inode is and so am off to google, but I am glad you were able to sort it. I am finding the advertising quite relevant at the moment and have not had any issues.

WordChazer wrote on May 9, 2015, 4:17 AM

Thanks. I'll go back and try those two images I wanted to upload with the last two posts now. The first one may still not work, but the second one ought to as it's a Pixabay image I wanted to use.

msiduri wrote on May 9, 2015, 8:12 AM

Thanks for the update and for addressing the issue in such a timely manner.

Hollyhocks100 wrote on May 11, 2015, 6:59 AM

It´s all double Dutch to me, but well done you for sorting it out emoticon :grin:

Glenn wrote on May 11, 2015, 3:13 PM

elitecodex - Does this also fix the problem with losing images from posts when edited via a mobile device, such as an iPad ? Will, I never heard back from you when I reported this a month ago.

Last Edited: May 11, 2015, 3:14 PM

seren3 wrote on May 17, 2015, 5:54 PM

Well I learned something today. I know even less than I thought emoticon :smile: !

BarbRad wrote on June 2, 2015, 4:47 AM

i would love to know all you learned about inodes , since that's what I'm having problems with while building my new Wordpress site. I have too many inodes , supposedly due to a script running I haven't a clue about. How do you build a site without adding files and images? Today I finally talked to one of the techs who might have a clue. He said it had to do with images trying to download from files that weren't available. That made sense. I knew they weren't able to get the images where they used to, and I was going to replace those images with images in the right files. I removed the place holders for those images that were probably generating the errors and I hope that improves the situation. The test site I'm working on is being cloned to replace what is currently in the main domain so I don't lose the traffic from the main domain.

BarbRad wrote on June 2, 2015, 4:49 AM

I'm on temporary restriction from the site I'm building because of this problem, and I've never had it on any other blog -- yet. holding my breath.

Ruby3881 wrote on June 4, 2015, 5:34 PM

Thanks so much for your vigilance, and for explaining the situation. I'm glad the issue was so easily resolved emoticon :smile: