Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
QA failed with kexec-tools-2.0.0-84.el6.x86_64:
[root@ibm-x3655-03 ~]# tail /etc/kdump.conf
#disk_timeout 30
#extra_modules gfs2
#options modulename options
#default shell
#net root.eng.bos.redhat.com
#link_delay 60
#ext4 /dev/mapper/vg_ibmx365503-lv_root
ext4 LABEL="KDUMP TEST"
core_collector makedumpfile -c -d 31
[root@ibm-x3655-03 ~]# service kdump restart
Stopping kdump:[ OK ]
Detected change(s) the following file(s):
/etc/kdump.conf
Rebuilding /boot/initrd-2.6.32-37.el6.x86_64kdump.img
findfs: unable to resolve 'LABEL="KDUMP TEST"'
Usage: mount -V : print version
mount -h : print this help
mount : list mounted filesystems
mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
mount -a [-t|-O] ... : mount all stuff from /etc/fstab
mount device : mount device at the known place
mount directory : mount known device here
mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
mount --bind olddir newdir
or move a subtree:
mount --move olddir newdir
One can change the type of mount containing the directory dir:
mount --make-shared dir
mount --make-slave dir
mount --make-private dir
mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
mount --make-rshared dir
mount --make-rslave dir
mount --make-rprivate dir
mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
/etc/kdump.conf: Bad mount point
Failed to run mkdumprd
Starting kdump:[FAILED]
(In reply to comment #4)
> ext4 LABEL="KDUMP TEST"
...
> [root@ibm-x3655-03 ~]# service kdump restart
> Stopping kdump:[ OK ]
> Detected change(s) the following file(s):
>
> /etc/kdump.conf
> Rebuilding /boot/initrd-2.6.32-37.el6.x86_64kdump.img
> findfs: unable to resolve 'LABEL="KDUMP TEST"'
This is due to the double quote you put in kdump.conf, while the label itself doesn't contain any double quote. It's _not_ introduced by the original patch for this BZ.
Since it may block your testing, I will fix it now. My solution is:
+ config_val="$(echo $config_val | sed -e 's/"//g')"
config_val=$(findfs "$config_val")
However, this will cause problem if a label name really contains any double quote But that will be rare if not invalid.
(In reply to comment #5)
> Since it may block your testing, I will fix it now. My solution is:
>
> + config_val="$(echo $config_val | sed -e 's/"//g')"
> config_val=$(findfs "$config_val")
>
> However, this will cause problem if a label name really contains any double
> quote But that will be rare if not invalid.
Okay, I find another solution which seems better:
+ config_val=$(eval echo $config_val)
This will allow any valid single/double quotes in the label name in kdump.conf.
Comment 9releng-rhel@redhat.com
2010-11-10 21:00:13 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
QA failed with kexec-tools-2.0.0-84.el6.x86_64: [root@ibm-x3655-03 ~]# tail /etc/kdump.conf #disk_timeout 30 #extra_modules gfs2 #options modulename options #default shell #net root.eng.bos.redhat.com #link_delay 60 #ext4 /dev/mapper/vg_ibmx365503-lv_root ext4 LABEL="KDUMP TEST" core_collector makedumpfile -c -d 31 [root@ibm-x3655-03 ~]# service kdump restart Stopping kdump:[ OK ] Detected change(s) the following file(s): /etc/kdump.conf Rebuilding /boot/initrd-2.6.32-37.el6.x86_64kdump.img findfs: unable to resolve 'LABEL="KDUMP TEST"' Usage: mount -V : print version mount -h : print this help mount : list mounted filesystems mount -l : idem, including volume labels So far the informational part. Next the mounting. The command is `mount [-t fstype] something somewhere'. Details found in /etc/fstab may be omitted. mount -a [-t|-O] ... : mount all stuff from /etc/fstab mount device : mount device at the known place mount directory : mount known device here mount -t type dev dir : ordinary mount command Note that one does not really mount a device, one mounts a filesystem (of the given type) found on the device. One can also mount an already visible directory tree elsewhere: mount --bind olddir newdir or move a subtree: mount --move olddir newdir One can change the type of mount containing the directory dir: mount --make-shared dir mount --make-slave dir mount --make-private dir mount --make-unbindable dir One can change the type of all the mounts in a mount subtree containing the directory dir: mount --make-rshared dir mount --make-rslave dir mount --make-rprivate dir mount --make-runbindable dir A device can be given by name, say /dev/hda1 or /dev/cdrom, or by label, using -L label or by uuid, using -U uuid . Other options: [-nfFrsvw] [-o options] [-p passwdfd]. For many more details, say man 8 mount . /etc/kdump.conf: Bad mount point Failed to run mkdumprd Starting kdump:[FAILED]