2

I saw this in dmesg. What does it mean?

EXT4-fs error (device sdb1): htree_dirblock_to_tree: bad entry in directory #763 3575: rec_len is smaller than minimal - block=30429885offset=0(671744), inode=0,
rec_len=0, name_len=0

How in the earth this happen? Is this because SDB is bad?

This is what /var/messages say

Sep 26 17:15:40 host pure-ftpd: ([email protected]) [INFO] New connection from 175.44.11.232 Sep 26 17:15:40 host pure-ftpd: ([email protected]) [INFO] Logout. Sep 26 17:15:41 host pure-ftpd: ([email protected]) [WARNING] Authentication failed for user [solarromancecom] Sep 26 17:15:41 host pure-ftpd: ([email protected]) [INFO] Logout. Sep 26 17:15:41 host pure-ftpd: ([email protected]) [INFO] New connection from 27.150.198.182 Sep 26 17:15:41 host pure-ftpd: ([email protected]) [INFO] New connection from 216.244.84.165 Sep 26 17:15:43 host pure-ftpd: ([email protected]) [WARNING] Authentication failed for user [admSep 27 04:17:49 host kernel: imklog 5.8.10, log source = /proc/kmsg started. Sep 27 04:17:49 host rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="1708" x-info="http://www.rsyslog.com"] start Sep 27 04:17:49 host kernel: Initializing cgroup subsys cpuset Sep 27 04:17:49 host kernel: Initializing cgroup subsys cpu Sep 27 04:17:49 host kernel: Linux version 2.6.32-358.18.1.el6.i686 ([email protected]) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) ) #1 SMP Wed Aug 28 14:27:42 UTC 2013 Sep 27 04:17:49 host kernel: KERNEL supported cpus: Sep 27 04:17:49 host kernel: Intel GenuineIntel Sep 27 04:17:49 host kernel: AMD AuthenticAMD Sep 27 04:17:49 host kernel: NSC Geode by NSC Sep 27 04:17:49 host kernel: Cyrix CyrixInstead Sep 27 04:17:49 host kernel: Centaur CentaurHauls Sep 27 04:17:49 host kernel: Transmeta GenuineTMx86 Sep 27 04:17:49 host kernel: Transmeta TransmetaCPU Sep 27 04:17:49 host kernel: UMC UMC UMC UMC Sep 27 04:17:49 host kernel: BIOS-provided physical RAM map: 

That's it. So the system reboot and before it reboot it doesn't tell why or anythign.

1 Answer 1

8

According to this knowledgebase article on novell.com, titled: EXT3 file-system error "bad entry in directory", the resolution for this message:

EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #5556142: rec_len is smaller than minimal - offset=0, inode=2553887680, rec_len=0, name_len=0

Is as follows:

NOTE: This error is caused by a file that has been marked as a directory. This is a non-fatal error and can be fixed by removing the file in question.

  1. Mount the file-system in question
  2. Locate the file that has been corrupted. The file's inode is the number after "bad entry in directory" Using the example error code the file would be found by typing:

     $ find /MOUNT_POINT -inum 5556142 
  3. Delete the file identified in step two

  4. Umount the file-system
  5. Check the disk, and check for errors.

    $ fsck /dev/PHYSICAL_DEVICE 
  6. Repeat step 5. If no errors, the file-system is clean.

The resolution is the same, it doesn't matter if it's EXT4 or an EXT3 formatted drive.

16
  • Dude, the server is down and require manual check. If not hardware error, what could possibly have happened? Commented Sep 27, 2013 at 10:59
  • @slm, There is a space missing to the find command. /MOUNT_POINT and -inum Commented Sep 27, 2013 at 11:04
  • root@host [~]# find /MOUNT_POINT-inum 763 find: /MOUNT_POINT-inum': No such file or directory find: 763': No such file or directory Device is already mounted Commented Sep 27, 2013 at 11:05
  • @JimThio - who knows why these things happen. They just do. Yes the partition may be failing, or an error may have occurred when the data was being written to the device, so it was left in a partial state. Commented Sep 27, 2013 at 11:05
  • root@host [~]# root@host [~]# find /home2 MOUNT_POINT-inum 763 -bash: root@host: command not found Commented Sep 27, 2013 at 11:06

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.