Hi,

I got error on RHEL server as per below:

Error on Server :-

EXT4-fs error (device dm-0): ext4_lookup: deleted inode referenced: 3535250
EXT4-fs error (device dm-0): ext4_lookup: deleted inode referenced: 3535746
EXT4-fs error (device dm-0): ext4_lookup: deleted inode referenced: 3536866
EXT4-fs error (device dm-0): ext4_lookup: deleted inode referenced: 3537880
EXT4-fs error (device dm-0): ext4_lookup: deleted inode referenced: 3535318
EXT4-fs error (device dm-0): ext4_lookup: deleted inode referenced: 3536489
EXT4-fs error (device dm-0): ext4_lookup: deleted inode referenced: 3535250
EXT4-fs error (device dm-0): ext4_lookup: deleted inode referenced: 3535746
EXT4-fs error (device dm-0): ext4_lookup: deleted inode referenced: 3536866
EXT4-fs error (device dm-0): ext4_lookup: deleted inode referenced: 3537880
EXT4-fs error (device dm-0): ext4_lookup: deleted inode referenced: 3535318
EXT4-fs error (device dm-0): ext4_lookup: deleted inode referenced: 3536489


please help if anyone knowing about this.

Thanks in advance

AGAIN, as with several of your other threads, you need to PROVIDE DETAILS. You don't tell us what version of RHEL you're using, what you were doing/trying to do when this occurred, what you typed in, etc. We STILL can't guess as to what you're doing.

And, as you've been told several times in the past, if you're using RHEL, you NEED TO PAY FOR IT, and contact RHEL support for help. You ignore this every time you're told.

Dear TB0ne - Yes we've connected with Redhat support team for same the issue and get “It looks like this FS is corrupted.”
Can you please fsck the relevant filesystem?
but its not happen to rectified the problem. if any one know about this error please share the solution.

we've run the fsck as suggested by RHEL, but not get rectification issue.

...and...
Then you need to call them back and tell them it didn't work.

And AGAIN, you STILL don't provide DETAILS. As asked before:

• Version of RHEL
• What you were doing/trying to do when this occurred
• What you typed in before this occurred
• What you typed in for the fsck command, and what those results/messages were

AGAIN: the file system is corrupted. Running an fsck on it will fix it, but since you still don't say what command you ran, what state the system was in, and what version of RHEL you're using, we can't really tell you much. However, since you say you're PAYING FOR RHEL SUPPORT, you should use it. If what they told you didn't work, it's simple; call them back and tell them it didn't, and ask what ELSE they would try.

You might find some useful things to do, mentioned in http://www.gossamer-threads.com/list...kernel/1135120 to be useful.

Did you try Google?
It dates back to 2009 though.

Hi..

I'm using RHEL 6.1 64 bit os version.
we've run fsck command from single user mode with ummount /data partition and then run command.

---------- Post added 10-09-14 at 10:27 AM ----------

fsck -n /dev/sda1

and?

You need to include the "-f" option or else fsck may just report that the filesystem seems to have been cleanly unmounted.

AGAIN, since you've missed it or ignored it MANY TIMES NOW, you need to PAY FOR RHEL, and (since you say you ARE paying for RHEL), USE the support you're paying for. You say you called them...great...so why didn't you call them BACK if you didn't get the problem resolved? Why didn't you read the man page on the fsck command, to see what the "-n" option does?

Also, we will AGAIN say you need to provide DETAILS: saying the "/data" partition tells us exactly NOTHING, since you don't say if that is indeed, the partition that has an error, what disk it's on, or anything about your partition layout, or what device the rest of your system runs on. We have to keep asking you for details with EVERY THREAD you open...it gets VERY frustrating, especially when you flat out ignore advice given, and don't seem to apply anything you've been told.