From: John McNulty <johnmcn1@googlemail.com>
To: linux-raid@vger.kernel.org
Subject: Re: What will happen with spares in this scenario?
Date: Mon, 29 Jun 2009 22:07:57 +0100 [thread overview]
Message-ID: <9A9AF670-B7EF-4E91-984D-445374CEFA82@googlemail.com> (raw)
In-Reply-To: <87zlbruinb.fsf@frosties.localdomain>
On 29 Jun 2009, at 17:08, Goswin von Brederlow wrote:
> So drop md1, make c0d0p1 as big as the others and then partition
> md0 eigther directly or via lvm.
You wouldn't happen to know if it's possible to create a partitionable
array like this in Kickstart would you? I've had a sniff around
Redhat's docs and a documented way of doing this isn't jumping out at
me. If I had to guess then it might look something like this?
part pv.1 --size 1 --ondisk cciss/c0d0 --grow --asprimary
part pv.2 --size 1 --ondisk cciss/c1d0 --grow --asprimary
raid pv.3 --level=RAID1 --device=md_d0 pv.1 pv.2
part /boot --fstype ext3 --size 300 --ondisk md_d0
part pv.4 --fstype "physical volume (LVM) --size 1 --ondisk md_d0 --grow
volgroup system --pesize=32768 pv.4
logvol / --fstype ext3 --name=root --vgname=system --size=51200
logvol swap --fstype swap --name=swap --vgname=system --size=8192
This might be a bit ambitious, and I can't see an option to "raid"
that would tell it to create a partitionable raid device, i.e. run --
auto=mdp behind the scenes. Unless it takes a hint from the device
name and does that without asking?
The systems I'm working on are to be kickstarted from a Spacewalk
server.
Rgds,
John
next prev parent reply other threads:[~2009-06-29 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 15:28 What will happen with spares in this scenario? John McNulty
2009-06-29 16:08 ` Goswin von Brederlow
2009-06-29 21:07 ` John McNulty [this message]
[not found] ` <BD450977-FA0D-4F63-8ADB-1314FA43E654@googlemail.com>
2009-06-30 4:26 ` Goswin von Brederlow
2009-06-30 8:16 ` John McNulty
2009-06-30 17:54 ` Goswin von Brederlow
2009-06-30 20:47 ` John McNulty
2009-07-01 6:57 ` Goswin von Brederlow
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=9A9AF670-B7EF-4E91-984D-445374CEFA82@googlemail.com \
--to=johnmcn1@googlemail.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