linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Nikolay Kichukov <hijacker@oldum.net>
Cc: linux RAID <linux-raid@vger.kernel.org>
Subject: Re: create raid10 md raid which hangs on auto-read-only with resync=PENDING
Date: Fri, 4 May 2012 07:23:39 +1000	[thread overview]
Message-ID: <20120504072339.7742201e@notabene.brown> (raw)
In-Reply-To: <4FA24A31.3020703@oldum.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 03 May 2012 12:04:49 +0300 Nikolay Kichukov <hijacker@oldum.net>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi all,
> I have recently included one more drive in my system and has switched from raid0 to raid10 on 3 devices/partitions.
> 
> I have created the raid as follows:
> 
> mdadm --create /dev/md3 --verbose --raid-devices=3 --level=raid10 --name=cryptdata  --layout=o2 --chunk=2M /dev/sda3
> /dev/sdb3 /dev/sdf3
> mdadm: size set to 319434752K
> mdadm: Defaulting to version 1.2 metadata
> mdadm: array /dev/md3 started.
> 
> 
> Information about the array:
> 
> mdadm --detail /dev/md3
> /dev/md3:
>         Version : 1.2
>   Creation Time : Thu May  3 11:42:57 2012
>      Raid Level : raid10
>      Array Size : 479152128 (456.96 GiB 490.65 GB)
>   Used Dev Size : 319434752 (304.64 GiB 327.10 GB)
>    Raid Devices : 3
>   Total Devices : 3
>     Persistence : Superblock is persistent
> 
>     Update Time : Thu May  3 11:42:57 2012
>           State : clean, resyncing (PENDING)
>  Active Devices : 3
> Working Devices : 3
>  Failed Devices : 0
>   Spare Devices : 0
> 
>          Layout : offset=2
>      Chunk Size : 2048K
> 
>            Name : hanna64:cryptdata  (local to host hanna64)
>            UUID : a7cc8eb7:8555b1bd:2856b686:829861be
>          Events : 0
> 
>     Number   Major   Minor   RaidDevice State
>        0       8        3        0      active sync   /dev/sda3
>        1       8       19        1      active sync   /dev/sdb3
>        2       8       83        2      active sync   /dev/sdf3
> 
> 
> And under /proc/mdstat:
> 
> cat /proc/mdstat
> Personalities : [raid0] [raid1] [raid10]
> md3 : active (auto-read-only) raid10 sdf3[2] sdb3[1] sda3[0]
>       479152128 blocks super 1.2 2048K chunks 2 offset-copies [3/3] [UUU]
>       	resync=PENDING
> 
> 
> The resync was not started due to the array being in auto-read-only mode.
> 
> I googled the issue and found out that to be able to start the resync one should issue:
> 
> mdadm --readwrite /dev/mdx
> (ref.: http://wiki.xtronics.com/index.php/Raid )
> 
> I have done it and it started resyncing:
> cat /proc/mdstat
> Personalities : [raid0] [raid1] [raid10]
> md3 : active raid10 sdf3[2] sdb3[1] sda3[0]
>       479152128 blocks super 1.2 2048K chunks 2 offset-copies [3/3] [UUU]
>       [=>...................]  resync =  6.2% (29748096/479152128) finish=120.3min speed=62220K/sec
> 
> 
> 
> Is this intended feature for 1.2 metadata?

This behaviour isn't a function of 1.2 metadata.
It is a function of  /sys/module/md_mod/parameters/start_ro which
is probably being setting by Debian early in boot because that can be a very
sensible thing to do.

I should probably get --create to over-ride it (I thought I had, but
obviously not).

If you write '0' to it, you'll find that the array starts normally.

Alternately, just start using the array.  As soon as you "mkfs", the array
will start resyncing.

NeilBrown


> 
> Kernel: 3.1.0-1-amd64
> mdadm: 3.2.3-2
> Distro: Debian testing
> 
> Cheers,
> - -Nik
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iQEcBAEBAgAGBQJPokoxAAoJEDFLYVOGGjgXb3cH/2cnkl+Q0q+vA+8z32XQwD28
> dnpohM0nlQe99in2D1fjkI0Bsnt3tYz0bjZALHxOPybEWH+U3X1WOztTx/UdfKmL
> fXTv8hFLscIsdvOK/JThkRdob99EEPbkZlnzCuTrIQDPJSj1v/kY7AG/9HxLCnT+
> 8KDZpkEyd9usSQZC/sUie2B/cG5VDir74sFc/ggr3UsZCFtBGPJuILCjlWAu6XcH
> SCV2FTvJt/Ahay3/IuzBvNRBys7OcOFKck/oGGgW2Ki5FUeehWGWbWVbYEiQ4pZR
> TPbPwrY84v6OS2Baqm8kZIr8j6UPFzPuErxGqhxq7e+btGx8aKklzbJn3dQCQck=
> =IVpx
> -----END PGP SIGNATURE-----
> --
> 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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iQIVAwUBT6L3Wznsnt1WYoG5AQJrtxAAvpXk/Gx4Q3vRqk+zsi99qCv8txV96m74
Ace6+FWleF8Uv31f59lK4Asm43CYzSaNrtI/x6NkW/6sLpyHOP6o421r5rgyAB3h
UjWkRDGhct2/ONcADuwb92eERvlhnMRRe3wBtX1zlyipghFqpn8Sm2nTZ5sSJMsj
ZZPSL9v80EfY0FKeyyTZoEo2gx5CBHAy2HCqNjMaU/KC4FIp+7uG9a9IklfORSnI
bHfmhp4hDZdgmX5KLHvX9nvY/etxaaKEl+GJGDRxe1Vm+/qdbJR+Y/0TdGEla+/q
zxs7YBT5jrSvnQo0mnwdR3ssfEQcnlUvsW7XSjmSgNSpRxp6Rp+LfkOn5seLEO4e
RLhEADnu+4u2Z2F6lOmcJpyP0f3AK40YuQvYYbWt3o/BmaaQ5Zw+N8SbBjjO0fyM
k/z6xFsxeqtF/fjFGIGWPFjPQxnTlB9XpJ54TGqi8M3C7kmJr0Zmq35+uN282Oyw
IDSs4qxqjB4riVyFkSQ4s2epknjXvOxPH9qirv2B7PolJtEtWSjv29phiMuoDxgM
3c59AAll2D8ulPsvt2sNS0DQ9Ola4oAqE9IjJPwwHfOU07Ji1MQLqm+a6zVAtO5g
2nq6NR+clSPV+meJp5Xb6G+KoHPTkJXPNS1h7KfHtOQyy/rxuz3lW68X55+iGWTe
OhwoUZUoWjA=
=e5x+
-----END PGP SIGNATURE-----

  reply	other threads:[~2012-05-03 21:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03  9:04 create raid10 md raid which hangs on auto-read-only with resync=PENDING Nikolay Kichukov
2012-05-03 21:23 ` NeilBrown [this message]
2012-05-08 14:16   ` Nikolay Kichukov

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=20120504072339.7742201e@notabene.brown \
    --to=neilb@suse.de \
    --cc=hijacker@oldum.net \
    --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).