[arch-general] mkinitcpio

Myra Nelson

2 Mar 2012 2 Mar '12

7:46 a.m.

I don't think this is significant enough to warrant a bug. Since the linux-3.2.6-1 kernel updates ( I don't remeber which version of mkinitcpio, sorry), I've been getting the following warning when mkinitcpio runs during the kernel install: cp: warning: source file `/lib/modules/3.2.9-1-ARCH/kernel/fs/ext4/ext4.ko.gz' specified more than once I originally thought it was due to my inclusion of the mkinitcpio-numlock hook from the AUR, but I have a fresh install on a new machine, without the numlock hook and get the same warning. I searched the bug tracker and found no reference to this. /usr is not mounted on a separte partition. my box HOOKS="base udev autodetect pata scsi sata filesystems usb usbinput fsck numlock" new box HOOKS="base udev autodetect pata scsi sata filesystems usb usbinput fsck" Since it's a warning not an error and doesn't appear to have any deliterious effects, it's not a problem. I just wondered if it's something I'm doing or if it's something in the hooks in mkinitcpio. Ciao for now Myra -- Life's fun when your sick and psychotic!

Show replies by date

Simon Perry

2 Mar 2 Mar

1:58 p.m.

On 02/03/12, Myra Nelson wrote: | I don't think this is significant enough to warrant a bug. Since the | linux-3.2.6-1 kernel updates ( I don't remeber which version of | mkinitcpio, sorry), I've been getting the following warning when | mkinitcpio runs during the kernel install: | | cp: warning: source file | `/lib/modules/3.2.9-1-ARCH/kernel/fs/ext4/ext4.ko.gz' specified more | than once I think it's a bug, but like you, I'm reluctant to call out things like this. I have removed ext4 from my MODULES line, and removed the filesystems hook in order to get rid of the dupe message. Unless some dev comes along and says "ext4 will always be in your initrd", I'm worried that this bug will be fixed then I'll rebuild, then I won't be able to boot because ext4 will be missing. Maybe I have the wrong idea here, but I never used to see this warning. -- Simon Perry (aka Pezz) [ s a n x i o n . n e t ]

Thomas Bächler

2:08 p.m.

Am 02.03.2012 14:58, schrieb Simon Perry:

...

I have removed ext4 from my MODULES line, and removed the filesystems hook in order to get rid of the dupe message.

If you don't have the filesystem hook, and you don't have ext4 it in MODULES, ext4 will be missing from the initramfs and you won't be able to boot.

Tom Gundersen

2:19 p.m.

On Mar 2, 2012 3:09 PM, "Thomas Bächler" wrote:

...

Am 02.03.2012 14:58, schrieb Simon Perry:

...
I have removed ext4 from my MODULES line, and removed the filesystems hook in order to get rid of the dupe message.

If you don't have the filesystem hook, and you don't have ext4 it in MODULES, ext4 will be missing from the initramfs and you won't be able to boot.

Unless you have ext2/3, as those are now aliases for ext4. Tom

Simon Perry

2:24 p.m.

On 02/03/12, Tom Gundersen wrote: | Unless you have ext2/3, as those are now aliases for ext4. Cheers, that explains it. Example: http://pastebin.com/f760JeFA So, in order to make things "nice", I should just use the filesystems hook, and not specify ext2 or ext4 in the modules line? -- Simon Perry (aka Pezz) [ s a n x i o n . n e t ]

Thomas Bächler

2:27 p.m.

Am 02.03.2012 15:24, schrieb Simon Perry:

...

On 02/03/12, Tom Gundersen wrote:

| Unless you have ext2/3, as those are now aliases for ext4.

Cheers, that explains it.

Example: http://pastebin.com/f760JeFA

So, in order to make things "nice", I should just use the filesystems hook, and not specify ext2 or ext4 in the modules line?

Actually, except for 'atl1', all those module specs are unnecessary.

Simon Perry

2:35 p.m.

On 02/03/12, Thomas Bächler wrote: | Actually, except for 'atl1', all those module specs are unnecessary. Booting is scary. If I take out all the modules except atl1, leave my hooks as is, and my machine doesn't boot after a mkinitcpio + reboot - will you buy me a slab of beer? ("Slab" is the Australian quantity for 24 beers) :) -- Simon Perry (aka Pezz) [ s a n x i o n . n e t ]

Thomas Bächler

2:40 p.m.

Am 02.03.2012 15:35, schrieb Simon Perry:

...

On 02/03/12, Thomas Bächler wrote:

| Actually, except for 'atl1', all those module specs are unnecessary.

Booting is scary.

