linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: "David C. Rankin" <drankinatty@suddenlinkmail.com>
Cc: mdraid <linux-raid@vger.kernel.org>
Subject: Re: Raid1 where Event Count off my 1 cannot assemble --force
Date: Mon, 9 Dec 2013 15:46:39 +1100	[thread overview]
Message-ID: <20131209154639.3b9f801c@notabene.brown> (raw)
In-Reply-To: <52A546DB.3090605@suddenlinkmail.com>

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

On Sun, 08 Dec 2013 22:28:11 -0600 "David C. Rankin"
<drankinatty@suddenlinkmail.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 12/08/2013 07:00 PM, NeilBrown wrote:
> > What version of mdadm do you have?  It looks like it should be cleverer than 
> > it is.
> > 
> > What if you add "--update=no-bitmap" to the --assemble line? As the bitmap
> > seems to be causing problem, ignoring it might help.
> > 
> > NeilBrown
> 
> I tried that too Neil, it said:
> 
> nemtemp:/mnt # mdadm --verbose --assemble --force --update=no-bitmap /dev/md1
> /dev/sd[ab]5
> mdadm: '--update=no-bitmap' is invalid.  Valid --update options are:
>      'sparc2.2', 'super-minor', 'uuid', 'name', 'resync',
>      'summaries', 'homehost', 'byteorder', 'devicesize'.
> 
> Like in my reply to Adam, I think the age of mdadm may be the issue. The
> openSuSE 11.0 install DVD is pretty old ;-) It just may not be handling the
> - --assemble correctly given the Event count difference, and there doesn't seem to
> be a way to just tell it:
> 
> "The data is correct on both disks, just assemble and run it and be quiet!"
> 
> I'll try booting an Arch install CD with 3.3.2 on it and report back. Thank you
> and Adam for your help.
> 
> If it does assemble with mdadm 3.3.2, anything I need to do on the assembled
> array to make sure it stays that way? fsck? Any way to tell it to make sure it
> is in sync so it will boot under the openSuSE 11.0 version of mdadm?
> 

Once you get any kernel to successfully assemble the array, any other
kernel/mdadm should be able to as well.

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

iQIVAwUBUqVLLznsnt1WYoG5AQJ5mg//UkmhkCAtbiCf7z+1X9i/HsoROqH3Dhn6
ii2GEkWcb+IL7tYJ3zp0uzXPJOAuU10SSF7Icrobp9ABnWsCHefEXgGt4kRB7dG8
VkIrYIEArmSkLXkRlSP76IWi2A/AZzhBC3/8QPVXVDBy2I93YHwbkIttzLJURc8R
/gtZRX7Bli4FgdNQuRj9K3KLc7Rar+CG1PmzLSInv3bXhZKM2JjlT2Wz4C0niBrf
0topMmjTrVESf8qT2QlOAvhN8BPNtWR95/H6W+v0nKU1KnyOuo6hwolqOFmspyJv
Hrn2PFdNKmYFfQ+rFOMZQk4mxII9OxLp5bidE7r4jedzyhQi6QKDLcXZc550irxI
e2vGu1Yg+V8d6dcRYgePChDIJn0c13iYgxZHxOJ4I1uhwC9dHNwgN8v377nkfZi+
wBml7Do2oynzImeCC7FVBnYrjmJm1M5djUqB12dIvQZySfI/SUMIVLPNyupiaSvb
xvZ/QzoJaowYo1a0lt5EmWAVD5FZ/YTjiffxCdRr/P1rVWfc7Jx2KE/i42heXo8e
zBU51hBrWI3JVLYMQr4/Rc1NYXtE51Cq0QzzM5dlnb+ya1m2boscYyUCZHjMGsJg
9JUnT6u7U8a676SZqCCUudIVPFxIR+xyhgpw0AmHcpfMdJ18ic/NmWXIQR7j+jka
e5LiyQVu5nw=
=nGpK
-----END PGP SIGNATURE-----

  reply	other threads:[~2013-12-09  4:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-08 10:18 Raid1 where Event Count off my 1 cannot assemble --force David C. Rankin
2013-12-08 10:57 ` Mikael Abrahamsson
2013-12-08 17:57   ` David C. Rankin
2013-12-09  0:38     ` David C. Rankin
2013-12-09  0:52       ` Adam Goryachev
2013-12-09  2:38         ` David C. Rankin
2013-12-09  3:12           ` Adam Goryachev
2013-12-09  3:40             ` David C. Rankin
2013-12-09  1:00       ` NeilBrown
2013-12-09  4:28         ` David C. Rankin
2013-12-09  4:46           ` NeilBrown [this message]
2013-12-09  5:20             ` [SOLVED] " David C. Rankin
2013-12-09  5:40               ` NeilBrown
2013-12-09  7:40                 ` Mikael Abrahamsson
2013-12-09 21:28                   ` David C. Rankin

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=20131209154639.3b9f801c@notabene.brown \
    --to=neilb@suse.de \
    --cc=drankinatty@suddenlinkmail.com \
    --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).