From: "Steve Wise" <swise@opengridcomputing.com>
To: "'nborisov'" <n.borisov.lkml@gmail.com>, <linux-kernel@vger.kernel.org>
Subject: RE: vmcore not getting created on linux-4.7
Date: Fri, 24 Jun 2016 15:19:09 -0500 [thread overview]
Message-ID: <014d01d1ce55$aa469730$fed3c590$@opengridcomputing.com> (raw)
In-Reply-To: <576D61C3.6030509@gmail.com>
> >> Also what's the content of your /etc/kdump.conf file?
> >>
> >
> > #raw /dev/sda5
> > #ext4 /dev/sda3
> > #ext4 LABEL=/boot
> > #ext4 UUID=03138356-5e61-4ab3-b58e-27507ac41937
> > #net my.server.com:/export/tmp
> > #net user@my.server.com
> > path /var/crash
> > #ext4 /dev/nvme0n1
> > core_collector makedumpfile -c --message-level 1 -d 31
> > #core_collector makedumpfile -c --message-level 1 -d 17
> > #core_collector scp
> > #core_collector cp --sparse=always
> > #extra_bins /bin/cp
> > #link_delay 60
> > #kdump_post /var/crash/scripts/kdump-post.sh
> > #extra_bins /usr/bin/lftp
> > #disk_timeout 30
> > #extra_modules gfs2
> > #options modulename options
> > #default shell
> > #debug_mem_level 0
> > #force_rebuild 1
> > #sshkey /root/.ssh/kdump_id_rsa
> >
>
> Rather standart, indeed. I have a similar configuration and everything
> is working as expected. The only other thing which I can suggest is to
> try updating the makedumpfile binary.
Updating to 1.6.0 of makedumpfile didn't help. :(
next prev parent reply other threads:[~2016-06-24 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 14:45 vmcore not getting created on linux-4.7 Steve Wise
2016-06-24 15:06 ` nborisov
2016-06-24 15:12 ` Steve Wise
2016-06-24 16:37 ` nborisov
2016-06-24 20:19 ` Steve Wise [this message]
[not found] ` <014e01d1ce55$aa4ba040$fee2e0c0$@opengridcomputing.com>
2016-07-12 16:13 ` Steve Wise
[not found] ` <00ca01d1dc58$52f00730$f8d01590$@opengridcomputing.com>
2016-07-14 19:19 ` Steve Wise
[not found] ` <00b501d1ce2a$cad610f0$608232d0$@opengridcomputing.com>
2016-06-24 16:37 ` Steve Wise
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='014d01d1ce55$aa469730$fed3c590$@opengridcomputing.com' \
--to=swise@opengridcomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=n.borisov.lkml@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox