Bug 450365

Summary:	rpm-based kernel upgraded cause kernel fault due to initrd busybox fault
Product:	Red Hat Enterprise Linux 4	Reporter:	Jason Haar <jhaar>
Component:	mkinitrd	Assignee:	Brian Lane <bcl>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	high	Docs Contact:
Priority:	low
Version:	4.6	CC:	varekova
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-07-27 18:01:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jason Haar 2008-06-07 02:58:09 UTC

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):


How reproducible:

every kernel upgrade is unusable.

Steps to Reproduce:
1. mount -oremount,mand /
2. upgrade kernel
3. reboot
  
Actual results:

fails to book

Expected results:

should boot

Additional info:

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
supports.

Comment 1 Ivana Varekova 2008-06-12 13:40:07 UTC

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).

Comment 2 Jason Haar 2008-06-12 22:38:05 UTC

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"?

Comment 3 Ivana Varekova 2008-06-13 07:49:02 UTC

Change the component to mkinitrd.