Backup Central

Dear Dean and Troels,

Thanks a lot for your responses.

my fstab entry for the drive is
/dev/sdb1 /mnt/usbdrive ext3 noauto 0 0

But as you both said, I have some errors at the filesystem



I have an error in my system log as follows. Running e2fsck resulted
to the error below. Is it safe to ignore this error? What I can do to
recover?

Thanks a lot again! I will try also to google as well to see what I
can do about it.


Best regards,
Christos


</var/log/messages>
Jun 25 12:35:19 tux kernel: kjournald starting. Commit interval 5 seconds
Jun 25 12:35:19 tux kernel: EXT3-fs warning (device sdb1):
ext3_clear_journal_err: Filesystem error recorded from previous mount:
IO failure
Jun 25 12:35:19 tux kernel: EXT3-fs warning (device sdb1):
ext3_clear_journal_err: Marking fs in need of filesystem check.
Jun 25 12:35:19 tux kernel: EXT3-fs warning: mounting fs with errors,
running e2fsck is recommended
Jun 25 12:35:19 tux kernel: EXT3 FS on sdb1, internal journal
Jun 25 12:35:19 tux kernel: EXT3-fs: recovery complete.
Jun 25 12:35:19 tux kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jun 25 12:35:28 tux kernel: SCSI error : <2 0 0 0> return code = 0x8000002
Jun 25 12:35:28 tux kernel: sdb: Current: sense key: Medium Error
Jun 25 12:35:28 tux kernel: Additional sense: Unrecovered read error
Jun 25 12:35:28 tux kernel: end_request: I/O error, dev sdb, sector 224690255
Jun 25 12:35:28 tux kernel: EXT3-fs error (device sdb1): ext3_readdir:
directory #14041149 contains a hole at offset 0
Jun 25 12:35:28 tux kernel: Aborting journal on device sdb1.
Jun 25 12:35:28 tux kernel: ext3_abort called.
Jun 25 12:35:28 tux kernel: EXT3-fs error (device sdb1):
ext3_journal_start_sb: Detected aborted journal
Jun 25 12:35:28 tux kernel: Remounting filesystem read-only
Jun 25 12:35:35 tux kernel: SCSI error : <2 0 0 0> return code = 0x8000002
Jun 25 12:35:35 tux kernel: sdb: Current: sense key: Medium Error
Jun 25 12:35:35 tux kernel: Additional sense: Unrecovered read error
Jun 25 12:35:35 tux kernel: end_request: I/O error, dev sdb, sector 224690255
Jun 25 12:35:35 tux kernel: EXT3-fs error (device sdb1):
ext3_find_entry: reading directory #14041149 offset 0
<//var/log/messages>


<e2fsck>
e2fsck 1.37 (21-Mar-2005)
/dev/sdb1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 26362044 (Attempt to read block from filesystem
resulted in short read) while reading indirect blocks of inode
13175716. Ignore error<y>?
</e2fsck>

Hi,

On Sat, 25 Jun 2005, Christos Tachtatzis wrote:

I have an error in my system log as follows. Running e2fsck resulted
to the error below. Is it safe to ignore this error? What I can do to
recover?
[snip]
Jun 25 12:35:28 tux kernel: end_request: I/O error, dev sdb, sector 224690255
Jun 25 12:35:28 tux kernel: EXT3-fs error (device sdb1): ext3_readdir:
directory #14041149 contains a hole at offset 0
[snip]
/dev/sdb1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 26362044 (Attempt to read block from filesystem
resulted in short read) while reading indirect blocks of inode
13175716. Ignore error<y>?

Well.. I guess you don't have a device of 26362044*512=115041410560 bytes
(=115GB), so reading that block is supposed to return error. So, inode
13175716 contains incorrect / corrupted information.

Running e2fsck without any special command line switches, the suggested
answers are usually fine. e2fsck tries to make the best of it. The -y
command line switch implies 'y' to all questions, and "allows e2fsck to be
used non-interactively". So, just accepting the default values should be
ok.

From the e2fsck manpage:
Almost any piece of software will have bugs. If you man-
age to find a filesystem which causes e2fsck to crash, or
which e2fsck is unable to repair, please report it to the
author.


HTH,
Maarten