← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1511534] Re: [Hyper-V] Fibre Channel multipath error message

 

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
       Status: Triaged

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1511534

Title:
  [Hyper-V] Fibre Channel multipath error message

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Wily:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Problem statement:
  Wily (and probably other previous releases with the updated kernels) return a multipath error for vFC (virtual Fibre Channel).

  Symptoms:
  The following messages are in the dmesg log during booting:
      device-mapper: table: 252:4: multipath: error getting device
      device-mapper: IOCtl: error adding target to table

  After logging in, run the command: multipath -ll

  The multipath command does not return any errors, and no new messages
  are added to the dmesg log or syslog after running the multipath
  command.

  
  Steps to repro
  ============
  Tested with the released Wily (15.10), kernel 4.2.0-16-generic.

   1. Create a Wily VM.
   2. Boot and install the multipath-tools package.
   3. Shutdown and attach a Virtual Fiber Channel adapter and connect it to a virtual SAN.
      Note: The host must have a Fiber Channel adapter. Use Hyper-V managers Virtual SAN Manager to create a Virtual Fiber Channel Storage Area Network.
   4. Boot the VM.
   5. Issue the following command to see any errors were reported during the boot.
          dmesg | grep -i error
      You should see the following two error:
          device-mapper: table: 252:4: multipath: error getting device
          device-mapper: IOCtl: error adding target to table

  Otherwise, the vFC disks are usable and show no issues at a use test
  case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511534/+subscriptions