From: AndyLiebman@aol.com
To: linux-raid@vger.kernel.org
Subject: What does "kicking non-fresh partition from array" mean?
Date: Fri, 23 Jan 2004 12:56:51 EST [thread overview]
Message-ID: <4a.26fcff87.2d42ba63@aol.com> (raw)
Hi all,
Can somebody tell me if some log warnings I'm seeing are worrisome? Does
"kicking non-fresh scsi/host4/bus0/target1/lun0/part1 from array!" refer to md4
or md6?
As you can see from cat /proc/mdstat, I have a failed removed drive in md6 --
which I am about to replace. Does this "kicking out" from the Kernel Warnings
log refer to md4 or md6?
FROM KERNEL WARNINGS LOG:
I see this every time I reboot
Jan 20 09:04:50 localhost kernel: md: device name has changed from
scsi/host2/bus0/target1/lun0/part1 to scsi/host2/bus0/target0/lun0/part1 since last
import!
Jan 20 09:04:50 localhost kernel: 8regs : 1828.800 MB/sec
Jan 20 09:04:50 localhost kernel: 32regs : 1248.000 MB/sec
Jan 20 09:04:50 localhost kernel: pII_mmx : 2568.000 MB/sec
Jan 20 09:04:50 localhost kernel: p5_mmx : 2561.600 MB/sec
Jan 20 09:04:50 localhost kernel: raid5: using function: pII_mmx (2568.000
MB/sec)
Jan 20 09:04:50 localhost kernel: raid5: raid level 5 set md4 active with 5
out of 5 devices, algorithm 2
Jan 20 09:04:50 localhost kernel: RAID5 conf printout:
Jan 20 09:04:50 localhost kernel: --- rd:5 wd:5 fd:0
Jan 20 09:04:50 localhost kernel: disk 0, s:0, o:1, n:0 rd:0 us:1
dev:scsi/host1/bus0/target0/lun0/part1
Jan 20 09:04:50 localhost kernel: disk 1, s:0, o:1, n:1 rd:1 us:1
dev:scsi/host2/bus0/target0/lun0/part1
Jan 20 09:04:50 localhost kernel: disk 2, s:0, o:1, n:2 rd:2 us:1
dev:scsi/host5/bus0/target0/lun0/part1
Jan 20 09:04:50 localhost kernel: disk 3, s:0, o:1, n:3 rd:3 us:1
dev:scsi/host3/bus0/target0/lun0/part1
Jan 20 09:04:50 localhost kernel: disk 4, s:0, o:1, n:4 rd:4 us:1
dev:scsi/host4/bus0/target0/lun0/part1
Jan 20 09:04:50 localhost kernel: RAID5 conf printout:
Jan 20 09:04:50 localhost kernel: --- rd:5 wd:5 fd:0
Jan 20 09:04:50 localhost kernel: disk 0, s:0, o:1, n:0 rd:0 us:1
dev:scsi/host1/bus0/target0/lun0/part1
Jan 20 09:04:50 localhost kernel: disk 1, s:0, o:1, n:1 rd:1 us:1
dev:scsi/host2/bus0/target0/lun0/part1
Jan 20 09:04:50 localhost kernel: disk 2, s:0, o:1, n:2 rd:2 us:1
dev:scsi/host5/bus0/target0/lun0/part1
Jan 20 09:04:50 localhost kernel: disk 3, s:0, o:1, n:3 rd:3 us:1
dev:scsi/host3/bus0/target0/lun0/part1
Jan 20 09:04:50 localhost kernel: disk 4, s:0, o:1, n:4 rd:4 us:1
dev:scsi/host4/bus0/target0/lun0/part1
Jan 20 09:04:51 localhost kernel: md: kicking non-fresh
scsi/host4/bus0/target1/lun0/part1 from array!
Jan 20 09:04:51 localhost kernel: md: device name has changed from
scsi/host2/bus0/target0/lun0/part1 to scsi/host2/bus0/target1/lun0/part1 since last
import!
Jan 20 09:04:51 localhost kernel: RAID5 conf printout:
Jan 20 09:04:51 localhost kernel: --- rd:5 wd:4 fd:1
Jan 20 09:04:51 localhost kernel: disk 0, s:0, o:1, n:0 rd:0 us:1
dev:scsi/host1/bus0/target1/lun0/part1
Jan 20 09:04:51 localhost kernel: disk 1, s:0, o:1, n:1 rd:1 us:1
dev:scsi/host2/bus0/target1/lun0/part1
Jan 20 09:04:51 localhost kernel: disk 2, s:0, o:1, n:2 rd:2 us:1
dev:scsi/host3/bus0/target1/lun0/part1
Jan 20 09:04:51 localhost kernel: disk 3, s:0, o:0, n:3 rd:3 us:1 dev:[dev
00:00]
Jan 20 09:04:51 localhost kernel: disk 4, s:0, o:1, n:4 rd:4 us:1
dev:scsi/host5/bus0/target1/lun0/part1
Jan 20 09:04:51 localhost kernel: RAID5 conf printout:
Jan 20 09:04:51 localhost kernel: --- rd:5 wd:4 fd:1
Jan 20 09:04:51 localhost kernel: disk 0, s:0, o:1, n:0 rd:0 us:1
dev:scsi/host1/bus0/target1/lun0/part1
Jan 20 09:04:51 localhost kernel: disk 1, s:0, o:1, n:1 rd:1 us:1
dev:scsi/host2/bus0/target1/lun0/part1
Jan 20 09:04:51 localhost kernel: disk 2, s:0, o:1, n:2 rd:2 us:1
dev:scsi/host3/bus0/target1/lun0/part1
Jan 20 09:04:51 localhost kernel: disk 3, s:0, o:0, n:3 rd:3 us:1 dev:[dev
00:00]
Jan 20 09:04:51 localhost kernel: disk 4, s:0, o:1, n:4 rd:4 us:1
dev:scsi/host5/bus0/target1/lun0/part1
reply other threads:[~2004-01-23 17:56 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=4a.26fcff87.2d42ba63@aol.com \
--to=andyliebman@aol.com \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).