linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Sven Hartrumpf <hartrumpf@gmx.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Using a newer mdadm version just for re-adding a device
Date: Mon, 4 Jun 2012 14:15:50 +1000	[thread overview]
Message-ID: <20120604141550.7db5cd4e@notabene.brown> (raw)
In-Reply-To: <20120531.192414.2085541500628127947.hartrumpf@gmx.net>

[-- Attachment #1: Type: text/plain, Size: 986 bytes --]

On Thu, 31 May 2012 19:24:14 +0200 (CEST) Sven Hartrumpf <hartrumpf@gmx.net>
wrote:

> To answer my own question (about a RAID-1):
> 
> Wed, 30 May 2012 19:38:15 +0200 (CEST), I wrote:
> > Is it safe to mix mdadm versions in the following scenario?
> ...
> > Now my question is:
> > Can I safely use the resulting binary (renamed to mdadm325 to avoid confusion)
> > to re-add the device and then continue to use the 3.2.2 package from openSUSE?
> 
> I made a backup and tried the above: it worked perfectly.

I like it when people work out the answer themselves :-)

The only possible issue is that when 3.2.5 adds a new device it will try to
give it a larger "Data Offset".  This won't confuse md, but it might confuse
you in later life.

About the only time you need to ensure you have a consistent version of mdadm
is when re-creating an array that died in some way and you want to recover
the data off it, but "-assemble --force" doesn't work.

NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2012-06-04  4:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30 17:38 Using a newer mdadm version just for re-adding a device Sven Hartrumpf
2012-05-31 17:24 ` Sven Hartrumpf
2012-06-04  4:15   ` NeilBrown [this message]

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=20120604141550.7db5cd4e@notabene.brown \
    --to=neilb@suse.de \
    --cc=hartrumpf@gmx.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).