From: joe briggs <jbriggs@briggsmedia.com>
To: Edward Tandi <ed@efix.biz>,
Timothy Miller <miller@techsource.com>,
reiser@namesys.com
Cc: Artur Jasowicz <kernel@mousebusiness.com>,
Brian Jackson <brian@brianandsara.net>,
Bart SCHELSTRAETE <Bart.SCHELSTRAETE@dhl.com>,
Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: AMD MP, SMP, Tyan 2466, REISERFS I/O error
Date: Thu, 26 Jun 2003 08:25:54 -0400 [thread overview]
Message-ID: <200306260825.54076.jbriggs@briggsmedia.com> (raw)
In-Reply-To: <1056583075.31265.22.camel@wires.home.biz>
[-- Attachment #1: Type: text/plain, Size: 2266 bytes --]
I am working on a Tyan 2466 SMP/Athlon server now and am getting tons of
reiserf errors (see attached /var/log/syslog) that claim an i/o error, yet
the log does not show any errors from the driver (should it?).
Unfortunately, Reiser does not indicate which drive the error is produced
from. My configuration is:
Tyan 2466 SMP 2 x AMD2400-MP
512 MB PC2100 DDR-> not registered!
Debian woody
2.4.21 reiser
system drive (os, swap) wd800-bb (80 gb ide)
data drives: 3ware 7200, 2 x wd2000 (200 gb ide) RAID-0
On Wednesday 25 June 2003 07:17 pm, Edward Tandi wrote:
> On Wed, 2003-06-25 at 23:59, Timothy Miller wrote:
> > Edward Tandi wrote:
> > > Yes, for SMP mode you absolutely need to use 'registered' RAM. Normal
> > > PC2100 ram will work OK with one processor but quickly fails with two
> > > (I had the same problems). Apparently, DDR RAM uses one clock edge to
> > > transfer in one direction and the opposite edge to transfer back again
> > > so the registers do synchronisation between one processor writing to
> > > the same location that the other one reads from. That's how it was
> > > explained to me anyway.
> >
> > DDR memory works very much like single data rate, except that data is
> > transferred (in whichever direction it's going) on both edges of the
> > clock, thus doubling the transfer rate. The memory does not switch
> > between reading and writing as you describe it.
> >
> > I believe registering is for reliability. Data is transferred one clock
> > cycle later but reduces signal loading.
>
> Thanks for the clarification. I do not profess to be an expert in the
> technology. Two writes or a read+write per clock cycle is close enough
> for the purpose of the discussion.
>
> The point I was trying to make is that the registers are there to deal
> with an SMP race condition of some sort. Athlon MP motherboards fitted
> with two processors will not work properly without 'registered' RAM. I
> have hard experience of this and it this experience I am sharing with
> someone who is seeing the same symptoms.
>
> Ed-T.
--
Joe Briggs
Briggs Media Systems
105 Burnsen Ave.
Manchester NH 01304 USA
TEL 603-232-3115 FAX 603-625-5809 MOBILE 603-493-2386
www.briggsmedia.com
[-- Attachment #2: reiserfs.txt --]
[-- Type: text/plain, Size: 4336 bytes --]
Jun 26 07:04:10 sentry kernel: vs-5150: search_by_key: invalid format found in block 266772. Fsck?
Jun 26 07:04:10 sentry kernel: vs-5657: reiserfs_do_truncate: i/o failure occurred trying to truncate [22 154 0xfffffffffffffff DIRECT]
Jun 26 07:04:10 sentry kernel: is_tree_node: node level 11226 does not match to the expected one 1
Jun 26 07:04:10 sentry kernel: vs-5150: search_by_key: invalid format found in block 266772. Fsck?
Jun 26 07:04:10 sentry kernel: vs-5350: reiserfs_delete_solid_item: i/o failure occurred trying to delete [22 154 0x0 SD]
Jun 26 07:04:10 sentry kernel: is_tree_node: node level 11226 does not match to the expected one 1
Jun 26 07:04:10 sentry kernel: vs-5150: search_by_key: invalid format found in block 266772. Fsck?
Jun 26 07:04:10 sentry kernel: vs-13050: reiserfs_update_sd: i/o failure occurred trying to update [22 140 0x0 SD] stat datais_tree_node: node level 11226 does not match to the expected one 1
Jun 26 07:04:10 sentry kernel: vs-5150: search_by_key: invalid format found in block 266772. Fsck?
Jun 26 07:04:10 sentry kernel: vs-5657: reiserfs_do_truncate: i/o failure occurred trying to truncate [22 140 0xfffffffffffffff DIRECT]
Jun 26 07:04:10 sentry kernel: is_tree_node: node level 11226 does not match to the expected one 1
Jun 26 07:04:10 sentry kernel: vs-5150: search_by_key: invalid format found in block 266772. Fsck?
Jun 26 07:04:10 sentry kernel: vs-5350: reiserfs_delete_solid_item: i/o failure occurred trying to delete [22 140 0x0 SD]
Jun 26 07:04:10 sentry kernel: is_tree_node: node level 11226 does not match to the expected one 1
Jun 26 07:04:10 sentry kernel: vs-5150: search_by_key: invalid format found in block 266772. Fsck?
Jun 26 07:04:10 sentry kernel: vs-13050: reiserfs_update_sd: i/o failure occurred trying to update [22 101 0x0 SD] stat datais_tree_node: node level 11226 does not match to the expected one 1
Jun 26 07:04:10 sentry kernel: vs-5150: search_by_key: invalid format found in block 266772. Fsck?
Jun 26 07:04:10 sentry kernel: vs-5657: reiserfs_do_truncate: i/o failure occurred trying to truncate [22 101 0xfffffffffffffff DIRECT]
Jun 26 07:04:10 sentry kernel: is_tree_node: node level 11226 does not match to the expected one 1
Jun 26 07:04:10 sentry kernel: vs-5150: search_by_key: invalid format found in block 266772. Fsck?
Jun 26 07:04:10 sentry kernel: vs-5350: reiserfs_delete_solid_item: i/o failure occurred trying to delete [22 101 0x0 SD]
Jun 26 07:04:10 sentry kernel: is_tree_node: node level 11226 does not match to the expected one 1
Jun 26 07:04:10 sentry kernel: vs-5150: search_by_key: invalid format found in block 266772. Fsck?
Jun 26 07:04:10 sentry kernel: vs-13050: reiserfs_update_sd: i/o failure occurred trying to update [22 152 0x0 SD] stat datais_tree_node: node level 11226 does not match to the expected one 1
Jun 26 07:04:10 sentry kernel: vs-5150: search_by_key: invalid format found in block 266772. Fsck?
Jun 26 07:04:10 sentry kernel: vs-5657: reiserfs_do_truncate: i/o failure occurred trying to truncate [22 152 0xfffffffffffffff DIRECT]
Jun 26 07:04:10 sentry kernel: is_tree_node: node level 11226 does not match to the expected one 1
Jun 26 07:04:10 sentry kernel: vs-5150: search_by_key: invalid format found in block 266772. Fsck?
Jun 26 07:04:10 sentry kernel: vs-5350: reiserfs_delete_solid_item: i/o failure occurred trying to delete [22 152 0x0 SD]
Jun 26 07:04:10 sentry kernel: is_tree_node: node level 11226 does not match to the expected one 1
Jun 26 07:04:10 sentry kernel: vs-5150: search_by_key: invalid format found in block 266772. Fsck?
Jun 26 07:04:10 sentry kernel: vs-13050: reiserfs_update_sd: i/o failure occurred trying to update [22 104 0x0 SD] stat datais_tree_node: node level 11226 does not match to the expected one 1
Jun 26 07:04:10 sentry kernel: vs-5150: search_by_key: invalid format found in block 266772. Fsck?
Jun 26 07:04:10 sentry kernel: vs-5657: reiserfs_do_truncate: i/o failure occurred trying to truncate [22 104 0xfffffffffffffff DIRECT]
Jun 26 07:04:10 sentry kernel: is_tree_node: node level 11226 does not match to the expected one 1
Jun 26 07:04:10 sentry kernel: vs-5150: search_by_key: invalid format found in block 266772. Fsck?
Jun 26 07:04:10 sentry kernel: vs-5350: reiserfs_delete_solid_item: i/o failure occurred trying to delete [22 104 0x0 SD]
next prev parent reply other threads:[~2003-06-26 11:13 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 16:37 Crusoe's persistent translation on linux? Samphan Raruenrom
2003-06-19 18:03 ` Vojtech Pavlik
2003-06-19 19:51 ` Samphan Raruenrom
2003-06-20 0:02 ` Nuno Silva
2003-06-20 0:16 ` Linus Torvalds
2003-06-20 2:08 ` Nuno Silva
2003-06-20 9:08 ` Xavier Bestel
2003-06-20 9:33 ` Nick Piggin
2003-06-20 14:08 ` Henning P. Schmiedehausen
2003-06-20 15:38 ` Linus Torvalds
2003-06-20 16:51 ` AMD MP, SMP, Tyan 2466 kernel
2003-06-20 17:08 ` Bart SCHELSTRAETE
2003-06-20 17:09 ` Brian Jackson
2003-06-25 17:37 ` Artur Jasowicz
2003-06-25 18:51 ` joe briggs
2003-06-25 18:16 ` Mike Dresser
2003-07-21 20:52 ` Artur Jasowicz
2003-07-22 4:02 ` Jason
2003-07-23 12:19 ` paterley
2003-07-23 20:03 ` Joe Briggs
2003-06-25 19:01 ` joe briggs
2003-06-25 18:56 ` Edward Tandi
2003-06-25 22:59 ` Timothy Miller
2003-06-25 23:17 ` Edward Tandi
2003-06-25 23:26 ` Timothy Miller
2003-06-25 23:39 ` Timothy Miller
2003-06-26 0:29 ` Edward Tandi
2003-06-25 23:40 ` Edward Tandi
2003-06-26 15:12 ` Herbert Poetzl
2003-06-25 23:35 ` Joel Jaeggli
2003-06-26 12:25 ` joe briggs [this message]
2003-06-26 11:55 ` AMD MP, SMP, Tyan 2466, REISERFS I/O error Oleg Drokin
2003-06-26 13:37 ` joe briggs
2003-06-26 23:15 ` Timothy Miller
2003-06-26 23:48 ` Joel Jaeggli
2003-06-27 13:01 ` joe briggs
2003-06-20 12:05 ` Crusoe's persistent translation on linux? Samphan Raruenrom
[not found] ` <20030619221126.B3287@ucw.cz>
2003-06-23 3:58 ` Crusoe's performance " Samphan Raruenrom
2003-06-23 5:22 ` H. Peter Anvin
2003-06-23 5:40 ` Grzegorz Jaskiewicz
2003-06-23 8:10 ` Vojtech Pavlik
2003-06-23 8:26 ` Vojtech Pavlik
2003-06-23 18:58 ` Samphan Raruenrom
2003-06-24 1:43 ` dean gaudet
2003-06-24 4:33 ` dean gaudet
2003-06-24 22:54 ` Samphan Raruenrom
2003-06-24 23:06 ` dean gaudet
2003-06-23 23:46 ` H. Peter Anvin
2003-06-24 0:51 ` H. Peter Anvin
2003-06-26 3:39 ` H. Peter Anvin
2003-06-26 4:22 ` H. Peter Anvin
[not found] ` <200306240051.RAA12097@cesium.transmeta.com>
2003-06-26 19:09 ` Samphan Raruenrom
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=200306260825.54076.jbriggs@briggsmedia.com \
--to=jbriggs@briggsmedia.com \
--cc=Bart.SCHELSTRAETE@dhl.com \
--cc=brian@brianandsara.net \
--cc=ed@efix.biz \
--cc=kernel@mousebusiness.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
--cc=reiser@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox