From: Kristian <kristian@korseby.net>
To: "Roeland Th. Jansen" <roel@grobbebol.xs4all.nl>,
David Weinehall <tao@acc.umu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext2fs corruption again
Date: Sat, 15 Sep 2001 16:49:22 +0200 [thread overview]
Message-ID: <3BA36A72.20702@korseby.net> (raw)
In-Reply-To: <3BA33818.8030503@korseby.net> <20010915122113.A24561@grobbebol.xs4all.nl>
Roeland Th. Jansen wrote:
> not that I say IBM's drive is bad, it's just a thought.
They are bad if it's hardware-related. The big one is manufactured in Hungary,
the other one in Thaiwan.
The error occured again.
I post the new errors. Maybe you can see any structure in it.
Sep 15 16:16:23 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: bit already cleared for block (5412-5427)
e2fsck reported the following on that device (hda5):
++ entries are new with this check
-- entries only appeared earlier
Duplicate/bad bock(s) in inode: 97: 643 +644+
Duplicate/bad bock(s) in inode: 98: +647+
Duplicate/bad bock(s) in inode: 99: +648+
Duplicate/bad bock(s) in inode: 100: 649
Duplicate/bad bock(s) in inode: 101: 650 651
Duplicate/bad bock(s) in inode: 102: 652
Duplicate/bad bock(s) in inode: 103: 653 656 +657+
Duplicate/bad bock(s) in inode: 104: +658+ 659 660
Duplicate/bad bock(s) in inode: 105: 661 662 663 664 665 666
Duplicate/bad bock(s) in inode: 106: 667 -668-
Duplicate/bad bock(s) in inode: 107: 669 -671-
-Duplicate/bad bock(s) in inode: 108: 672 673 674-
-Duplicate/bad bock(s) in inode: 110: 678-
767011: 647 648 649 650 651 652 653 654 671
832166: 655 656 657 658 659 660 661 662
832170: 643 644
832178: 663 664 665 666 667
832178 is /var/log/boot.log
832170 is /var/log/wtmp
832166 is /var/log/messages
767011 is /home/tisi/syslog
Only syslog related files are concerned.
syslog is configured that it will accept logs from other machines. Maybe there's
a possibility that these strange errors were caused by the network-card or
-driver ? I own an eepro100. Just a thought...
These errors occured since 2.4.5 that's why I think it's software-related.
I'll try to use 'hdparm -d1 -X33 /dev/hda' and other modes to see if it occurs
again. But testing could take some time. It appears ~~ every second day.
Kristian
·· · · reach me :: · ·· ·· · · ·· · ·· · ··· · ·
:: http://www.korseby.net
:: http://www.tomlab.de
kristian@korseby.net ....::
next prev parent reply other threads:[~2001-09-15 14:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-15 11:14 ext2fs corruption again Kristian Peters
2001-09-15 12:21 ` Roeland Th. Jansen
2001-09-15 14:49 ` Kristian [this message]
2001-09-15 21:04 ` Mike Fedyk
2001-09-15 15:48 ` Mohammad A. Haque
2001-09-15 16:19 ` Kristian Peters
-- strict thread matches above, loose matches on Subject: below --
2001-09-15 10:44 Kristian
2001-09-15 8:46 Kristian
2001-09-15 12:42 ` David Weinehall
2001-09-15 17:19 ` David Rees
2001-09-15 17:55 ` Kristian Peters
2001-09-15 22:19 ` Pavel Machek
2001-09-15 23:51 ` Andreas Dilger
2001-09-16 19:33 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BA36A72.20702@korseby.net \
--to=kristian@korseby.net \
--cc=linux-kernel@vger.kernel.org \
--cc=roel@grobbebol.xs4all.nl \
--cc=tao@acc.umu.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox