mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: What does 'WrongLevel' mean in RAID0 ?
Date: Tue, 12 Apr 2005 22:08:23 +0000	[thread overview]
Message-ID: <1113343703l.9659l.0l@werewolf.able.es> (raw)
In-Reply-To: <16988.17389.81020.101830@cse.unsw.edu.au> (from neilb@cse.unsw.edu.au on Tue Apr 12 23:55:57 2005)


On 04.12, Neil Brown wrote:
> On Tuesday April 12, jamagallon@able.es wrote:
> > Hi all...
> > 
> > I have a RAID0 setup on top of three IDE drives.
> > mdadm monitor sends me mesages with:
> > 
> > DeviceDisappeared
> > /dev/md0
> > Wrong-Level
> > 
> > The RAID seems to be working well. Any pointer on what does this
> > mean ?
> 
>  From  "man mdadm"  (if you know where to look)
> 
>        Follow or Monitor
>               Monitor  one  or  more  md devices and act on any state changes.
>               This is only meaningful for raid1, 4, 5, 6 or  multipath  arrays
>               as  only  these  have  interesting state.  raid0 or linear never
>               have missing, spare, or failed drives, so there  is  nothing  to
>               monitor.
> 
> You are presumably trying to monitor a raid0 (which isn't meaningful)
> and mdadm is telling you (in its own idiosyncratic way) that it isn't
> going to monitor it.
> 

Thank you very much !! One less mistery in my life ;)

--
J.A. Magallon <jamagallon()able!es>     \               Software is like sex:
werewolf!able!es                         \         It's better when it's free
Mandrakelinux release 10.2 (Limited Edition 2005) for i586
Linux 2.6.11-jam14 (gcc 3.4.3 (Mandrakelinux 10.2 3.4.3-7mdk)) #3



      reply	other threads:[~2005-04-12 22:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12 20:45 J.A. Magallon
2005-04-12 21:55 ` Neil Brown
2005-04-12 22:08   ` J.A. Magallon [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=1113343703l.9659l.0l@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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®