When the system has large number of disks(800) , Resource Filesystem start timeout (60s)

[peixubin]

My system has large number of disks about 800 , Resource Filesystem start timeout,exceed 60s. I read the resource script ,the problem is found in the partprobe call with no args in the trigger_udev_rules_if_needed function.

       [ "$refresh_flag" = "no" ] && return

        have_binary partprobe && **partprobe** >/dev/null 2>&1
        timeout=${OCF_RESKEY_CRM_meta_timeout:="60000"}

Moreover,my system has more than 20 filesystem.If each filesystem resource needs to call partprobe ,the service startup time will become very long .

I modify the script as follows:

      [ "$refresh_flag" = "no" ] && return

        have_binary partprobe && **partprobe $tmp ** >/dev/null 2>&1
        timeout=${OCF_RESKEY_CRM_meta_timeout:="60000"}

The script is running normally.

[oalbrigt]

Does this also work if the device is not yet known? Like if a fs is just created from another node on shared storage.