From: Jens Benecke <jens@spamfreemail.de>
To: reiserfs-list@namesys.com
Subject: Re: $25 question - ReiserFS 3.6 data errors on 2.4.23
Date: Mon, 01 Mar 2004 13:30:36 +0100 [thread overview]
Message-ID: <c1va9o$ahg$1@sea.gmane.org> (raw)
In-Reply-To: 1077098911.5090.38.camel@tribesman.namesys.com
Vladimir Saveliev wrote:
>> Feb 17 14:40:18 linux1 kernel: is_leaf: item location seems wrong (second
>> one): *3.6* [68637 68643 0x1 IND], item_len 8, item_location 1444,
>> free_space(entry_count) 0
>> Feb 17 14:40:18 linux1 kernel: drbd(43,0):vs-5150: search_by_key: invalid
>> format found in block 4683374. Fsck?
> These days usually when one notices similar corruptions - he later
> discovers hardware problem (memory problem more often). May I ask you to
> try memtest for some time.
We finally found time to halt one machine and did. memtest86 finds about 150
seemingly random places in RAM where bit errors occur.
It's a wonder that Linux had an uptime of over 90 days with almost flawless
operation on a machine with THAT kind of hopelessly b0rken RAM.
Thank you for being so stubborn about hardware errors. :-)
--
Jens Benecke (jens at spamfreemail.de)
http://www.hitchhikers.de - Europaweite kostenlose Mitfahrzentrale
http://www.spamfreemail.de - 100% saubere Postfächer - garantiert!
http://www.rb-hosting.de - PHP ab 9? - SSH ab 19? - günstiger Traffic
next prev parent reply other threads:[~2004-03-01 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040218093510.GD21098@backtop.namesys.com>
2004-02-18 10:08 ` $25 question - ReiserFS 3.6 data errors on 2.4.23 Vladimir Saveliev
2004-02-18 10:32 ` Jens Benecke
2004-02-18 13:27 ` Nick Burrett
2004-02-18 13:42 ` Jens Benecke
2004-02-20 1:41 ` Tom Vier
2004-03-01 12:30 ` Jens Benecke [this message]
2004-02-17 13:52 Jens Benecke
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='c1va9o$ahg$1@sea.gmane.org' \
--to=jens@spamfreemail.de \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.