If I take out all the modules except atl1, leave my hooks as is, and my machine doesn't boot after a mkinitcpio + reboot - will you buy me a slab of beer?

Actually no. But you can make a backup copy of your old initramfs-linux.img and compare lsinitcpio -a output for the old and new one.

Simon Perry

3:45 p.m.

On 02/03/12, Thomas Bächler wrote: | Actually no. But you can make a backup copy of your old | initramfs-linux.img and compare lsinitcpio -a output for the old and new | one. It's a lot of output to parse and diff accurately. Nevertheless, be glad you didn't bet (even though I provided no counter reward). I've just spent 20 minutes netbooting, mount raid / lvm / luks volumes, and getting ext4 back into my initrd. Filesystems hook is necessary if you want to leave MODULES bare. -- Simon Perry (aka Pezz) [ s a n x i o n . n e t ]

Thomas Bächler

3:54 p.m.

Am 02.03.2012 16:45, schrieb Simon Perry:

...

Filesystems hook is necessary if you want to leave MODULES bare.

Which I told you in my first reply.

Simon Perry

4:05 p.m.

On 02/03/12, Thomas Bächler wrote: | Which I told you in my first reply. Apologies for missing this after reading: "Actually, except for 'atl1', all those module specs are unnecessary." In the subsequent message... Not blaming you at all, but jesus - Captain Smug alert. -- Simon Perry (aka Pezz) [ s a n x i o n . n e t ]

C Anthony Risinger

3:55 p.m.

On Fri, Mar 2, 2012 at 9:45 AM, Simon Perry wrote:

...

On 02/03/12, Thomas Bächler wrote:

| Actually no. But you can make a backup copy of your old | initramfs-linux.img and compare lsinitcpio -a output for the old and new | one.

It's a lot of output to parse and diff accurately.

comm -3 <(lsinitcpio /boot/initramfs-linux.img) <(lsinitcpio /boot/initramfs-linux.img.orig) (note: `.orig` ;-) ... diff would work too.

...

Nevertheless, be glad you didn't bet (even though I provided no counter reward).

I've just spent 20 minutes netbooting, mount raid / lvm / luks volumes, and getting ext4 back into my initrd.

