From: micah <micah@riseup.net>
To: NeilBrown <neilb@suse.de>
Cc: micah anderson <micah@debian.org>, linux-raid@vger.kernel.org
Subject: Re: Raid1 element stuck in (S) state
Date: Sun, 02 Nov 2014 10:45:50 -0500 [thread overview]
Message-ID: <87tx2hobbl.fsf@muck.riseup.net> (raw)
In-Reply-To: <20141030094734.2451cc24@notabene.brown>
NeilBrown <neilb@suse.de> writes:
>> >> > Are there any errors in the kernel logs when you --add the device?
>> >
>> > You didn't answer this question either. Are there any messages in the
>> > kernel log: /var/log/kern.log on debian.
>> > Or in the output of "dmesg".
>>
>> The only thing I see in the log is:
>>
>> [307932.328420] mdadm: sending ioctl 1261 to a partition!
>> [307932.328425] mdadm: sending ioctl 1261 to a partition!
>> [307932.346642] mdadm: sending ioctl 1261 to a partition!
>> [307932.346648] mdadm: sending ioctl 1261 to a partition!
>> [307932.352466] mdadm: sending ioctl 1261 to a partition!
>> [307932.352468] mdadm: sending ioctl 1261 to a partition!
>> [307932.376821] mdadm: sending ioctl 1261 to a partition!
>> [307932.376824] mdadm: sending ioctl 1261 to a partition!
>> [307932.377623] mdadm: sending ioctl 1261 to a partition!
>> [307932.377630] mdadm: sending ioctl 1261 to a partition!
>> [307932.467292] md: bind<sdc1>
>> [307932.588154] RAID1 conf printout:
>> [307932.588159] --- wd:1 rd:2
>> [307932.588164] disk 0, wo:1, o:1, dev:sdc1
>> [307932.588167] disk 1, wo:0, o:1, dev:sdd1
>> [307932.588248] md: recovery of RAID array md3
>> [307932.588251] md: minimum _guaranteed_ speed: 50000 KB/sec/disk.
>> [307932.588254] md: using maximum available idle IO bandwidth (but not more than 2000000 KB/sec) for recovery.
>> [307932.588260] md: using 128k window, over a total of 976759672 blocks.
>>
>> but this is just when the device is added, after that it appears that
>> logrotation failed and I have a zero byte kern.log, and firewall spew
>> has filled up my dmesg ring.
I fixed my logging and re-added the device, and found there was a
hardware error preventing things from syncing properly. I've resolved
that error and now things are fine. Thanks for the push to look closer
there!
micah
prev parent reply other threads:[~2014-11-02 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 14:18 Raid1 element stuck in (S) state micah anderson
2014-10-27 20:57 ` Joe Lawrence
2014-10-28 4:45 ` micah
2014-10-28 21:42 ` NeilBrown
2014-10-29 14:03 ` micah
2014-10-29 20:10 ` NeilBrown
2014-10-29 21:32 ` micah
2014-10-29 22:47 ` NeilBrown
2014-11-02 15:45 ` micah [this message]
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=87tx2hobbl.fsf@muck.riseup.net \
--to=micah@riseup.net \
--cc=linux-raid@vger.kernel.org \
--cc=micah@debian.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.