Linux Help
guides forums blogs
Home Desktops Distributions ISO Images Logos Newbies Reviews Software Support & Resources Linuxhelp Wiki

Welcome Guest ( Log In | Register )



Advanced DNS Management
New ZoneEdit. New Managment.

FREE DNS Is Back

Sign Up Now
 
Reply to this topicStart new topic
> Ls: Input/output Error, problems with ext2 partitioned SCSI disk
sistemas@ylos.co...
post Nov 11 2005, 05:26 AM
Post #1


Whats this Lie-nix Thing?
*

Group: Members
Posts: 1
Joined: 11-November 05
Member No.: 5,729



Hi,

In the last days I've found a strange problem with
one of the servers in the company where I work. Generally
when "ls -l" is made, it returns the list of the files in the
directory, but in some old (they are there since 2003) 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
Go to the top of the page
 
+Quote Post
DS2K3
post Nov 11 2005, 09:43 AM
Post #2


Its GNU/Linuxhelp.net
*******

Group: Support Specialist
Posts: 1,284
Joined: 14-November 04
From: Southampton, Hampshire
Member No.: 4,165



It does look like disk corruption. In such cases, I am of the opinnion that it is best to salvage what you can to another volume, restore the rest from a backup, and then reformat the faulty disk. You could try running a plain "fsck" on the drive, but ity might not come up with anything that e2fsck didnt.

D


--------------------
Fixed your problem? Let us know!
richard@linuxhelp.net

www.Gathr.co.uk Online Event Management
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 16th October 2017 - 05:17 PM