From: "J.A. Magallon" <jamagallon@able.es>
To: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: RAID0: WrongLevel ?
Date: Tue, 26 Oct 2004 22:17:55 +0000 [thread overview]
Message-ID: <1098829075l.6518l.1l@werewolf.able.es> (raw)
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 ?
Boot info:
md: Autodetecting RAID arrays.
md: autorun ...
md: considering hdd1 ...
md: adding hdd1 ...
md: adding hdc1 ...
md: adding hda1 ...
md: created md0
md: bind<hda1>
md: bind<hdc1>
md: bind<hdd1>
md: running: <hdd1><hdc1><hda1>
md0: setting max_sectors to 128, segment boundary to 32767
raid0: looking at hdd1
raid0: comparing hdd1(117218176) with hdd1(117218176)
raid0: END
raid0: ==> UNIQUE
raid0: 1 zones
raid0: looking at hdc1
raid0: comparing hdc1(117218176) with hdd1(117218176)
raid0: EQUAL
raid0: looking at hda1
raid0: comparing hda1(245111616) with hdd1(117218176)
raid0: NOT EQUAL
raid0: comparing hda1(245111616) with hdc1(117218176)
raid0: NOT EQUAL
raid0: comparing hda1(245111616) with hda1(245111616)
raid0: END
raid0: ==> UNIQUE
raid0: 2 zones
raid0: FINAL 2 zones
raid0: zone 1
raid0: checking hda1 ... contained as device 0
(245111616) is smallest!.
raid0: checking hdc1 ... nope.
raid0: checking hdd1 ... nope.
raid0: zone->nb_dev: 1, size: 127893440
raid0: current zone offset: 245111616
raid0: done.
raid0 : md_size is 479547968 blocks.
raid0 : conf->hash_spacing is 351654528 blocks.
raid0 : nb_zone is 2.
raid0 : Allocating 8 bytes for hash.
md: ... autorun DONE.
Runtime info:
annwn:~# cat /proc/partitions
major minor #blocks name
3 0 245117376 hda
3 1 245111706 hda1
22 0 117220824 hdc
22 1 117218241 hdc1
22 64 117220824 hdd
22 65 117218241 hdd1
annwn:~# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid5] [multipath] [raid6]
md0 : active raid0 hdd1[2] hdc1[1] hda1[0]
479547968 blocks 64k chunks
unused devices: <none>
annwn:~# mdadm -D /dev/md0
/dev/md0:
Version : 00.90.01
Creation Time : Mon Sep 13 17:57:08 2004
Raid Level : raid0
Array Size : 479547968 (457.33 GiB 491.06 GB)
Raid Devices : 3
Total Devices : 3
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Mon Sep 13 17:57:08 2004
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Chunk Size : 64K
UUID : c7c5ec26:ae5a99f9:49fec7a1:7e0dcc69
Events : 0.12
Number Major Minor RaidDevice State
0 3 1 0 active sync /dev/hda1
1 22 1 1 active sync /dev/hdc1
2 22 65 2 active sync /dev/hdd1
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrakelinux release 10.1 (Community) for i586
Linux 2.6.9-jam1 (gcc 3.4.1 (Mandrakelinux 10.1 3.4.1-4mdk)) #4
reply other threads:[~2004-10-26 22:18 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=1098829075l.6518l.1l@werewolf.able.es \
--to=jamagallon@able.es \
--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®