From: "Kyle" <kyle@southa.com>
To: <linux-kernel@vger.kernel.org>
Subject: raidhotadd freeze server (kernel 2.6.1)
Date: Mon, 16 Feb 2004 02:42:27 +0800 [thread overview]
Message-ID: <01f201c3f3f3$762bf2a0$353ffea9@kyle> (raw)
Today I found that one of my harddisk (/dev/hda) failed, /dev/hda and
/dev/hdc are md-raid1 mirrored.
Feb 13 23:06:08 s1 kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Feb 13 23:06:08 s1 kernel: hda: dma_intr: error=0x40 { UncorrectableError },
LBAsect=159025049, high=9, low=8030105,sector=159025044
Feb 13 23:06:08 s1 kernel: end_request: I/O error, dev hda, sector 159025044
Feb 13 23:06:08 s1 kernel: raid1: Disk failure on hda3, disabling device.
Feb 13 23:06:08 s1 kernel: ^IOperation continuing on 1 devices
Feb 13 23:06:08 s1 kernel: raid1: hda3: rescheduling sector 154719624
Feb 13 23:06:08 s1 kernel: raid1: hdc3: redirecting sector 154719624 to
another mirror
Feb 13 23:06:09 s1 kernel: RAID1 conf printout:
Feb 13 23:06:09 s1 kernel: --- wd:1 rd:2
Feb 13 23:06:09 s1 kernel: disk 0, wo:0, o:1, dev:hdc3
Feb 13 23:06:09 s1 kernel: disk 1, wo:1, o:0, dev:hda3
Feb 13 23:06:09 s1 kernel: RAID1 conf printout:
Feb 13 23:06:09 s1 kernel: --- wd:1 rd:2
Feb 13 23:06:09 s1 kernel: disk 0, wo:0, o:1, dev:hdc3
Then I tried:
raidhotremove /dev/md1 /dev/hda3
and then wondering if I raidhotadd back /dev/hda3, the harddisk would be
okay ......:
raidhotadd /dev/md1 /dev/hda3
and my server freeze immediately!
/dev/md0 -> /boot
/dev/md1 -> /
/dev/md2 -> swap
I have to press the reset button to reboot the machine.
at /var/log/message, I found:
Feb 15 23:45:23 s1 kernel: process `nslookup' is using obsolete setsockopt
SO_BSDCOMPAT
Feb 15 23:52:01 s1 kernel: md: trying to hot-add hda3 to md1 ...
Feb 15 23:52:01 s1 kernel: md: could not lock hda3.
Feb 15 23:52:01 s1 kernel: md: error, md_import_device() returned -16
Feb 15 23:53:07 s1 kernel: md: trying to hot-add hda3 to md1 ...
Feb 15 23:53:07 s1 kernel: md: could not lock hda3.
Feb 15 23:53:07 s1 kernel: md: error, md_import_device() returned -16
Feb 15 23:55:54 s1 kernel: md: trying to hot-add hda3 to md1 ...
Feb 15 23:55:54 s1 kernel: md: could not lock hda3.
Feb 15 23:55:54 s1 kernel: md: error, md_import_device() returned -16
Feb 15 23:57:47 s1 kernel: md: trying to hot-add hda3 to md1 ...
Feb 15 23:57:47 s1 kernel: md: could not lock hda3.
Feb 15 23:57:47 s1 kernel: md: error, md_import_device() returned -16
Feb 15 23:59:02 s1 kernel: md: trying to hot-add hda3 to md1 ...
Feb 15 23:59:02 s1 kernel: md: could not lock hda3.
Feb 15 23:59:02 s1 kernel: md: error, md_import_device() returned -16
Feb 15 23:59:14 s1 kernel: md: trying to hot-add md1 to md1 ...
Feb 15 23:59:19 s1 kernel: md: could not lock md1.
Feb 15 23:59:19 s1 kernel: md: error, md_import_device() returned -4
Feb 15 23:59:49 s1 kernel: md: trying to hot-add hdc3 to md1 ...
Feb 15 23:59:49 s1 kernel: md: could not lock hdc3.
Feb 15 23:59:49 s1 kernel: md: error, md_import_device() returned -16
Feb 16 00:00:30 s1 kernel: md: trying to remove hda3 from md1 ...
Feb 16 00:00:30 s1 kernel: md: unbind<hda3>
Feb 16 00:00:30 s1 kernel: md: export_rdev(hda3)
Feb 16 01:13:24 s1 syslogd 1.4.1: restart. <- hard rebooted
Feb 16 01:13:24 s1 syslog: syslogd startup succeeded
Feb 16 01:13:24 s1 kernel: klogd 1.4.1, log source = /proc/kmsg started.
Feb 16 01:13:24 s1 kernel: Linux version 2.6.1 (root@s1.pbasehk.com) (gcc
versi$
Feb 16 01:13:24 s1 kernel: BIOS-provided physical RAM map:
........
Is it kernel problem, or md problem or my problem?
Please CC my email since I read the list from web, thanks!
Kyle
reply other threads:[~2004-02-15 18:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='01f201c3f3f3$762bf2a0$353ffea9@kyle' \
--to=kyle@southa.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
all inboxes | Powered by JetHome®