On Wed, Apr 27, 2016 at 8:35 PM, Pratyush Anand <panand(a)redhat.com> wrote:
On Wed, Apr 27, 2016 at 6:10 PM, Xunlei Pang <xpang(a)redhat.com>
> For example, I just tested on my laptop:
> cat /etc/kdump.conf
> #raw /dev/vg/lv_kdump
> #ext4 /dev/vg/lv_kdump
> #xfs /dev/mapper/rhel-root
> #ext4 UUID=03138356-5e61-4ab3-b58e-27507ac41937
> #nfs 10.66.129.115:/export/nfs
> #ssh user(a)my.server.com
> #sshkey /root/.ssh/kdump_id_rsa
> path /var/crash
> Initailly it was mounted as:
> /dev/mapper/rhel-swap on /var/crash type ext2 (rw,relatime,seclabel)
> Then I unmounted /var/crash and changed /dev/mapper/rhel-swap to a ext4 using
> /dev/mapper/rhel-swap on /var/crash type ext4 (rw,relatime,seclabel,data=ordered)
> After that, I did kdumpctl restart, it didn't trigger the rebuilding.
> Actually, though "/dev/mapper/rhel-swap" device mapper name was not
> but its(dm-1's) uuid (and filesystem) has been changed.
Got It :-)
Thanks for the creating a scenario. Will send a follow-up patch to resolve it.
In stead of sending as follow-up patch, I merged the changes in V5.