From: Michael Evans <mjevans1983@gmail.com>
To: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Device role question
Date: Sat, 27 Feb 2010 19:34:33 -0800 [thread overview]
Message-ID: <4877c76c1002271934m3db22c7ahc93d3d4129df7d22@mail.gmail.com> (raw)
In-Reply-To: <20100227091027.GA3510@lazy.lzy>
On Sat, Feb 27, 2010 at 1:10 AM, Piergiorgio Sartor
<piergiorgio.sartor@nexgo.de> wrote:
> Hi,
>
>> Ok, please run this for each disk in the array:
>>
>> mdadm --examine /dev/(DEVICE)
>>
>> The output would be most readable if you did each array's devices in
>> order, and you can list them on the same command (- - examine takes
>> multiple inputs)
>>
>> If you still think the situation isn't as I described above, post the results.
>
> Well, here it is:
>
> $> mdadm -E /dev/sd[ab]2
> /dev/sda2:
> Magic : a92b4efc
> Version : 1.1
> Feature Map : 0x1
> Array UUID : 54db81a7:b47e9253:7291055e:4953c163
> Name : lvm
> Creation Time : Fri Feb 6 20:17:13 2009
> Raid Level : raid10
> Raid Devices : 2
>
> Avail Dev Size : 624928236 (297.99 GiB 319.96 GB)
> Array Size : 624928000 (297.99 GiB 319.96 GB)
> Used Dev Size : 624928000 (297.99 GiB 319.96 GB)
> Data Offset : 264 sectors
> Super Offset : 0 sectors
> State : clean
> Device UUID : 8f6cd2c4:0efc8286:09ec91c6:bc5014bf
>
> Internal Bitmap : 8 sectors from superblock
> Update Time : Sat Feb 27 10:08:22 2010
> Checksum : 1703ded0 - correct
> Events : 161646
>
> Layout : far=2
> Chunk Size : 64K
>
> Device Role : spare
> Array State : AA ('A' == active, '.' == missing)
> /dev/sdb2:
> Magic : a92b4efc
> Version : 1.1
> Feature Map : 0x1
> Array UUID : 54db81a7:b47e9253:7291055e:4953c163
> Name : lvm
> Creation Time : Fri Feb 6 20:17:13 2009
> Raid Level : raid10
> Raid Devices : 2
>
> Avail Dev Size : 624928236 (297.99 GiB 319.96 GB)
> Array Size : 624928000 (297.99 GiB 319.96 GB)
> Used Dev Size : 624928000 (297.99 GiB 319.96 GB)
> Data Offset : 264 sectors
> Super Offset : 0 sectors
> State : clean
> Device UUID : 6e2763b5:9415b181:e41a9964:b0c21ca6
>
> Internal Bitmap : 8 sectors from superblock
> Update Time : Sat Feb 27 10:08:22 2010
> Checksum : 87d25401 - correct
> Events : 161646
>
> Layout : far=2
> Chunk Size : 64K
>
> Device Role : Active device 0
> Array State : AA ('A' == active, '.' == missing)
>
> And the details too:
>
> $> mdadm -D /dev/md1
> /dev/md1:
> Version : 1.1
> Creation Time : Fri Feb 6 20:17:13 2009
> Raid Level : raid10
> Array Size : 312464000 (297.99 GiB 319.96 GB)
> Used Dev Size : 312464000 (297.99 GiB 319.96 GB)
> Raid Devices : 2
> Total Devices : 2
> Persistence : Superblock is persistent
>
> Intent Bitmap : Internal
>
> Update Time : Sat Feb 27 10:09:24 2010
> State : active
> Active Devices : 2
> Working Devices : 2
> Failed Devices : 0
> Spare Devices : 0
>
> Layout : far=2
> Chunk Size : 64K
>
> Name : lvm
> UUID : 54db81a7:b47e9253:7291055e:4953c163
> Events : 161646
>
> Number Major Minor RaidDevice State
> 0 8 18 0 active sync /dev/sdb2
> 2 8 2 1 active sync /dev/sda2
>
> bye,
>
> --
>
> piergiorgio
>
I've checked my arrays and my only RAID-10 array has a single spare
(hot spare) as part of the set with several other members. All
current members storing DATA are listed as active members.
What's confusing is that /proc/mdadm lists it as an active member
(synced to data) but that the device does not match. Maybe you can
stop/restart the array?
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-02-28 3:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 14:23 Device role question Piergiorgio Sartor
2010-02-27 5:56 ` Michael Evans
2010-02-27 8:08 ` Piergiorgio Sartor
2010-02-27 8:55 ` Michael Evans
2010-02-27 9:10 ` Piergiorgio Sartor
2010-02-28 3:34 ` Michael Evans [this message]
2010-02-28 10:38 ` Piergiorgio Sartor
2010-02-28 4:41 ` Neil Brown
2010-02-28 10:35 ` Piergiorgio Sartor
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=4877c76c1002271934m3db22c7ahc93d3d4129df7d22@mail.gmail.com \
--to=mjevans1983@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=piergiorgio.sartor@nexgo.de \
/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).