Bug 438755

Summary: mkdumprd creates /dev/efirtc in wrong location in initrd
Product: Red Hat Enterprise Linux 5 Reporter: Doug Chapman <dchapman>
Component: kexec-toolsAssignee: Neil Horman <nhorman>
Status: CLOSED ERRATA QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.3CC: ddomingo, mgahagan, mmatsuya, qcai, tao, wmealing
Target Milestone: rc   
Target Release: ---   
Hardware: ia64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
(ia64) When the kdump kernel is booted, the following error will appear in the boot log: mknod: /tmp/initrd. [numbers] /dev/efirtc: No such file or directory This error results from a malformed request to create the efirtc in an incorrect path. However, the device path in question is also created statically in the initramfs when the kdump service is started. As such, the run-time creation of the device node is redundant, harmless, and should not affect the performance of kdump.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-20 20:58:38 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:
Bug Depends On:    
Bug Blocks: 391221, 454962    
Attachments:
Description Flags
patch to create /dev/efirtc in the right place none

Description Doug Chapman 2008-03-24 21:26:03 UTC 
Description of problem:
On a kdump boot on ia64 we see the following error:

Creating initial device nodes
mknod: /tmp/initrd.Ye4781/dev/efirtc: No such file or directory

This is caused by the bit of code in mkdumprd that creates the "init" for the
initrd image.  I am attaching a patch which resolves this issue.




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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Doug Chapman 2008-03-24 21:26:03 UTC 
Created attachment 298952 [details]
patch to create /dev/efirtc in the right place
Comment 2 Neil Horman 2008-03-25 10:58:51 UTC 
easy, obvious fix, with no need for extra testing, requesting exception for 5.2.
Comment 4 Neil Horman 2008-04-04 12:37:56 UTC 
cleared exceptio, moving to 5.3, since deadline passeed
Comment 10 Neil Horman 2008-04-29 14:30:55 UTC 
Release note material:
"""
On IA64 systems, there exists a bug in which, during the boot up of the kdump
kernel, this error will scroll accross the screen:
mknod: /tmp/initrd.<numbers>/dev/efirtc: No such file or directory

This error is the result of a malformed request to create the efirtc device node
in the wrong path.  However, the device node in question is also created
statically in the initramfs when the kdump service is started.  As such this
secondary, run time creation is redundant, and the resultant failure is
harmelss.  This cosmetic error will be corrected in our next release
"""
Comment 12 Don Domingo 2008-04-30 00:09:23 UTC 
adding to RHEL5.2 release notes updates:

<quote>
(ia64) When the kdump kernel is booted, the following error will appear in the
boot log:

mknod: /tmp/initrd.[numbers]/dev/efirtc: No such file or directory

This error results from a malformed request to create the efirtc in an incorrect
path. However, the device path in question is also created statically in the
initramfs when the kdump service is started. As such, the run-time creation of
the device node is redundant, harmless, and should not affect the performance of
kdump.
</quote>

please advise if any further revisions are required. thanks!
Comment 13 Kevin Krafthefer 2008-05-22 16:05:46 UTC 
This RFE has been reviewed during the RHEL RFE review
with Red Hat product management. This request has been *tentatively* approved
for inclusion
in the next update. This decision is not final and still pends further
technical review and scoping by Red Hat development engineering.
Comment 14 Neil Horman 2008-05-22 17:20:41 UTC 
fixed properly in -22.el5
Comment 16 Ryan Lerch 2008-08-11 01:30:36 UTC 
Tracking this bug for the Red Hat Enterprise Linux 5.3 Release Notes. 

This Release Note is currently located in the Known Issues section.
Comment 17 Ryan Lerch 2008-08-11 01:30:36 UTC 
Release note added. If any revisions are required, please set the 
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.
Comment 27 Neil Horman 2008-11-03 11:43:11 UTC 
I'm sorry, I don't know how I missed that.  There are several devices that get overwritten in this way.  and the fix is obvious.  I'm respinning now.
Comment 31 errata-xmlrpc 2009-01-20 20:58:38 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0105.html