e2fsck is recommended
Posted: 20. Feb 2007 13:29
Hallo
Ich arbeite auch mit SLES 10 und habe dort folgendes Problem (gehabt???)
Ein RAID 0 (4 Platten a 320GB)
Plötzlich war das Filesystem nur noch READ only gemountet.
in /var/log/messages stand .....
.
.
Feb 20 12:19:49 lds1 kernel: EXT3-fs error (device dm-0): ext3_free_blocks: Freeing blocks not in datazone - block = 365684307, count = 1
Feb 20 12:19:49 lds1 kernel: Aborting journal on device dm-0.
.
.
Feb 20 12:20:32 lds1 kernel: EXT3-fs error (device dm-0): ext3_free_blocks: Freeing blocks not in datazone - block = 1955375396, count = 1
Feb 20 12:20:33 lds1 kernel: EXT3-fs error (device dm-0) in ext3_reserve_inode_write: Journal has aborted
Feb 20 12:20:33 lds1 kernel: EXT3-fs error (device dm-0) in ext3_truncate: Journal has aborted
Feb 20 12:20:33 lds1 kernel: EXT3-fs error (device dm-0) in ext3_reserve_inode_write: Journal has aborted
Feb 20 12:20:33 lds1 kernel: EXT3-fs error (device dm-0) in ext3_orphan_del: Journal has aborted
Feb 20 12:20:33 lds1 kernel: EXT3-fs error (device dm-0) in ext3_reserve_inode_write: Journal has aborted
Feb 20 12:20:33 lds1 kernel: EXT3-fs error (device dm-0) in ext3_delete_inode: Journal has aborted
Feb 20 12:20:33 lds1 kernel: __journal_remove_journal_head: freeing b_committed_data
Feb 20 12:20:33 lds1 kernel: __journal_remove_journal_head: freeing b_committed_data
Feb 20 12:20:33 lds1 kernel: __journal_remove_journal_head: freeing b_committed_data
Feb 20 12:20:33 lds1 kernel: ext3_abort called.
Feb 20 12:20:33 lds1 kernel: EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal
Feb 20 12:20:33 lds1 kernel: Remounting filesystem read-only
.
.
nach einem reboot und dem mount Befehl stand dann in /var/log/messages
.
.
Feb 20 12:59:00 lds1 kernel: EXT3-fs warning (device dm-0): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
Feb 20 12:59:00 lds1 kernel: EXT3-fs warning (device dm-0): ext3_clear_journal_err: Marking fs in need of filesystem check.
Feb 20 12:59:00 lds1 kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Feb 20 12:59:00 lds1 kernel: EXT3 FS on dm-0, internal journal
Feb 20 12:59:00 lds1 kernel: EXT3-fs: recovery complete.
Feb 20 12:59:00 lds1 kernel: EXT3-fs: mounted filesystem with ordered data mode.
.
.
Dort steht - recovery complete -
Muss ich jetzt noch den - recommended e2fsck ausführen oder hat er das selbst gemacht und ist alles jetzt alles wieder ok?
Wie finde ich raus welche meiner Platten das device dm-0 ist?
mfg
Frank
Ich arbeite auch mit SLES 10 und habe dort folgendes Problem (gehabt???)
Ein RAID 0 (4 Platten a 320GB)
Plötzlich war das Filesystem nur noch READ only gemountet.
in /var/log/messages stand .....
.
.
Feb 20 12:19:49 lds1 kernel: EXT3-fs error (device dm-0): ext3_free_blocks: Freeing blocks not in datazone - block = 365684307, count = 1
Feb 20 12:19:49 lds1 kernel: Aborting journal on device dm-0.
.
.
Feb 20 12:20:32 lds1 kernel: EXT3-fs error (device dm-0): ext3_free_blocks: Freeing blocks not in datazone - block = 1955375396, count = 1
Feb 20 12:20:33 lds1 kernel: EXT3-fs error (device dm-0) in ext3_reserve_inode_write: Journal has aborted
Feb 20 12:20:33 lds1 kernel: EXT3-fs error (device dm-0) in ext3_truncate: Journal has aborted
Feb 20 12:20:33 lds1 kernel: EXT3-fs error (device dm-0) in ext3_reserve_inode_write: Journal has aborted
Feb 20 12:20:33 lds1 kernel: EXT3-fs error (device dm-0) in ext3_orphan_del: Journal has aborted
Feb 20 12:20:33 lds1 kernel: EXT3-fs error (device dm-0) in ext3_reserve_inode_write: Journal has aborted
Feb 20 12:20:33 lds1 kernel: EXT3-fs error (device dm-0) in ext3_delete_inode: Journal has aborted
Feb 20 12:20:33 lds1 kernel: __journal_remove_journal_head: freeing b_committed_data
Feb 20 12:20:33 lds1 kernel: __journal_remove_journal_head: freeing b_committed_data
Feb 20 12:20:33 lds1 kernel: __journal_remove_journal_head: freeing b_committed_data
Feb 20 12:20:33 lds1 kernel: ext3_abort called.
Feb 20 12:20:33 lds1 kernel: EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal
Feb 20 12:20:33 lds1 kernel: Remounting filesystem read-only
.
.
nach einem reboot und dem mount Befehl stand dann in /var/log/messages
.
.
Feb 20 12:59:00 lds1 kernel: EXT3-fs warning (device dm-0): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
Feb 20 12:59:00 lds1 kernel: EXT3-fs warning (device dm-0): ext3_clear_journal_err: Marking fs in need of filesystem check.
Feb 20 12:59:00 lds1 kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Feb 20 12:59:00 lds1 kernel: EXT3 FS on dm-0, internal journal
Feb 20 12:59:00 lds1 kernel: EXT3-fs: recovery complete.
Feb 20 12:59:00 lds1 kernel: EXT3-fs: mounted filesystem with ordered data mode.
.
.
Dort steht - recovery complete -
Muss ich jetzt noch den - recommended e2fsck ausführen oder hat er das selbst gemacht und ist alles jetzt alles wieder ok?
Wie finde ich raus welche meiner Platten das device dm-0 ist?
mfg
Frank