From: Friedrich Lobenstock <fl@fl.priv.at>
To: Linux RAID Mailing Liste <linux-raid@vger.kernel.org>
Subject: [BUG?] count of "Spare Devices" wrong after fail/remove/add
Date: Tue, 21 Jan 2003 02:20:04 +0100 [thread overview]
Message-ID: <3E2CA044.5030202@fl.priv.at> (raw)
Hi!
While experimenting with fail/remove/add of mdadm
# mdadm --detail /dev/md0
/dev/md0:
Version : 00.90.00
Creation Time : Mon Jan 20 22:53:28 2003
Raid Level : raid1
Array Size : 40209024 (38.35 GiB 41.22 GB)
Device Size : 40209024 (38.35 GiB 41.22 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Tue Jan 21 00:49:47 2003
State : dirty, no-errors
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 2
Number Major Minor RaidDevice State
0 3 1 0 active sync /dev/hda1
1 22 1 1 active sync /dev/hdc1
UUID : d876333b:694e852b:e9a6f40f:0beb90f9
I do wounder why I've got 2 spare drives despite the fact that I
did not add any. I've just got two drives in this raid1 that's it.
Kernel is 2.4.19.
mdadm is 1.0.1
I tried to reproduce this by recreating the array and running
fail/remove/add on it but did not succeed. No reboot.
PS: Array Size : 40209024 (38.35 GiB 41.22 GB)
should IMHO be
Array Size : 40209024 (38.35 GiB 40.21 GB)
--
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock FL226-RIPE Internetservices
URL: http://www.fl.priv.at/ Email: fl@fl.priv.at
____________________________________________________________________
next reply other threads:[~2003-01-21 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 1:20 Friedrich Lobenstock [this message]
2003-01-22 4:23 ` [BUG?] count of "Spare Devices" wrong after fail/remove/add Neil Brown
2003-01-22 8:46 ` Friedrich Lobenstock
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=3E2CA044.5030202@fl.priv.at \
--to=fl@fl.priv.at \
--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).