| View previous topic :: View next topic |
| Author |
Message |
NickDaFish
Tux's lil' helper
Joined: 12 Sep 2002
Posts: 112
Location: Boston, USA
|
 Posted: Mon Mar 24, 2003 5:59 pm Post subject: Lots of ext2 errors reported by e2fsck |
 |
|
I built an old Gateway machine into a postfix mail server a little while ago, to handle bulk mailings (10000+ mails). It's using a Promise66 (Non-RAID) card and it's drive appears to be getting alot of errors. Every now and then I will run....
| Code: | | e2fsck -n -v -f /dev/hde3 |
Most of the time it reports a few wrongly sized inodes but occationaly it goes nuts. It reports pages and pages of errors and often segfaults before finishing. I can take the machine offline and repair the errors but this seemes to be happeneing alot. If I check on of my other gentoo machines I get a one or two errors but nothing on the scale of the postfix machine. Also the boot partition (part of the same disk) never has any errors.
Here are some examples of what I get...
| Quote: | Error reading block 762082163 (Invalid argument) while doing inode scan.
HTREE directory inode 64712 has an unsupported hash version (28)
HTREE directory inode 64712 uses an incompatible htree root node flag.
HTREE directory inode 64712 has a tree depth (17) which is too big
Inode 178686 has INDEX_FL flag set but is not a directory.
Entry 'openssl-rand.3.gz' in /usr/share/man/man3 (64712) has an incorrect filetype (was 7, should be 0).
Problem in HTREE directory inode 178439 (/usr/portage/metadata/cache/sys-apps): bad block number 720920. |
I'm kinda worryed about this. Does this point to a bad disk? Contoller? Driver? Or should I just expect this sort of thing on a ext2 partition that does so much disk thrashing? |
|
| Back to top |
|
 |
Malakin
Veteran
Joined: 14 Apr 2002
Posts: 1692
Location: Victoria BC Canada
|
| Posted: Mon Mar 24, 2003 6:52 pm Post subject: |
|
|
| Sounds like something is wrong. You can run "badblocks" on the drive or you can download a utility from the drive manufacturers site to check the drive. |
|
| Back to top |
|
|
NickDaFish
Tux's lil' helper
Joined: 12 Sep 2002
Posts: 112
Location: Boston, USA
|
| Posted: Mon Mar 24, 2003 10:43 pm Post subject: |
|
|
The drive was in use in annother system before and it was fine. I just ran a e2fsck using the '-c' option and it reported no bad blocks. I also ran badblocks on it's own and that didn't report anything either.
I don't think it's the drive (Physically at least).
Any more ideas anybody?  |
|
| Back to top |
|
|
|
Kernel & Hardware
