linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Jake Thomas <thomasj10@georgefox.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: Device Unusable At Startup
Date: Mon, 13 Aug 2012 10:20:20 +1000	[thread overview]
Message-ID: <20120813102020.172d3a93@notabene.brown> (raw)
In-Reply-To: <CACO8viqZO9bbdYtZMT3E0oMfWUjAzps1uNq7rBm419eXtt6bCg@mail.gmail.com>

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

On Sun, 12 Aug 2012 16:59:25 -0700 Jake Thomas <thomasj10@georgefox.edu>
wrote:

> sudo mdadm --create /dev/answers --level=1 --raid-devices=2
> /dev/blog,/dev/linux-raid@vger.kernel.org

;-)

> 
> Thanks for the responses Neil!
> 
>    I did try the following kernel parameter:
> 
> md-mod.start_dirty_degraded=1
> 
>    Does my kernel simply not honor that parameter? I'll try and look
> into my initial ramdisk and see some of these scripts you're talking
> about.

That parameter is for a different issue.  Starting a RAID5 or RAID6 when it
is dirty and degraded can cause data loss, so it is not done by default.

In your situation the array is not dirty and it isn't RAID5 or RAID6, so that
doesn't apply.

NeilBrown

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

  reply	other threads:[~2012-08-13  0:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-12 23:59 Device Unusable At Startup Jake Thomas
2012-08-13  0:20 ` NeilBrown [this message]
2012-08-13  6:45   ` Jake Thomas
2012-08-13  6:51     ` Jake Thomas
  -- strict thread matches above, loose matches on Subject: below --
2012-09-27 23:47 Jake Thomas
2012-09-28 11:11 ` Jan Ceuleers
2012-09-28 12:12   ` Jake Thomas
2012-09-28 16:24     ` Jan Ceuleers
2012-08-12 22:17 Jake Thomas
2012-08-12 22:39 ` NeilBrown
2012-08-05  7:13 Jake Thomas

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=20120813102020.172d3a93@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=thomasj10@georgefox.edu \
    /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).