Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back > Forums > Linux Forums > Linux - Server
User Name
Linux - Server This forum is for the discussion of Linux Software used in a server related context.


  Search this Thread
Old 11-25-2010, 01:10 PM   #1
LQ Newbie
Registered: Mar 2002
Location: Grenoble (France)
Distribution: RedHat
Posts: 4

Rep: Reputation: 0
Unhappy root inode is not a directory

I'm trying to solve a corrupted file system problem on a cluster front end.

The filesytem is (or was ) 500Gb ext3.
We had a small electrical power failure yesterday, the server do not stop but the disk array (SCSI Raid 5 disk system) restarted. This morning, the filesystem was not available (I/O error) so I reboot the front end. The fsck failed with the message:
root inode is not a directory

There are nearly 400Gb of data on this filesystem. Any idea to solve the problem ? Google always point to a commercial software or windows software...


Old 11-25-2010, 01:48 PM   #2
Senior Member
Registered: Mar 2004
Location: Cary, NC, USA
Distribution: Fedora, Kubuntu, RedHat, CentOS, SuSe
Posts: 1,288

Rep: Reputation: 99
If it is a SCSI Raid 5 disk system, you probably want to look there for your answer. You may have to wait until it can rebuild itself. Then again, it may be too corrupted, but that's probably where you'll want to look to find out. That's the downside of raid 5. You get your redundancy and higher capacity than raid 1, but if you have a disk problem, you have to rebuild a drive w/ parity calculations rather than simply copying the drive. Hopefully, the error you are getting is the disk array attempting to prevent you from writing to it until it can finish all of it's calculations and get your array back online.


Old 11-26-2010, 05:49 AM   #3
LQ Newbie
Registered: Mar 2002
Location: Grenoble (France)
Distribution: RedHat
Posts: 4

Original Poster
Rep: Reputation: 0
I don't think it is related to the Raid because I haven't any failure on the disks. It look like if the ext3 filesystems was corrupted. Runing fsck says:

Missing '..' in directory inode 48922819.
Fix<y>? yes

Entry '..' in ... (48922819) points to inode (2) located in a bad block.
Clear<y>? yes

for many directories and then:

Pass 3: Checking directory connectivity
Root inode is not a directory; aborting.
e2fsck: aborted


corrupted, ext3, inode, root

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
Kupfer- no application for XXX (inode/directory) Oliviakrk Linux - Desktop 0 07-06-2010 05:40 PM
Need help using e2fsck (corrupt root inode) bamsesbilledbog Linux - Software 1 07-03-2006 02:26 AM
konquerror error: you have linked konq to inode/directory ... Tarzan-81 Linux - Software 5 01-13-2006 06:04 AM
how to modify a directory inode xlh3110 Linux - General 2 12-03-2005 12:34 PM
Directory access denied to root user: inode hack? netmar Linux - Security 2 07-31-2004 05:53 AM > Forums > Linux Forums > Linux - Server

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

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