linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Wesley W. Terpstra" <wesley@terpstra.ca>
To: Phil Turmel <philip@turmel.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: kernel refuses devices mdadm -E accepts
Date: Tue, 20 Jan 2015 19:32:50 +0100	[thread overview]
Message-ID: <CAA-O0XgV8NBSHxg9Q9RBLiASeCh_qCQLutc8_mg2Y2fwhWBOLA@mail.gmail.com> (raw)
In-Reply-To: <54BE9E47.9030706@turmel.org>

On Tue, Jan 20, 2015 at 7:28 PM, Phil Turmel <philip@turmel.org> wrote:
>> Kernel version 3.17.8 and mdadm version 3.3.2.
> There have been many bug fixes to mdadm since that kernel was retired.

Really? I will give that a shot.

> Show us the output of that if it doesn't work (it should resume your
> reshape).

I will try that.

It was totally stupid reshape, I was changing the "data-offset" to
align it. Really unnecessary, and really slow, so I feel like an idiot
for starting it.

>> Thanks for any help. If I lose this array, I am going to face a lot of grief...
> I shouldn't have to say this, but RAID is for availability, not for data
> security.  You still need a backup system for any important data.

Sure. The really vital (and small) stuff I have backed up elsewhere,
but the sheer volume of raw video my girlfriend records is not
economically feasible to backup beyond raid+btrfs snapshots.

      parent reply	other threads:[~2015-01-20 18:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 23:01 kernel refuses devices mdadm -E accepts Wesley W. Terpstra
2015-01-19 23:52 ` Roger Heflin
2015-01-20 18:28 ` Phil Turmel
2015-01-20 18:32   ` Phil Turmel
2015-01-20 18:43     ` Wesley W. Terpstra
     [not found]       ` <FCB084A5-816F-4954-971E-1C69C707F213@blub.net>
2015-01-21 12:37         ` Wesley W. Terpstra
2015-01-20 18:32   ` Wesley W. Terpstra [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=CAA-O0XgV8NBSHxg9Q9RBLiASeCh_qCQLutc8_mg2Y2fwhWBOLA@mail.gmail.com \
    --to=wesley@terpstra.ca \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.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).