LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 12-14-2005, 05:23 PM   #1
edkhosting
LQ Newbie
 
Registered: Sep 2003
Posts: 10

Rep: Reputation: 0
does anyone know where I can read up more about clearing inodes and such?


I have a server right now that is clearning inodes and has been since sunday, its a raid 10 array and it has said its cleared 6 million 19 thousand of them.
 
Old 12-14-2005, 05:51 PM   #2
liamoboyle
Member
 
Registered: Mar 2004
Location: Wellington, New Zealand
Distribution: Debian
Posts: 127

Rep: Reputation: 15
What filesystem are you using? Sounds like (maybe) hard disk damage. Look at "man e2fsck" or "info e2fsck" if you're using an ext2 or ext3 filesystem.
 
Old 12-14-2005, 10:05 PM   #3
mikaa
LQ Newbie
 
Registered: Dec 2005
Location: germany
Posts: 5

Rep: Reputation: 0
i think that ext3 doesn't use inodes
 
Old 12-14-2005, 11:16 PM   #4
chrism01
LQ Guru
 
Registered: Aug 2004
Location: Sydney
Distribution: Centos 6.9, Centos 7.3
Posts: 17,362

Rep: Reputation: 2377Reputation: 2377Reputation: 2377Reputation: 2377Reputation: 2377Reputation: 2377Reputation: 2377Reputation: 2377Reputation: 2377Reputation: 2377Reputation: 2377
An inode is the entry in a dir file for each file (inc itself).
This is std Unix/Linux/BSD.
 
Old 12-14-2005, 11:38 PM   #5
btmiller
Senior Member
 
Registered: May 2004
Location: In the DC 'burbs
Distribution: Arch, Scientific Linux, Debian, Ubuntu
Posts: 4,284

Rep: Reputation: 371Reputation: 371Reputation: 371Reputation: 371
Mikaa, ext3 does use inodes. It just adds journaling to protect the filesystem state in case of a sudden crash.

Edkhosting -- are you getting this message during a filesystem fsck on bootup (or initiated manually)? Any time I've seen something like that it has generally pointed to a badly corrupted filesystem. Was the system forcibly shutdown recently or have there been any hardware failures? If the filesystem is damaged badly enough, you may need to clean things out by hand via debugfs (do not use unless the situation is hopeless and you really know what you're doing -- debugfs allows you to directly edit inodes, amongst other things) and if that fails restore from back-ups.
 
Old 12-15-2005, 02:52 AM   #6
edkhosting
LQ Newbie
 
Registered: Sep 2003
Posts: 10

Original Poster
Rep: Reputation: 0
a filesystem fsck on bootup. Here is what I posted on another board

Quote:
I have a db server its a dual xeon with 2gb ram and a Adaptec 2230SLP with 4 Fujitsu 74GB running in a raid 10 setup and a Western Digital Raptor for a backup drive.


The main os is on the raid array(everything is). I didn't make it so \var\lib\mysql was on the raid array and mount it and have the os on another drive. Now this db server has 2 large databases on it totaling in over 3 million tables and 38gb of space. The server locked up the other night and it was rebooted and so I went to run a check on it when it came up and opened up a screen session and ran "mysqlcheck -rof --all-databases" which I have done many times before nothing unusual. The database was running correctly and the forum was working fine. It usually takes about 6-8 hours to do this and about 2 hours into it I noticed the server was somewhat down but before usually I wouldn't be able to ssh in but I was able to this time. I went and checked the screen session and every table it was checking was saying that it was read only and it was going through all the tables. Going onto the forums that the databases are used for it was throwing up an error saying the sessions table was read only and couldn't write to it. Well I tried to do a shutdown -r now and reboot the server but shutdown just hung I went into top and tried to kill it and couldn't so the server was hard rebooted. It came up and said that there were errors on the drive/raid array and to run a check. Well this has been since sunday on the 11th that it started clearing inodes after running fsck and it has currently cleared around 6 million 19 thousand inodes and counting.

Now after all this my question is do you think my databases are gone? I would hope not since the os was able to load and the server is running its just clearing inodes which means its fixing the file system. I cannot ssh in it is still running now clearing inodes. The thing is its clearing the inodes where the databases are located it seems the inodes for everything else is fine.

so my feeling is the data/databases are still there its just the permissions on them are wrong and it has to do with the inodes to which fsck is fixing now. I mean they were fine and then it said the tables were read only it didn't say they didn't exist that its just read only. I don't know how long this is going to take for the server to fix everthing but its been running since sunday clearing inodes so I take it thats a good thing. Also I was pondering the idea if I could just stop the check and tar up the msql folder even with the wrong permissons and just move them over to another db server that I ordered and is live and reset the permissions there on the new server to what they should be with that mysql database. Will that work?

background is I run a free forum host and there are two db's one for each web server. Each web server is hosting about 30,000 phpbb forums and each forum has about 25 tables so you can do the math on how many tables each db is holding.

Last edited by edkhosting; 12-15-2005 at 02:54 AM.
 
Old 12-17-2005, 12:12 AM   #7
edkhosting
LQ Newbie
 
Registered: Sep 2003
Posts: 10

Original Poster
Rep: Reputation: 0
can anyone else help me?
 
Old 12-17-2005, 02:32 AM   #8
btmiller
Senior Member
 
Registered: May 2004
Location: In the DC 'burbs
Distribution: Arch, Scientific Linux, Debian, Ubuntu
Posts: 4,284

Rep: Reputation: 371Reputation: 371Reputation: 371Reputation: 371
The inodes also hold the lists of the actual disk blocks used by the files, so if those lists have gotten corrupted, you're in trouble. Although if things were working OK for awhile, maybe you'll be lucky and the corruption will be with other files in the filesystem. My advice would be to let fsck run to completion and see what happens. Be prepared to look in the filesystem's lost+found directory for bits and pieces of files that fsck may recover from damaged files.

You need to figure out what caused the problem in the first place. Are your RAID controller and all of the disks working correctly? Have you had any disk or other subsystem failures?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Had a crash and need help and info, running a fsck and clearing millions of inodes edkhosting Linux - Software 3 12-13-2005 10:12 AM
Out of Inodes tmiles Linux - Newbie 4 02-06-2005 08:35 PM
Inodes used up wolferd1 Linux - General 2 02-04-2005 04:22 PM
What is inodes? ionian2k Linux - Newbie 1 12-15-2002 10:29 AM
Inodes milena1 Linux - General 0 02-05-2002 07:55 PM


All times are GMT -5. The time now is 02:58 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration