** Description changed:

+ SRU Request for Lucid/Maverick/Natty/Oneiric:
+ 
+ [Impact] - When a server is configured with the /boot as a separate
+ partition, which is the default configuration when LVM installation is
+ selected, the kdump mechanism fails systematically.
+ 
+ [Development/Stable Fix] - This has been fixed in the development
+ version with the addition of the following:
+ 
+   * Backport changes to fix kdump functionality. LP: #828731.
+     - debian/kdump.initramfs: call /usr/bin/makedumpfile via a chroot command,
+       so that if makedumpfile is statically linked, we get proper library
+       resolution. Thanks to Louis Bouchard <louis.bouch...@canonical.com> for
+       the patch. LP: #785425.
+     - debian/kdump.initramfs: handle the possibility that /usr, /boot, or
+       /var is on a separate filesystem and needs to be manually mounted before
+       calling makedumpfile. LP: #828731.
+     - Depend on makedumpfile, without which the initramfs script doesn't work.
+     - Fix an unnecessary bashism.
+     - Only install the kdump initramfs script and depend on makedumpfile on
+       architectures that makedumpfile supports.
+ 
+ [Test Case] - See 'how to reproduce' below.
+ [Regression Potential] - Need to ensure kdump works correctly in backported 
versions.
+ 
+ --
+ 
  Binary package hint: kexec-tools
  
  This concerns kexec-tools 1:2.0.1-2ubuntu4 in Ubuntu Natty.
  
  I am trying to get a kernel crash dump. Instead of getting a nice vmcore
  file in /var/crash/, I get a vmcore.log file with the following:
  
  /root/usr/bin/makedumpfile: error while loading shared libraries:
  libdw.so.1: cannot open shared object file: No such file or directory
  
  Problem number 1: /usr/bin/makedumpfile is a dynamically-linked
  executable. Not the kind of thing you want to run in an initramfs
  environment.
  
  There is, however, a "makedumpfile-static" package, which not only
  provides /bin/makedumpfile-static, but also an initramfs-tools hook so
  that this statically-linked binary is copied in as /bin/makedumpfile in
  the initrd.
  
  Problem number 2: The 0_kdump script is hard-coded to use the dynamic
  binary in root:/usr/bin/. It is not at all aware of
  initrd:/bin/makedumpfile .

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/785425

Title:
  0_kdump uses dynamic makedumpfile(8) binary, which fails horribly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/785425/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to