[opensuse-factory] Why is btrfs added to initrd
Hi, I'm using recent factory snapshot and wonder why btrf is always loaded by initrd allthough I don't use it and it's not set in /etc/sysconfig? cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 10/10/13 06:14, Ruediger Meier escribió:
Hi,
I'm using recent factory snapshot and wonder why btrf is always loaded by initrd allthough I don't use it and it's not set in /etc/sysconfig?
cu, Rudi
because mkinitrd is dumb and does not know, if that is a concern, use dracut -H ... -- "Judging by their response, the meanest thing you can do to people on the Internet is to give them really good software for free". - Anil Dash -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday 10 October 2013, Cristian Rodríguez wrote:
El 10/10/13 06:14, Ruediger Meier escribió:
Hi,
I'm using recent factory snapshot and wonder why btrf is always loaded by initrd allthough I don't use it and it's not set in /etc/sysconfig?
cu, Rudi
because mkinitrd is dumb and does not know, if that is a concern, use dracut -H ...
Until the update to 13.1 mkinitrd never installed btrfs so my questions is why this is done now by default. cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/10/2013 09:45 AM, Ruediger Meier pecked at the keyboard and wrote:
On Thursday 10 October 2013, Cristian Rodríguez wrote:
El 10/10/13 06:14, Ruediger Meier escribió:
Hi,
I'm using recent factory snapshot and wonder why btrf is always loaded by initrd allthough I don't use it and it's not set in /etc/sysconfig?
cu, Rudi
because mkinitrd is dumb and does not know, if that is a concern, use dracut -H ...
Until the update to 13.1 mkinitrd never installed btrfs so my questions is why this is done now by default.
cu, Rudi
This is the prequel to btrfs being forced upon people the same way KDE4 and systemd was previously force fed to the masses. And yes I know other options will be offered (not easily) during install. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday 2013-10-10 16:12, Ken Schneider - openSUSE wrote:
I'm using recent factory snapshot and wonder why btrf is always loaded by initrd allthough I don't use it and it's not set in /etc/sysconfig?
This is the prequel to btrfs being forced upon people the same way KDE4 was previously force fed to the masses.
No it is not, please get your facts straight. The inclusion of btrfs.ko into initrds did not go in line with the simultaneous removal of ext*.ko. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/10/13 9:45 AM, Ruediger Meier wrote:
On Thursday 10 October 2013, Cristian Rodríguez wrote:
El 10/10/13 06:14, Ruediger Meier escribió:
Hi,
I'm using recent factory snapshot and wonder why btrf is always loaded by initrd allthough I don't use it and it's not set in /etc/sysconfig?
cu, Rudi
because mkinitrd is dumb and does not know, if that is a concern, use dracut -H ...
Until the update to 13.1 mkinitrd never installed btrfs so my questions is why this is done now by default.
Contrary to some other opinions, it's just a bug in the mkinitrd hooks for btrfsprogs. It'll happen on any system where btrfsprogs is installed, whether btrfs is used or not. setup-btrfs.sh doesn't test whether it's actually required for anything and boot-btrfs.sh doesn't have anything to key off to determine whether it's needed. I'll poke at it. It should be pretty easy to fix. -Jeff -- Jeff Mahoney SUSE Labs
On Thursday 10 October 2013, Jeff Mahoney wrote:
On 10/10/13 9:45 AM, Ruediger Meier wrote:
On Thursday 10 October 2013, Cristian Rodríguez wrote:
El 10/10/13 06:14, Ruediger Meier escribió:
Hi,
I'm using recent factory snapshot and wonder why btrf is always loaded by initrd allthough I don't use it and it's not set in /etc/sysconfig?
cu, Rudi
because mkinitrd is dumb and does not know, if that is a concern, use dracut -H ...
Until the update to 13.1 mkinitrd never installed btrfs so my questions is why this is done now by default.
Contrary to some other opinions, it's just a bug in the mkinitrd hooks for btrfsprogs. It'll happen on any system where btrfsprogs is installed, whether btrfs is used or not.
setup-btrfs.sh doesn't test whether it's actually required for anything and boot-btrfs.sh doesn't have anything to key off to determine whether it's needed.
I'll poke at it. It should be pretty easy to fix.
Thanks. BTW now in 13.1 the initrd wants to load a lot more modules: btrfs dm-snapshot-origin dm-mirror dm-snapshot hid-holtek-kbd hid-lenovo-tpkbd hid-logitech-dj hid-ortek hid-roccat-arvo hid-roccat-isku hid-samsung hid-apple hid-belkin hid-cherry hid-ezkey hid-microsoft I guess that one of the hid modules causes my system to hang (see the other thread). How can I tell mkinitrd to skip partikular modules? cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 10/10/13 11:39, Ruediger Meier escribió:
How can I tell mkinitrd to skip partikular modules?
blacklisting them.. or just create your initrd with dracut in host only mode. -- "If debugging is the process of removing bugs, then programming must be the process of putting them in." - Edsger Dijkstra -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/10/13 10:39 AM, Ruediger Meier wrote:
On Thursday 10 October 2013, Jeff Mahoney wrote:
On 10/10/13 9:45 AM, Ruediger Meier wrote:
On Thursday 10 October 2013, Cristian Rodríguez wrote:
El 10/10/13 06:14, Ruediger Meier escribió:
Hi,
I'm using recent factory snapshot and wonder why btrf is always loaded by initrd allthough I don't use it and it's not set in /etc/sysconfig?
cu, Rudi
because mkinitrd is dumb and does not know, if that is a concern, use dracut -H ...
Until the update to 13.1 mkinitrd never installed btrfs so my questions is why this is done now by default.
Contrary to some other opinions, it's just a bug in the mkinitrd hooks for btrfsprogs. It'll happen on any system where btrfsprogs is installed, whether btrfs is used or not.
setup-btrfs.sh doesn't test whether it's actually required for anything and boot-btrfs.sh doesn't have anything to key off to determine whether it's needed.
I'll poke at it. It should be pretty easy to fix.
Thanks.
BTW now in 13.1 the initrd wants to load a lot more modules: btrfs
Bug. Fix posted in this thread.
dm-snapshot-origin dm-mirror dm-snapshot
This happens if you're already using dm to hold your root file system. The problem is that those modules are added whether you're using them or not. Also, any dm modules that are used by active tables whether they're used by the root file system/swap or not are included automatically. Unfortunately, descending the stack to determine which modules are in use can be fragile. Every dm target's table, where the format is specific to the target type, would need to be parsed and the only benefit is not including a few modules in the initrd.
hid-holtek-kbd hid-lenovo-tpkbd hid-logitech-dj hid-ortek hid-roccat-arvo hid-roccat-isku hid-samsung hid-apple hid-belkin hid-cherry hid-ezkey hid-microsoft
These are actually in response to bug reports. There are systems that need these modules loaded in order for keyboard input to work. It might be worthwhile to see if we can load them only if keyboard input is actually needed. I'm not sure that'd be a high priority item, though.
I guess that one of the hid modules causes my system to hang (see the other thread).
How can I tell mkinitrd to skip partikular modules?
You can't. You can direct modprobe to skip modules, though, via /etc/modprobe.d/ files. -Jeff -- Jeff Mahoney SUSE Labs
On 10/10/13 10:32 AM, Jeff Mahoney wrote:
On 10/10/13 9:45 AM, Ruediger Meier wrote:
On Thursday 10 October 2013, Cristian Rodríguez wrote:
El 10/10/13 06:14, Ruediger Meier escribió:
Hi,
I'm using recent factory snapshot and wonder why btrf is always loaded by initrd allthough I don't use it and it's not set in /etc/sysconfig?
cu, Rudi
because mkinitrd is dumb and does not know, if that is a concern, use dracut -H ...
Until the update to 13.1 mkinitrd never installed btrfs so my questions is why this is done now by default.
Contrary to some other opinions, it's just a bug in the mkinitrd hooks for btrfsprogs. It'll happen on any system where btrfsprogs is installed, whether btrfs is used or not.
setup-btrfs.sh doesn't test whether it's actually required for anything and boot-btrfs.sh doesn't have anything to key off to determine whether it's needed.
I'll poke at it. It should be pretty easy to fix.
Ok, all that should be needed is adding the following to the end of the comments section in /lib/mkinitrd/scripts/boot-btrfs.sh. All of my 13.1 installs use a btrfs root and I've confirmed it works as expected there. Can someone with a different rootfs test and confirm it doesn't include the btrfs module? ---->8---- #%if: "$rootfstype" = "btrfs" ----8<---- All that's needed is to run mkinitrd afterwards and confirm that the btrfs module isn't included. Once I get confirmation, I'll submit a new btrfsprogs package with that fix. -Jeff -- Jeff Mahoney SUSE Labs
On Thursday 10 October 2013, Jeff Mahoney wrote:
On 10/10/13 10:32 AM, Jeff Mahoney wrote:
On 10/10/13 9:45 AM, Ruediger Meier wrote:
On Thursday 10 October 2013, Cristian Rodríguez wrote:
El 10/10/13 06:14, Ruediger Meier escribió:
Hi,
I'm using recent factory snapshot and wonder why btrf is always loaded by initrd allthough I don't use it and it's not set in /etc/sysconfig?
cu, Rudi
because mkinitrd is dumb and does not know, if that is a concern, use dracut -H ...
Until the update to 13.1 mkinitrd never installed btrfs so my questions is why this is done now by default.
Contrary to some other opinions, it's just a bug in the mkinitrd hooks for btrfsprogs. It'll happen on any system where btrfsprogs is installed, whether btrfs is used or not.
setup-btrfs.sh doesn't test whether it's actually required for anything and boot-btrfs.sh doesn't have anything to key off to determine whether it's needed.
I'll poke at it. It should be pretty easy to fix.
Ok, all that should be needed is adding the following to the end of the comments section in /lib/mkinitrd/scripts/boot-btrfs.sh. All of my 13.1 installs use a btrfs root and I've confirmed it works as expected there. Can someone with a different rootfs test and confirm it doesn't include the btrfs module?
---->8---- #%if: "$rootfstype" = "btrfs" ----8<----
All that's needed is to run mkinitrd afterwards and confirm that the btrfs module isn't included. Once I get confirmation, I'll submit a new btrfsprogs package with that fix.
This works. btrfs is not included anymore. Later this evening I will test rebooting. Could also be that "btrfs dev scan" was responsible for hanging the long time at boot. cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/10/13 11:05 AM, Ruediger Meier wrote:
On Thursday 10 October 2013, Jeff Mahoney wrote:
On 10/10/13 10:32 AM, Jeff Mahoney wrote:
On 10/10/13 9:45 AM, Ruediger Meier wrote:
On Thursday 10 October 2013, Cristian Rodríguez wrote:
El 10/10/13 06:14, Ruediger Meier escribió:
Hi,
I'm using recent factory snapshot and wonder why btrf is always loaded by initrd allthough I don't use it and it's not set in /etc/sysconfig?
cu, Rudi
because mkinitrd is dumb and does not know, if that is a concern, use dracut -H ...
Until the update to 13.1 mkinitrd never installed btrfs so my questions is why this is done now by default.
Contrary to some other opinions, it's just a bug in the mkinitrd hooks for btrfsprogs. It'll happen on any system where btrfsprogs is installed, whether btrfs is used or not.
setup-btrfs.sh doesn't test whether it's actually required for anything and boot-btrfs.sh doesn't have anything to key off to determine whether it's needed.
I'll poke at it. It should be pretty easy to fix.
Ok, all that should be needed is adding the following to the end of the comments section in /lib/mkinitrd/scripts/boot-btrfs.sh. All of my 13.1 installs use a btrfs root and I've confirmed it works as expected there. Can someone with a different rootfs test and confirm it doesn't include the btrfs module?
---->8---- #%if: "$rootfstype" = "btrfs" ----8<----
All that's needed is to run mkinitrd afterwards and confirm that the btrfs module isn't included. Once I get confirmation, I'll submit a new btrfsprogs package with that fix.
This works. btrfs is not included anymore. Later this evening I will test rebooting. Could also be that "btrfs dev scan" was responsible for hanging the long time at boot.
Yeah, I think we're gonna have to do something about the unqualified "btrfs dev scan" there. Otherwise we're gonna run into trouble with systems that have discovered lots of devices while looking for the root file system. mdadm has solved this with a config file that specifies which devices to search. I suppose a potential headache with this approach is that, when we start supporting multiple device volumes, if a new device is added to the root file system, the initrd will have to be regenerated. I'm not sure that's a great approach. -Jeff -- Jeff Mahoney SUSE Labs
On Thursday 10 October 2013, Jeff Mahoney wrote:
On 10/10/13 11:05 AM, Ruediger Meier wrote:
On Thursday 10 October 2013, Jeff Mahoney wrote:
On 10/10/13 10:32 AM, Jeff Mahoney wrote:
On 10/10/13 9:45 AM, Ruediger Meier wrote:
On Thursday 10 October 2013, Cristian Rodríguez wrote:
El 10/10/13 06:14, Ruediger Meier escribió: > Hi, > > I'm using recent factory snapshot and wonder why btrf is > always loaded by initrd allthough I don't use it and it's not > set in /etc/sysconfig? > > cu, > Rudi
because mkinitrd is dumb and does not know, if that is a concern, use dracut -H ...
Until the update to 13.1 mkinitrd never installed btrfs so my questions is why this is done now by default.
Contrary to some other opinions, it's just a bug in the mkinitrd hooks for btrfsprogs. It'll happen on any system where btrfsprogs is installed, whether btrfs is used or not.
setup-btrfs.sh doesn't test whether it's actually required for anything and boot-btrfs.sh doesn't have anything to key off to determine whether it's needed.
I'll poke at it. It should be pretty easy to fix.
Ok, all that should be needed is adding the following to the end of the comments section in /lib/mkinitrd/scripts/boot-btrfs.sh. All of my 13.1 installs use a btrfs root and I've confirmed it works as expected there. Can someone with a different rootfs test and confirm it doesn't include the btrfs module?
---->8---- #%if: "$rootfstype" = "btrfs" ----8<----
All that's needed is to run mkinitrd afterwards and confirm that the btrfs module isn't included. Once I get confirmation, I'll submit a new btrfsprogs package with that fix.
This works. btrfs is not included anymore. Later this evening I will test rebooting. Could also be that "btrfs dev scan" was responsible for hanging the long time at boot.
Yeah, I think we're gonna have to do something about the unqualified "btrfs dev scan" there. Otherwise we're gonna run into trouble with systems that have discovered lots of devices while looking for the root file system.
Ok I have rebooted again. The hanging was not caused by btrfs. It still happens. But btrfs module is still loaded during the boot process. Not by initrd anymore but later, see http://pastebin.com/KQnqRSRp cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Cristian Rodríguez -
Jan Engelhardt -
Jeff Mahoney -
Ken Schneider - openSUSE -
Ruediger Meier