From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: Michael Evans <mjevans1983@gmail.com>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
linux-raid@vger.kernel.org
Subject: Re: metadata 1.2
Date: Sat, 27 Mar 2010 10:47:13 +0100 [thread overview]
Message-ID: <20100327094713.GA2537@lazy.lzy> (raw)
In-Reply-To: <4877c76c1003270231j58767878w77886a1226fa33a2@mail.gmail.com>
Hi,
> I forget the commands, but the key thing for grub2 is stuffing all of
> the modules you need in to a single loadable image, and invoking the
> grub2 install command to embed THAT image. It's then supposed to
exactly, THAT image is 28K and grub-install complains
there is no space, basically...
Actually, the complain is different, but the meaning
is that grub2 cannot do it.
The problem is grub2 wants to have its own things
outside the filesystem/lvm/raid containers.
Which is OK, but it requires also space somewhere
in the disk.
Standard option is to use the 32K left by tools
like fdisk, which put the beginning of the first
partition, by default, at sector 63.
Of course it is a bit silly to have a single
partition on a disk just to leave 32K free for
the bootmanager.
Not that this makes any damage, but it would be
more clean, i.e. less tools to deal with, to
avoid the partitioning completely.
This would require enough space for the bootmanager
to put its stuff.
That's why I was surprised that 1.2 leaves *only* 4K
without, apparently, any chance of having more space.
> In any event, the 4k offset code is still useful for raid 1 arrays,
How about changing it to something else?
Thanks,
bye,
--
piergiorgio
next prev parent reply other threads:[~2010-03-27 9:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 19:43 metadata 1.2 Piergiorgio Sartor
2010-03-27 1:49 ` Michael Evans
2010-03-27 9:16 ` Piergiorgio Sartor
2010-03-27 9:31 ` Michael Evans
2010-03-27 9:47 ` Piergiorgio Sartor [this message]
2010-03-27 21:10 ` Michael Evans
2010-03-28 7:20 ` Piergiorgio Sartor
2010-03-28 6:58 ` Luca Berra
2010-03-28 7:22 ` Piergiorgio Sartor
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=20100327094713.GA2537@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--cc=linux-raid@vger.kernel.org \
--cc=mjevans1983@gmail.com \
/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).