RHEL 7 VM takes more than 10 minutes to boot with FC RDM LUNs

Solution Verified - Updated -

Issue

  • RHEL 7 VM takes more than 10 minutes to boot with FC RDM LUNs.
    During boot the process, console logs showed following errors and call traces:

    sd 2:0:7:0: timing out command, waited 120s 
    INFO: task systemd-udevd:261 blocked for more than 120 seconds. 
    "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 
    systemd-udevd D ffff946d2b30a080 0 261 259 0x00000000 
    Call Trace: 
    schedule+0x29/0x70 
     [<ffffffff810c9355>] async_synchronize_cookie_domain+0x85/0x150 
     [<ffffffff810c2d00>] ? wake_up_atomic_t+0x30/0x30 
     [<ffffffff810c9457>] async_synchronize_full+0x17/0x20 
     [<ffffffff81118fe7>] load_module+0x2787/0x2bc0 
     [<ffffffff813a3030>] ? ddebug_proc_write+0x100/0x100 
     [<ffffffff8111950f>] SyS_init_module+0xef/0x140 
     [<ffffffff81774ddb>] system_call_fastpath+0x22/0x27 
     [<ffffffff81774d21>] ? system_call_after_swapgs+0xae/0x146 
     sd 2:0:8:0: timing out command, waited 120s 
    
  • Same issue does not occur while using iSCSI RDM LUNs.

Environment

  • Red Hat Enterprise Linux 7.4+
  • SolidFire SSD SAN LUNs mapped to VMware guest using FC RDM.
  • ESXi 6.0 U3, 6.5 U3, 6.7 U2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content