From: Resident Boxholder <resid@boxho.com>
To: Kernel List <linux-kernel@vger.kernel.org>
Subject: how to log reiser and raid0 crash? 2.6.0-t4
Date: Tue, 26 Aug 2003 15:57:39 -0400 [thread overview]
Message-ID: <3F4BBBB3.2080100@boxho.com> (raw)
In-Reply-To: <1061926566.1076.2.camel@teapot.felipe-alfaro.com>
2.6.0-test4 amd xp 3000+ msi mbo nforce2 four Maxtor 60G 8mbcache raid0
I cause a lock up by doing a cp -aR /usr/src /mnt/usr which moves data
larger
than total hard buffer cache, to raid0 reiserfs or ext2 ( NOT reiser4!)
Copy ops
smaller than buffer cache(8mb x 4 = 32mb) don't fail. Nothing fails on a
single
drive, compiles or copies, just copy to a mounted raid0 device. What
should I
try, test, or dump?
No irq error storm. No cd drives installed. Smaller copy ops work. Turning
swap off first slows things down enough to work, but swap itself is probably
OK. I have bios turn apic off, then linux turns it on, which is good
until the
turn apic off before turn apic on patch gets into test5 or whatever.
hdparm sets all four drives the same, udma6 but have tried down to udma4
and pio4 and dma turned off, unmask on or off.
If two drives are on the mboard controller and two on a promise pci card,
does /proc/ide/amd74xx refer to the two drives on the motherboard only?
It seems to mention four drives but the two slow ones might just be a
ref to unoccupied slave drive positions.
I'm wondering what to send in. Maybe I could send a log from successful
copy with swap off, showing reiser logging, and config, in case a stress
condition or misconfig shows up even when catastrophic failure doesn't
occur. With swap on the fail is sudden and no error logging is coming
through.
I could incrementally copy /usr/src to one raid, then do a copy from that
raid to another raid. All that would do is test copying from one balanced
set of four drives/partitions to another balanced set, versus copying from
one drive's /usr/src to that and three other drives' raid set, which is
unbalanced, dragging on one drive.
-Bob
next prev parent reply other threads:[~2003-08-26 20:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 10:22 reiser4 snapshot for August 26th Oleg Drokin
2003-08-26 18:20 ` Steven Cole
2003-08-26 18:26 ` Alex Zarochentsev
2003-08-26 19:36 ` Felipe Alfaro Solana
2003-08-26 19:43 ` Oleg Drokin
2003-08-26 19:51 ` Steven Cole
2003-08-26 20:05 ` Mike Fedyk
2003-08-26 20:13 ` Steven Cole
2003-08-26 20:26 ` Mike Fedyk
2003-08-26 20:25 ` Steven Cole
2003-08-26 20:30 ` Hans Reiser
2003-08-26 20:28 ` Hans Reiser
2003-08-26 19:53 ` Mike Fedyk
2003-08-26 19:57 ` Resident Boxholder [this message]
2003-08-26 22:20 ` how to log reiser and raid0 crash? 2.6.0-t4 Resident Boxholder
2003-08-27 10:35 ` Oleg Drokin
2003-08-28 7:28 ` Resident Boxholder
2003-08-26 18:38 ` reiser4 snapshot for August 26th Steven Cole
2003-08-26 19:22 ` Hans Reiser
2003-08-26 18:38 ` Oleg Drokin
2003-08-26 18:41 ` Hans Reiser
2003-08-26 18:41 ` Alex Zarochentsev
2003-08-26 19:14 ` Steven Cole
2003-08-28 11:46 ` Alex Zarochentsev
2003-08-28 15:12 ` Steven Cole
2003-08-28 16:33 ` Tupshin Harper
2003-08-26 19:15 ` Hans Reiser
2003-08-28 18:31 ` Vladimir Demidov
2003-08-26 21:28 ` Diego Calleja García
2003-08-27 7:38 ` Oleg Drokin
2003-08-27 5:52 ` Ian Wienand
2003-08-27 6:03 ` Yury Umanets
2003-08-27 11:19 ` Felipe Alfaro Solana
2003-08-27 15:54 ` Hans Reiser
2003-09-15 11:15 ` reiser4 snapshot 20030905 [OOPS] Maciej Soltysiak
2003-09-15 13:52 ` Nikita Danilov
[not found] <785F348679A4D5119A0C009027DE33C105CDAFC0@mcoexc04.mlm.maxtor.com>
2003-08-28 21:56 ` how to log reiser and raid0 crash? 2.6.0-t4 Resident Boxholder
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=3F4BBBB3.2080100@boxho.com \
--to=resid@boxho.com \
--cc=linux-kernel@vger.kernel.org \
/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