From: "Sebastian Färber" <faerber@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Prevent automatic reconstruction during boot/assembly (RAID 1)?
Date: Tue, 11 Aug 2009 14:28:26 +0200 [thread overview]
Message-ID: <2953e180908110528u705fc002m6c799821fe278375@mail.gmail.com> (raw)
Hi,
i'm trying to figure out if it is possible to prevent the
automatic reconstruction that can occur during the md assembly
at boot.
I'm running Kernel 2.6.30.4 and use a RAID-1 over two SATA disks.
If the server is rebooted "hard" due to power loss etc. it often happens
that the reconstruction of my RAID-1 is automatically triggered by the kernel.
Is there any way to prevent this? I want to re-add the "out of sync"
drive myself
using mdadm only.
I'm currently using raid auto detection (partiton type fd) and the old
0.90 superblock format but if it helps i would switch
to an initrd/newer superblock.
Thanks for your help!
Regards,
Sebastian
next reply other threads:[~2009-08-11 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 12:28 Sebastian Färber [this message]
2009-08-12 23:10 ` Prevent automatic reconstruction during boot/assembly (RAID 1)? Neil Brown
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=2953e180908110528u705fc002m6c799821fe278375@mail.gmail.com \
--to=faerber@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox