mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: WANG Chao <chaowang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: lvm thin_* binaries are installed in hostonly mode?
Date: Wed, 4 Dec 2013 22:05:17 +0800	[thread overview]
Message-ID: <20131204140517.GD3430@dhcp-17-89.nay.redhat.com> (raw)

Hi, Harald

I notice these thin_* binaries are installed to kdump initramfs in spite
of the fact that I don't use thinp lvm:

# ll sbin/thin_*
-rwxr-xr-x. 1 root root  384648 Dec  4 20:37 sbin/thin_check
-rwxr-xr-x. 1 root root 2184112 Dec  4 20:37 sbin/thin_dump
-rwxr-xr-x. 1 root root 2179792 Dec  4 20:37 sbin/thin_repair
-rwxr-xr-x. 1 root root 2179928 Dec  4 20:37 sbin/thin_restore

This is introduced here:

commit 5d623b1
Author: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date:   Mon Oct 21 09:09:26 2013 +0200

    lvm: always install thin utils for lvm


These binaries are totally 6.6M in size. That's too much for a kdump
environment.

As you probably know, in kdump kernel, we only have very limited memory
(~128M) and makedumpfile (a vmcore dump tool) is more faster if there's
more available memory out there.

IMO, it's best we only install these thin_* bins when people are
actually using these ones.

Anyway, I don't know if you have any particular reason to do this..


Thanks
WANG Chao

             reply	other threads:[~2013-12-04 14:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04 14:05 WANG Chao [this message]
     [not found] ` <20131204140517.GD3430-2coKmSd1Zb6BYdNaKHuJJRcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
2013-12-04 15:20   ` lvm thin_* binaries are installed in hostonly mode? Vivek Goyal
     [not found]     ` <20131204152011.GB15680-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-12-11 11:05       ` WANG Chao

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=20131204140517.GD3430@dhcp-17-89.nay.redhat.com \
    --to=chaowang-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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