Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

Inode search and detection (server kernel) hanging up machine

Discussion in 'Data Protection' started by bsasninja, Mar 23, 2012.

  1. bsasninja

    bsasninja Well-Known Member

    Sep 2, 2004
    Likes Received:
    Trophy Points:
    After having 3 crashes today and checking /var/log/messages I see that there is a problem in some directory of the /home partition.

    I runned smartd, badblocks and everything is ok. After my 2nd crash I updated cpanel to discard a corrupted cpanel system file on the machine. The update process was ok, after 20 minutes I watched the process repquota at 100% increasing the server load to the sky.

    Booted the server again, and.

    1) I removed some cpanel crons from the crontab list
    2) I renamed the repquota command at /usr/sbin/repquota to other thing, in case if its called again nothing happens.

    This gives me time to work and see a solution to this. At /var/log/message the same error before each crash is showed:

    server kernel: EXT3-fs error (device sda8): ext3_lookup: unlinked inode 68518001 in directory #68517945

    ok this error repeats 5 times with different inodes but in the SAME DIRECTORY #.

    So in my opinion its some user folder with unaccurate group or owner permissions. Is there a way with a command to see to which directory belongs that number????
    If that is the case I can check quickly the suspicious folder causing all this mess.

  2. cPanelMichael

    cPanelMichael Technical Support Community Manager
    Staff Member

    Apr 11, 2011
    Likes Received:
    Trophy Points:
    cPanel Access Level:
    Root Administrator
    Hello :)

    You can search for specific inodes using the "find" command. EX:

    find / -inum [inode-number]
    Thank you.
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. brianoz

    brianoz Well-Known Member

    Mar 13, 2004
    Likes Received:
    Trophy Points:
    Melbourne, Australia
    cPanel Access Level:
    Root Administrator
    Presumably you've fixed this long ago; but just for the sake of the record here that can't be due to ownership "problems", as described.

    It sounds more like a file system corruption issue, and the way to fix it would be to run an fsck as soon as possible (as such corruption tends to get worse). This sort of corruption can occur without bad blocks or smart errors. An unlinked file is always a serious problem. In fact, it can sometimes be caused by a crash, though why it wasn't resolved by the auto-fsck during the boot process is something I'm not sure about.
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice