From: Jim Klimov <klimov@2ka.mipt.ru>
To: Neil Brown <neilb@suse.de>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re[2]: RAID1 submirror failure causes reboot?
Date: Fri, 10 Nov 2006 15:53:06 +0300 [thread overview]
Message-ID: <208777171.20061110155306@2ka.mipt.ru> (raw)
In-Reply-To: <17748.15156.405065.904318@cse.unsw.edu.au>
Hello Neil,
>> [87398.531579] blk: request botched
NB> ^^^^^^^^^^^^^^^^^^^^
NB> That looks bad. Possible some bug in the IDE controller or elsewhere
NB> in the block layer. Jens: What might cause that?
NB> --snip--
NB> That doesn't look like raid was involved. If it was you would expect
NB> to see raid1_end_write_request or raid1_end_read_request in that
NB> trace.
So that might be the hard or soft part of IDE layer failing the
system, or a PCI problem for example?
Just in case, motherboard is Supermicro X5DPE-G2: e7501 chipset,
Dual Xeon-533. Rather old now, way cool back when it was bought ;)
But, as anything new, it could be manufactured bad. Maybe now there
are some well-known problems with the tech?
NB> Do you have any other partitions of hdc in use but not on raid?
NB> Which partition is sector 176315718 in ??
All partitions are mirrored, and this sector is in hdc11:
# fdisk /dev/hdc
...
Command (m for help): u
Changing display/entry units to sectors
Command (m for help): p
Disk /dev/hdc: 102.9 GB, 102935347200 bytes
16 heads, 63 sectors/track, 199450 cylinders, total 201045600 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/hdc1 * 63 1000943 500440+ fd Linux raid autodetect
/dev/hdc2 1000944 5001695 2000376 fd Linux raid autodetect
/dev/hdc3 5001696 16721711 5860008 83 Linux
/dev/hdc4 16721712 201045599 92161944 5 Extended
/dev/hdc5 16721775 24534719 3906472+ 83 Linux
/dev/hdc6 24534783 28441727 1953472+ 83 Linux
/dev/hdc7 28441791 32348735 1953472+ 83 Linux
/dev/hdc8 32348799 44068751 5859976+ 83 Linux
/dev/hdc9 44068815 51881759 3906472+ 83 Linux
/dev/hdc10 51881823 59694767 3906472+ 83 Linux
/dev/hdc11 59694831 190555343 65430256+ 83 Linux
/dev/hdc12 190555407 201045599 5245096+ 83 Linux
--
Best regards,
Jim Klimov mailto:klimov@2ka.mipt.ru
next prev parent reply other threads:[~2006-11-10 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 8:17 RAID1 submirror failure causes reboot? Jim Klimov
2006-11-10 8:41 ` Neil Brown
2006-11-10 12:53 ` Jim Klimov [this message]
2006-11-13 7:17 ` Re[2]: " Neil Brown
2006-11-13 20:11 ` Jens Axboe
2006-11-13 22:05 ` Neil Brown
2006-11-14 7:28 ` Jens Axboe
2006-11-14 10:36 ` Re[4]: " Jim Klimov
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=208777171.20061110155306@2ka.mipt.ru \
--to=klimov@2ka.mipt.ru \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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.