All of lore.kernel.org
 help / color / mirror / Atom feed
From: "GeneralNMX" <generalmx@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Raid starts dirty every boot on Ubuntu
Date: Sun, 1 Feb 2009 12:23:16 -0500	[thread overview]
Message-ID: <004101c98491$c575dd10$50619730$@com> (raw)
In-Reply-To: 


On my Ubuntu server, ALL my raids start dirty every single time and kicks
one drive (any one of the four), re-adds it, then reconstructs the raid
array. For the example below, this is a raid1 with two spares.  When it
finishes booting, the device that was kicked is still in the array, as a
spare. This makes the boot literally take hours, and I don’t know exactly
what it’s doing since it just sits there without a progress indicator. I
don’t think it’s fsck because it doesn’t even get to fsck yet in the
runlevel. It goes like this:

md: md7 stopped.
md: unbind<sda9>
md: export_rdev(sda9)
md: ubind<sdb9>
md: export_rdev(sdb9)
md: bind<sdc9>
md: bind<sdb9>
md: bind<sdd9>
md: bind<sda9>
md: Kicking non-fresh sdd9 from array!
md: unbind<sdd9>
md: export_rdev(sdd9)
raid1: raid set md7 active with 2 out of 2 mirrors


--
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

                 reply	other threads:[~2009-02-01 17:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='004101c98491$c575dd10$50619730$@com' \
    --to=generalmx@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.