:-( i guess you missed the "make a backup copy of your old initramfs-linux.img" part? you should have been able to simply edit you bootloader on the fly, and use the old copy.

...

Filesystems hook is necessary if you want to leave MODULES bare.

indeed -- will include all FS modules if used before autodetect, or only your root device if used after. if not used at all ... well, then it won't include squat. -- C Anthony

Simon Perry

4:07 p.m.

On 02/03/12, C Anthony Risinger wrote: | i guess you missed the "make a backup copy of your old | initramfs-linux.img" part? you should have been able to simply edit | you bootloader on the fly, and use the old copy. Yep, dumb mistake. :( Forgot to put it in /boot ... -- Simon Perry (aka Pezz) [ s a n x i o n . n e t ]

C Anthony Risinger

4:18 p.m.

On Fri, Mar 2, 2012 at 10:07 AM, Simon Perry wrote:

...

On 02/03/12, C Anthony Risinger wrote:

| i guess you missed the "make a backup copy of your old | initramfs-linux.img" part? you should have been able to simply edit | you bootloader on the fly, and use the old copy.

Yep, dumb mistake. :(

Forgot to put it in /boot ...

as a simple pointer, i tend to do stuff like this: (backup) # cp /boot/initramfs-linux.img{,.orig} (restore) # cp /boot/initramfs-linux.img{.orig,} ... you can also use `mv` for the latter ... just make sure comma is on the correct side for what you want done. these just use bash's string expansion (the first of all expansions) to execute: # cp /boot/initramfs-linux.img /boot/initramfs-linux.img.orig ... and # cp /boot/initramfs-linux.img.orig /boot/initramfs-linux.img ... respectively. i make backups so often that i should really have a little alias or something ... then again, `cp` does backups itself, maybe should leverage that, meh. -- C Anthony

Simon Perry

4:37 p.m.

On 02/03/12, C Anthony Risinger wrote: | ... respectively. i make backups so often that i should really have a | little alias or something ... then again, `cp` does backups itself, | maybe should leverage that, meh. I normally stick to the "if I have the last working one there, and I can load it via editing the grub line, I'm good". Didn't eat my own dog food in this instance. I've grown to trust Arch kernels, however being the pedantic Sys Admin that I am, I like to resolve warnings (i.e. the mkinitcpio one). Something clearly changed in order to make this warning appear. I used to have ext2 and ext4 in my MODULES line, and autodetect and filesystems in my HOOKS. Never used to get a warning about ext4 being included twice, regardless of my lack of intricate "know how". So when you see it, you try and fix it. Trying leads to removing things from mkinitcpio.conf, this leads to sympathising with a brother on the Arch list, then getting told you have unecessary modules in your mkinitcpio.conf by an Arch hero, then missing one thing they said and blurping your box. Anyway, as David Crosby said in The Simpsons: Just take it one day at a time and know that I love you. -- Simon Perry (aka Pezz) [ s a n x i o n . n e t ]

Tom Gundersen

5:11 p.m.

On Fri, Mar 2, 2012 at 5:37 PM, Simon Perry wrote:

...

Something clearly changed in order to make this warning appear. I used to have ext2 and ext4 in my MODULES line, and autodetect and filesystems in my HOOKS. Never used to get a warning about ext4 being included twice, regardless of my lack of intricate "know how".

Sorry if this is already clear to anyone, but for the benefit of the archives: The reason having "ext2 ext4" in the MODULES array gives a warning is that we recently dropped the ext2 and ext3 modules in favor of making them aliases for ext4. We allow aliases of modules to appear in the MODULES array, so if you want to see what modules will _actually_ be included in your initramfs you could resolve all the aliases like: $ MODULES="ext2 ext3 ext4" $ modprobe -aR $MODULES ext4 ext4 ext4 Cheers, Tom

Myra Nelson

5:12 p.m.

On Fri, Mar 2, 2012 at 08:19, Tom Gundersen wrote:

...

On Mar 2, 2012 3:09 PM, "Thomas Bächler" wrote:

...
Am 02.03.2012 14:58, schrieb Simon Perry:

...
I have removed ext4 from my MODULES line, and removed the filesystems hook in order to get rid of the dupe message.

If you don't have the filesystem hook, and you don't have ext4 it in MODULES, ext4 will be missing from the initramfs and you won't be able to boot.

Unless you have ext2/3, as those are now aliases for ext4.

Tom

First off, sorry for causing so much noise. That was not my intent.

...

From Thomas Bächler If you don't have the filesystem hook, and you don't have ext4 it in MODULES, ext4 will be missing from the initramfs and you won't be able to boot.

...

From Tom Gunderson Unless you have ext2/3, as those are now aliases for ext4

Back to my original question. my box -> HOOKS="base udev autodetect pata scsi sata filesystems usb usbinput fsck numlock" new box ->HOOKS="base udev autodetect pata scsi sata filesystems usb usbinput fsck" Modules in my rc.conf -> MODULES=(e1000 vboxdrv) Module in new box rc.conf -> MODULES=() cp: warning: source file `/lib/modules/3.2.9-1-ARCH/kernel/fs/ext4/ext4.ko.gz' specified more than once What causes this warning? Does it need to be fixed? Is the error something I've done or is it in the hooks from mkinitcpio? I apologize for seeming terse, but the thread seems to have veered off topic just a bit. Myra -- Life's fun when your sick and psychotic!

Myra Nelson

5:15 p.m.

On Fri, Mar 2, 2012 at 11:12, Myra Nelson wrote:

...

On Fri, Mar 2, 2012 at 08:19, Tom Gundersen wrote:

...
On Mar 2, 2012 3:09 PM, "Thomas Bächler" wrote:

...
Am 02.03.2012 14:58, schrieb Simon Perry:

...
I have removed ext4 from my MODULES line, and removed the filesystems hook in order to get rid of the dupe message.

If you don't have the filesystem hook, and you don't have ext4 it in MODULES, ext4 will be missing from the initramfs and you won't be able to boot.

Unless you have ext2/3, as those are now aliases for ext4.

Tom

First off, sorry for causing so much noise. That was not my intent.

From Thomas Bächler If you don't have the filesystem hook, and you don't have ext4 it in MODULES, ext4 will be missing from the initramfs and you won't be able to boot.

From Tom Gunderson Unless you have ext2/3, as those are now aliases for ext4

Back to my original question.

my box -> HOOKS="base udev autodetect pata scsi sata filesystems usb usbinput fsck numlock"

new box ->HOOKS="base udev autodetect pata scsi sata filesystems usb usbinput fsck"

Modules in my rc.conf -> MODULES=(e1000 vboxdrv)

Module in new box rc.conf -> MODULES=()

cp: warning: source file `/lib/modules/3.2.9-1-ARCH/kernel/fs/ext4/ext4.ko.gz' specified more than once

What causes this warning? Does it need to be fixed? Is the error something I've done or is it in the hooks from mkinitcpio?

I apologize for seeming terse, but the thread seems to have veered off topic just a bit.

Myra

-- Life's fun when your sick and psychotic!

Thanks Tom. I sent my other reply before you last post. Consider this solved! Thanks Myra -- Life's fun when your sick and psychotic!

Tom Gundersen

5:22 p.m.

On Fri, Mar 2, 2012 at 6:15 PM, Myra Nelson wrote:

...

On Fri, Mar 2, 2012 at 11:12, Myra Nelson wrote:

...
First off, sorry for causing so much noise. That was not my intent.

Don't think you caused any :-)

...

...
my box -> HOOKS="base udev autodetect pata scsi sata filesystems usb usbinput fsck numlock"

new box ->HOOKS="base udev autodetect pata scsi sata filesystems usb usbinput fsck"

Modules in my rc.conf -> MODULES=(e1000 vboxdrv)

Module in new box rc.conf -> MODULES=()

cp: warning: source file `/lib/modules/3.2.9-1-ARCH/kernel/fs/ext4/ext4.ko.gz' specified more than once

[...]

...

Thanks Tom. I sent my other reply before you last post. Consider this solved!

Assuming you have ext[234] in your MODULES array in mkinitcpio.conf, then yes, that's the reason :-) (you pasted your MODULES array from rc.conf above, which is not involved in mkinitcpio). If, on the other hand, you don't have any fs modules in mkinitcpio.conf, then please file a bug against mkinitcpio. Cheers, Tom

Thomas Bächler

5:32 p.m.

Am 02.03.2012 18:22, schrieb Tom Gundersen:

...

Assuming you have ext[234] in your MODULES array in mkinitcpio.conf, then yes, that's the reason :-) (you pasted your MODULES array from rc.conf above, which is not involved in mkinitcpio). If, on the other hand, you don't have any fs modules in mkinitcpio.conf, then please file a bug against mkinitcpio.

This is a bug regardless. Warnings that have no meaning should be avoided if they are avoidable. This one is. Let's annoy Dave about it.

Myra Nelson

5:54 p.m.

On Fri, Mar 2, 2012 at 11:32, Thomas Bächler wrote:

...

Am 02.03.2012 18:22, schrieb Tom Gundersen:

...
Assuming you have ext[234] in your MODULES array in mkinitcpio.conf, then yes, that's the reason :-) (you pasted your MODULES array from rc.conf above, which is not involved in mkinitcpio). If, on the other hand, you don't have any fs modules in mkinitcpio.conf, then please file a bug against mkinitcpio.

This is a bug regardless. Warnings that have no meaning should be avoided if they are avoidable. This one is. Let's annoy Dave about it.

I know. Give a girl a break. I'm not awake yet. The sun doesn't come up till noon. modules from old mkinitcpio.conf MODULES="pata_atiixp ahci libahci ehci-hcd ohci-hcd ext2 ext4 vfat" modules from mikintcpio.conf now MODULES="pata_atiixp ahci libahci ehci-hcd ohci-hcd ext4 vfat" I ran sudo /sbin/mkinitcpio -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img and had no warnings. But if we can bug Dave anyway. I'll file a bug report. Myra -- Life's fun when your sick and psychotic!

C Anthony Risinger

5:17 p.m.

On Fri, Mar 2, 2012 at 11:12 AM, Myra Nelson wrote:

...

cp: warning: source file `/lib/modules/3.2.9-1-ARCH/kernel/fs/ext4/ext4.ko.gz' specified more than once

What causes this warning? Does it need to be fixed? Is the error something I've done or is it in the hooks from mkinitcpio?

I apologize for seeming terse, but the thread seems to have veered off topic just a bit.

it's harmless: # touch a b; mkdir c; cp a a b c/ cp: warning: source file `a' specified more than once # ls -1 c/ a b ... mkinitcpio prob just needs to sort+filter dupes. -- C Anthony

Thomas Bächler

5:27 p.m.

Am 02.03.2012 18:12, schrieb Myra Nelson:

...

Back to my original question.

my box -> HOOKS="base udev autodetect pata scsi sata filesystems usb usbinput fsck numlock"

new box ->HOOKS="base udev autodetect pata scsi sata filesystems usb usbinput fsck"

Modules in my rc.conf -> MODULES=(e1000 vboxdrv)

Module in new box rc.conf -> MODULES=()

The modules from rc.conf do not matter here - the modules from mkinitcpio.conf are relevant.

4457

Age (days ago)

4457

Last active (days ago)

List overview

Download

22 comments

5 participants

participants (5)

C Anthony Risinger
Myra Nelson
Simon Perry
Thomas Bächler
Tom Gundersen