On 03/28/17 at 06:33pm, Xunlei Pang wrote:
On 03/28/2017 at 05:55 PM, Baoquan He wrote:
> On 03/28/17 at 05:22pm, Xunlei Pang wrote:
>> On 03/28/2017 at 05:08 PM, Baoquan He wrote:
>>> On 03/28/17 at 05:03pm, Xunlei Pang wrote:
>>>> On 03/28/2017 at 04:05 PM, Baoquan He wrote:
>>>>>> @@ -120,7 +120,7 @@ to_mount() {
>>>>>> # If remote mount fails, dracut-initqueue will still start
and once
>>>>>> # dracut-initqueue finishes, kdump service will start.
Because remote mount
>>>>>> # failed, kdump service will fail and it will lead to kdump
error handler.
>>>>>> - if ! is_nfs_dump_target; then
>>>>>> + if ! is_fs_type_nfs $_fstype; then
>>>>> This sounds reasonable. But one question comes up, checking fedora
git
>>>>> log, I found commit about this code adding was merged earlier than
the
From the fedora git log:
commit 002337c6715e442f306b87b92340bef15c4420ac
Author: WANG Chao <chaowang(a)redhat.com>
Date: Thu May 8 19:37:15 2014 +0800
Introduce kdump error handling service
commit de95c74a76aa515f8e1baf5e5decdefd8ec4a81b
Author: WANG Chao <chaowang(a)redhat.com>
Date: Mon Jun 16 16:57:21 2014 +0800
mkdumprd: append "x-initrd.mount" to the mount options.
We usually don't respect the commit time since it's from posted patch,
instead the commit order need be concerned since that is when patch is
merged and the dependency order.
>