How come the initrd cpio archives are so large?

[Yuval Turgeman]

You're only seeing the early microcode, to see the full content try

/usr/lib/dracut/skipcpio initrd | gzip -d -| cpio -divu


On Mon, Jan 21, 2019 at 12:48 PM Shlomi Fish <shlomif at gmail.com> wrote:

> Hi all!
>
> root at telaviv1:~/initrd/good/unpack # ls -l ../img
> -rw------- 1 root root 11419609 Jan 21 11:42 ../img
> root at telaviv1:~/initrd/good/unpack # cpio -i  < ../img
> 26 blocks
> root at telaviv1:~/initrd/good/unpack # du .
> 16K     ./kernel/x86/microcode
> 20K     ./kernel/x86
> 24K     ./kernel
> 32K     .
> root at telaviv1:~/initrd/good/unpack #
>
>
> ==> why is the initrd cpio image so large in comparison to its contents?
>
> I am trying to debug this kernel bootup problem -
> https://bugs.mageia.org/show_bug.cgi?id=24203 - it happens with all
> kernels I tried - compiled from source or not except for those that were
> prepared in the past. Any help would be appreciated.
>
> --
> Shlomi Fish http://www.shlomifish.org/
>
> Buddha has the Chuck Norris nature.
>
> Please reply to list if it's a mailing list post - http://shlom.in/reply .
> _______________________________________________
> Linux-il mailing list
> Linux-il at cs.huji.ac.il
> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cs.huji.ac.il/pipermail/linux-il/attachments/20190318/389aa60e/attachment.html>