Hey all,
Last night, I had a server crash. This morning, when I rebooted the machine, I ran into some issues with one of my ext3 scsi disks.
When I re-ran fsck.ext3 manually, I used "-p" to auto-repair all the problems. Unfortunately, it doesn't seem to be repairing the problems. Here is the output of the fsck.ext3 run:
(Repair filesystem) 1 # fsck.ext3 -pvf /dev/sda1
/dev/sda1: Duplicate or bad block in use!
/dev/sda1: Duplicate blocks found... invoking duplicate block passes.
Pass 1B: Rescan for duplicate/bad blocks
/dev/sda1: Duplicate/bad block(s) in inode 8:/dev/sda1: 255/dev/sda1:
/dev/sda1: Duplicate/bad block(s) in inode 12956827:/dev/sda1: 255/dev/sda1:
/dev/sda1: Duplicate/bad block(s) in inode 21571136:/dev/sda1: 255/dev/sda1:
/dev/sda1: Duplicate/bad block(s) in inode 21732272:/dev/sda1: 127/dev/sda1:
/dev/sda1: Duplicate/bad block(s) in inode 27987088:/dev/sda1: 170/dev/sda1:
/dev/sda1: Pass 1C: Scan directories for inodes with dup blocks.
/dev/sda1: Pass 1D: Reconciling duplicate blocks
/dev/sda1: (There are 4 inodes containing duplicate/bad blocks.)
/dev/sda1: File <The journal inode> (inode #8, mod time Wed Aug 13 12:15:57 2003)
has 1 duplicate block(s), shared with 2 file(s):
/dev/sda1: /8k/lib/r55/lib/_/emitter_control.adc
(inode #21571136, mod time Fri Feb 11 16:43:02 2000)
/dev/sda1: /8k/lib/r72/lib/_/navigation_message.adc
(inode #12956827, mod time Thu Jun 18 16:33:12 1998)
/dev/sda1:
/dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
(Repair filesystem) 2 # exit
Any insight is appreciated.
-Rob
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
