From: Phil Turmel <philip@turmel.org>
To: Mark Knecht <markknecht@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Any risk switching mdadm to static?
Date: Wed, 26 Dec 2012 14:53:33 -0500 [thread overview]
Message-ID: <50DB55BD.2040208@turmel.org> (raw)
In-Reply-To: <CAK2H+ecQpTtipdPWQmVj2gCZ6FPzeXfx5bj8y4asVdhf1CTkfA@mail.gmail.com>
On 12/26/2012 02:28 PM, Mark Knecht wrote:
> On Wed, Dec 26, 2012 at 11:02 AM, Phil Turmel <philip@turmel.org> wrote:
[trim /]
>> I can't answer the question off the top, but I thought I'd point out
>> that you probably don't need static for use with an initramfs. Because
>> I run stable amd64 on one of my gentoo servers, and don't have 'static'
>> set for mdadm. I use dracut with mdraid and lvm use flags to build my
>> initramfs images. Rootfs is in LVM which is on MD raid10.
>
> OK, that's good to know. I'm not currently using dracut as I'd like to go
> through the process once or twice by hand as I learn, and maybe I'm
> overreacting to what I'm seeing here. It's my understanding that the
> purpose of the static flag is to build into the mdadm binary any libraries
> that would normally be loaded dynamically. Is that correct?
Yes.
> c2stable ~ # ldd /sbin/mdadm
> linux-vdso.so.1 (0x00007fff735e3000)
> libc.so.6 => /lib64/libc.so.6 (0x00007f81a31e6000)
> /lib64/ld-linux-x86-64.so.2 (0x00007f81a3591000)
> c2stable ~ #
Mine is effective identical (slight offset differences, as expected for
custom-compiled systems). Dracut put these libraries in my initramfs.
> So the above is for NOT static case. My concern is about
> whether I have to put these libraries in my initramfs image
> by hand, or said another way, if I build static then are these
> libraries completely linked in and carried along with the
> mdadm binary?
Yes, as you've since demonstrated.
>> From my understanding of how linking works, I'd say it *can't* hurt.
>>
>
> That's my general feeling also, but I'm just trying to be both extra
> careful as well as learn something.
>
> Thanks for the response!
You're welcome.
Phil
next prev parent reply other threads:[~2012-12-26 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-26 17:57 Any risk switching mdadm to static? Mark Knecht
2012-12-26 19:02 ` Phil Turmel
[not found] ` <CAK2H+ecQpTtipdPWQmVj2gCZ6FPzeXfx5bj8y4asVdhf1CTkfA@mail.gmail.com>
2012-12-26 19:53 ` Phil Turmel [this message]
2012-12-26 19:32 ` Tommy Apel Hansen
[not found] ` <CAK2H+efpHB-Okn_PaitAKmLPKwmn1kNZzJpEvM-BW7fWWwrZVw@mail.gmail.com>
2012-12-26 19:55 ` Tommy Apel Hansen
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=50DB55BD.2040208@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=markknecht@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).