Bug 97084 - mkinitd fails to detect rootfs on commented out /etc/fstab
Summary: mkinitd fails to detect rootfs on commented out /etc/fstab
Keywords:
Status: CLOSED DUPLICATE of bug 65249
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mkinitrd
Version: 7.3
Hardware: i686
OS: Linux
medium
low
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-06-10 04:02 UTC by Elan Ruusamäe
Modified: 2007-04-18 16:54 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:56:39 UTC
Embargoed:


Attachments (Terms of Use)
patch to fix the issue (491 bytes, patch)
2003-06-10 04:04 UTC, Elan Ruusamäe
no flags Details | Diff

Description Elan Ruusamäe 2003-06-10 04:02:27 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; UNIX) Opera 7.10  [en]

Description of problem:
mkinitd fails to detect rootfs when commented out entry present for '/' in 
/etc/fstab and therefore thinks rootfs is on LVM, which invokes lvmscan, which 
is not installed on system.

here's revelant part of code run:

++ awk '{ if ($2 == "/") { print $1; }}' /etc/fstab
+ rootdev=#LABEL=/
/dev/hda2
+ echo '#LABEL=/' /dev/hda2
+ cut -d/ -f3
+ grep loop
+ echo '#LABEL=/' /dev/hda2
+ cut -c1-6
+ grep LABEL=
++ ls -l '#LABEL=/
/dev/hda2'
ls: #LABEL=/
/dev/hda2: No such file or directory
++ sed -e 's/.* \([0-9]\+\), *[0-9]\+.*/\1/'
+ major=
+ '[' '' -ne 58 ']'
/sbin/mkinitrd: line 357: [: : integer expression expected
+ root_lvm=1





Version-Release number of selected component (if applicable):
mkinitrd-3.3.10-1

How reproducible:
Always

Steps to Reproduce:
1.add '#LABEL=/ /' to /etc/fstab
2.run mkinitrd

    

Additional info:

Comment 1 Elan Ruusamäe 2003-06-10 04:04:21 UTC
Created attachment 92291 [details]
patch to fix the issue

Comment 2 Jeremy Katz 2003-06-11 03:33:04 UTC

*** This bug has been marked as a duplicate of 65249 ***

Comment 3 Red Hat Bugzilla 2006-02-21 18:56:39 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.