Red Hat Bugzilla – Bug 450365
rpm-based kernel upgraded cause kernel fault due to initrd busybox fault
Last modified: 2011-07-27 14:01:29 EDT
Description of problem:
We're using HAVP as an AV proxy, which requires the root fs to be mounted "mand"
- mandatory locks. However, when a kernel upgrade occurs, the initrd
auto-generated includes the "mand" option - and busybox's mount command doesn't
support mand. So initrd cannot mount the root fs and crashes!
Version-Release number of selected component (if applicable):
every kernel upgrade is unusable.
Steps to Reproduce:
1. mount -oremount,mand /
2. upgrade kernel
fails to book
either busybox should support every FS option that the kernel supports, or the
kernel installer should be smart enough to only "remember" fs options busybox
Hello, I'm not sure why busybox is used here - there is no reason to be used
busybox. So please do you know what is the cause/ do you use some special
setting? (I'm not sure whether I have not overlook something but if you use the
steps you attach here in Steps to Reproduce, then the busybox is not called at all).
I'm sorry, I assumed it was busybox due to my previous experience with mkcdrec -
which uses busybox to keep the initrd size down
I've just unpacked initrd and I see there's no /bin/mount in there, so I assume
it must be a built-in function of /bin/nash?
So it's the "mount" functionality of nash that doesn't support the more esoteric
FS options - such as "mand"?
Change the component to mkinitrd.