Description of problem: A read-only nfs mount point is configured as dump target in /etc/kdump.conf. Then kdump service can still be started successfully although mkdir test on the mount point is failed. Version-Release number of selected component (if applicable): kexec-tools-1.102pre-77.el5.1 How reproducible: Configure a read-only nfs mount point in /etc/kdump.conf. service kdump start Actual results: Kdump service is started OK. Expected results: Kdump service should fail. Because afterwards the dump process will definitely fail. And mkdir test already shows failure.
Created attachment 369095 [details] patch to check for writability here you go, this should validate thta the nfs mount can be written. Please verify this patch fixes the issue. Thanks!
ping, any feedback?
With your patch line, it seems still no r/w checking and the service can still be started with a ro nfs mountpoint.
Created attachment 390288 [details] new version of patch here, try this version.
With new patch, it works: [root@dhcp-65-30 ~]# service kdump start No kdump initial ramdisk found. [WARNING] Rebuilding /boot/initrd-2.6.18-164.el5kdump.img touch: cannot touch `/tmp/tmp.hIBoZq4191//var/crash/testfile': Read-only file system /etc/kdump.conf: Read only NFS mount 10.66.65.148:/nfs1 Failed to run mkdumprd [root@dhcp-65-30 ~]#
I'm re-proposing this bug as an exception, since the patch just missed the test deadline. Its very low impact, and it would be nice to square it away before 5.5
fixed in -94.el5
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: previously, kdump did not test to see whether an NFS location was writeable before commencing a dump. When an unwriteable NFS location was specified in kdump.conf, kdump would therefore start the dump anyway, which would inevitably fail. Kdump now checks that NFS locations are writeable before dumping, and therefore avoids performing dumps that are destined to fail.
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-2010-0179.html