linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Don Jessup <donj@asaca.com>
To: linux-raid@vger.kernel.org
Subject: MD Warnings on RAID5 linux 2.4.22
Date: Fri, 26 Mar 2004 15:24:38 -0800 (PST)	[thread overview]
Message-ID: <20040326232438.98003.qmail@web14526.mail.yahoo.com> (raw)



  I have raid 5 array that I'm --assembling on a computer but when I
 assemble it and start and stop the array.  I get the following warnings.



Apr  5 15:19:57 DM200_791498 kernel: md14: WARNING: [dev e7:a4] appears to be
on the same physical disk as [dev
e7:a0]. True
Apr  5 15:19:57 DM200_791498 kernel:      protection against single-disk
failure might be compromised.
Apr  5 15:19:57 DM200_791498 kernel: md: bind<[dev e7:a4],5>
Apr  5 15:19:58 DM200_791498 kernel:  [events: 0000007f]
Apr  5 15:19:58 DM200_791498 kernel: md14: WARNING: [dev e7:90] appears to be
on the same physical disk as [dev
e7:a4]. True
Apr  5 15:19:58 DM200_791498 kernel:      protection against single-disk
failure might be compromised.
Apr  5 15:19:58 DM200_791498 kernel: md: bind<[dev e7:90],6>




   I was wondering how to make these warnings stop?  There does not 
  seem to be a problem with single disk failure.

   The command I'm using to assemble the RAID looks like the following:
      mdadm --assemble /dev/md14
--uuid=c9cc5194:50e0de0d:af3b7236:a60790c9
--update=super-minor /dev/mapd145:1 /dev/mapd149:1 /dev/mapd153:1
/dev/mapd157:1 /dev/mapd161:1 /dev/mapd165:1


=====
Don Jessup
Asaca/Shibasoku Corp. of America
400 Corporate Circle, Unit G
Golden, CO  80401
303-278-1111 X232
donj@asaca.com
http://www.asaca.com

             reply	other threads:[~2004-03-26 23:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-26 23:24 Don Jessup [this message]
2004-03-26 23:38 ` MD Warnings on RAID5 linux 2.4.22 Guy
2004-03-28 10:17 ` Luca Berra

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=20040326232438.98003.qmail@web14526.mail.yahoo.com \
    --to=donj@asaca.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).