On 07/24/14 at 08:58am, Vivek Goyal wrote:
On Tue, Jul 22, 2014 at 03:18:00PM +0800, WANG Chao wrote:
[..]
diff --git a/mkdumprd b/mkdumprd index ba35800..c908b00 100644 --- a/mkdumprd +++ b/mkdumprd @@ -106,6 +106,9 @@ to_mount() { _fstype=$(findmnt -k -f -n -r -o FSTYPE $_dev) _options=$(findmnt -k -f -n -r -o OPTIONS $_dev) _options=${_options/#ro/rw} #mount fs target as rw in 2nd kernel
- # "x-initrd.mount" mount failure will trigger isolate emergency service
- # W/o this, systemd won't isolate, thus we won't get to emergency
- _options="$_options,x-initrd.mount"
Hi Chao,
Say, I am dumping to an NFS target and mounting NFS fails. Assume "default" in kdump.conf is "dump_to_rootfs". Now by the time we hit kdump emergency service, has rootfs been mounted so that dump can be saved on root fs?
Yes.
If dump_to_rootfs(), we will start dracut-initqueue service and sysroot.mount again. So yes, the /sysroot is ok to access.
But I find a problem, when thinking about your question. nfs mount is not supposed to be with "x-initrd.mount". "x-initrd.mount" is only useful for local mount, because nfs mount should be associated with remote-fs.target. I'll send an update to fix it.
Thanks WANG Chao