Hi,
In the last days I've found a strange problem with
one of the servers the company where I work. Generally
When "ls -l" returns the list of the files in the
directory, but in some old directories, we obtain an
"Input/Output error" from some files contained in the
directory.
In the past I found the same error, and I solved
with a e2fsck to the problematic partition. But now,
I've made the same process, it has finished ok, but the
error persists.
Does anybody know any solution for my problem? I
think it isn't a physical problem (it's my point of
view, but it's possible that I'm wrong), it seems a
problem in the table of inodes, but I don't know how to
solve it.
Some details of the system:
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 1.2G 999M 122M 90% /
/dev/sda1 30M 21M 8.3M 71% /boot
none 503M 0 503M 0% /dev/shm
/dev/hda2 72G 54G 14G 79% /disk2
/dev/sda5 15G 5.2G 9.2G 36% /home <==
(problems here)
some messages from dmesg, I think that device ide0 is
hda2 and device sd is the problematic SCSI disk:
EXT2-fs error (device ide0(3,2)): ext2_free_blocks:
Freeing blocks not in datazone - block = 3520652577,
count = 1
EXT2-fs error (device ide0(3,2)): ext2_check_page: bad
entry in directory #1278475: unaligned directory entry
- offset=0, inode=0, rec_len=33291, name_len=19
EXT2-fs error (device ide0(3,2)): ext2_check_page: bad
entry in directory #1278475: unaligned directory entry
- offset=0, inode=0, rec_len=33291, name_len=19
EXT2-fs error (device ide0(3,2)): ext2_check_page: bad
entry in directory #1278475: unaligned directory entry
- offset=0, inode=0, rec_len=33291, name_len=19
EXT2-fs error (device ide0(3,2)): ext2_check_page: bad
entry in directory #1278475: unaligned directory entry
- offset=0, inode=0, rec_len=33291, name_len=19
EXT2-fs error (device ide0(3,2)): ext2_check_page: bad
entry in directory #1278475: unaligned directory entry
- offset=0, inode=0, rec_len=33291, name_len=19
EXT2-fs error (device ide0(3,2)): ext2_check_page: bad
entry in directory #1278475: unaligned directory entry
- offset=0, inode=0, rec_len=33291, name_len=19
EXT2-fs error (device ide0(3,2)): ext2_check_page: bad
entry in directory #1278475: unaligned directory entry
- offset=0, inode=0, rec_len=33291, name_len=19
EXT2-fs error (device ide0(3,2)): ext2_check_page: bad
entry in directory #1278475: unaligned directory entry
- offset=0, inode=0, rec_len=33291, name_len=19
EXT2-fs warning (device sd(8,5)): ext2_read_super:
mounting ext3 filesystem as ext2
EXT2-fs error (device ide0(3,2)): ext2_check_page: bad
entry in directory #1278475: unaligned directory entry
- offset=0, inode=0, rec_len=33291, name_len=19
EXT2-fs error (device ide0(3,2)): ext2_check_page: bad
entry in directory #1278475: unaligned directory entry
- offset=0, inode=0, rec_len=33291, name_len=19
TCP: Treason uncloaked! Peer 195.53.125.135:30021/80
shrinks window 2191618559:2191622759. Repaired.
EXT2-fs error (device ide0(3,2)): ext2_check_page: bad
entry in directory #1278475: unaligned directory entry
- offset=0, inode=0, rec_len=33291, name_len=19
EXT2-fs error (device ide0(3,2)): ext2_check_page: bad
entry in directory #1278475: unaligned directory entry
- offset=0, inode=0, rec_len=33291, name_len=19
José Miguel Millan Rosa
e-mail: sistemas@ylos.com
Systems Department
Ylos Hispania SL
Pş Prim, 27
43202 Reus (Tarragona)
SPAIN
Web: http://www.ylos.com
Tel: +34 902 181073
Fax: +34 977 331114
Logged In: YES
user_id=628
Originator: NO
This errors in your system log means that your filesystem is corrupted. You need to unmount the filesystem and run e2fsck to check and fix the inconsistencies in your filesystem. The I/O errors reported when you tried to open some of the files are due to those consistency problems.