msa1000 disk fault log

[mark.M]

show dmesg ........

SCSI error : <0 0 0 1> return code = 0x10000
end_request: I/O error, dev sda, sector 1656756488
EXT3-fs error (device sda1): ext3_find_entry: reading directory #103547075 offset 0

SCSI error : <0 0 0 1> return code = 0x10000
end_request: I/O error, dev sda, sector 1656756488
EXT3-fs error (device sda1): ext3_readdir: directory #103547075 contains a hole at offset 0
SCSI error : <0 0 0 1> return code = 0x10000
end_request: I/O error, dev sda, sector 646976344
EXT3-fs error (device sda1): ext3_find_entry: reading directory #40435812 offset 0

SCSI error : <0 0 0 1> return code = 0x10000
end_request: I/O error, dev sda, sector 646976344
EXT3-fs error (device sda1): ext3_find_entry: reading directory #40435812 offset 0

SCSI error : <0 0 0 1> return code = 0x10000
end_request: I/O error, dev sda, sector 646976344
EXT3-fs error (device sda1): ext3_find_entry: reading directory #40435812 offset 0
SCSI error : <0 0 0 1> return code = 0x10000
end_request: I/O error, dev sda, sector 646976344
EXT3-fs error (device sda1): ext3_readdir: directory #40435812 contains a hole at offset 0
SCSI error : <0 0 0 1> return code = 0x10000
end_request: I/O error, dev sda, sector 14686456
SCSI error : <0 0 0 1> return code = 0x10000
end_request: I/O error, dev sda, sector 14190584
SCSI error : <0 0 0 1> return code = 0x10000
end_request: I/O error, dev sda, sector 14190584
SCSI error : <0 0 0 1> return code = 0x10000

what is mean?
arrary disk fault change worked of new disk
but directory read error.... why? why?

[Steven E. Protter · Accepted solution]

You have a bad disk.

This may be a disk array being mis-detected as a disk, but more likely is a bad disk or inaccessible LUN allocated to this machine via world wide name.

The disk needs to be replaced, or the LUN needs to be properly configured.

SEP

[Ivan Ferreira]

I think that could be an inode missing reference, pointing to an inaccesible disk block (EXT3-fs error - directory #40435812 contains a hole at offset 0).

Umount the filesystem and run fsck -f to check filesytem inconsistences.

[mark.M]

i will method of recovery Data?
please....

[Ivan Ferreira]

I didn't understood your last question.

If fsck do not fix the problem, the best way to recover data is from a backup. You MUST have always good backup plan.