From: "Leslie Rhorer" <lrhorer@satx.rr.com>
To: 'Linux RAID' <linux-raid@vger.kernel.org>
Subject: Temporarily Disable Array
Date: Fri, 4 Feb 2011 22:44:12 -0600 [thread overview]
Message-ID: <CC.BC.19545.0A5DC4D4@cdptpa-omtalb.mail.rr.com> (raw)
In a few days, I am going to be upgrading Linux on one of my servers
from Debian "Lenny" to "Squeeze". I've gone through this upgrade a handful
of times, and it can be pretty tricky. It would be best if the data array
were not assembled over and over again during the process. I know it really
shouldn't make a difference, but in the real world stability issues have
raised their ugly heads more than once causing additional time and heartache
associated with the array to be required to complete the task. With this in
mind, I would like to temporarily disable the assembly of the array until
the upgrade is complete and the system stable. Do I have the following
checklist correct, or is there something wrong or missing? Are there better
alternatives? I'm not missing something about the "homehost" utility, am I?
1. Edit /etc/mdadm/mdadm.conf and comment out the line specifying the
array. Also comment out the line "HOMEHOST <system>"
2. Edit /etc/fstab and comment out the line specifying the mount point for
the array.
3. Issue the command `update-initramfs -u`
4. Reboot the system, making sure the array does not assemble.
5. Perform the OS upgrade.
6. Edit mdadm.conf and fstab, removing the comment markers placed in steps
1 and 2.
7. Issue the command `update-initramfs -u`
8. Reboot the system, making sure the array assembles and mounts.
next reply other threads:[~2011-02-05 4:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 4:44 Leslie Rhorer [this message]
[not found] <AANLkTiktOdqq5Y3OWvU5dusDy+t_guEo88jm=DN-HnR8@mail.gmail.com>
2011-02-08 0:14 ` Temporarily Disable Array Leslie Rhorer
2011-02-09 19:08 ` hansbkk
2011-02-10 0:37 ` Leslie Rhorer
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=CC.BC.19545.0A5DC4D4@cdptpa-omtalb.mail.rr.com \
--to=lrhorer@satx.rr.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;
as well as URLs for NNTP newsgroup(s).