linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: admin <vondra@homeatcloud.cz>
To: linux-hotplug@vger.kernel.org
Subject: Dangling UDEV links after removing FC LUNs
Date: Sat, 03 Dec 2016 16:20:05 +0000	[thread overview]
Message-ID: <20161203162005.Horde.7B1kAhbyMfoGECiY5wzO_1J@owncloud.homeatcloud.cz> (raw)

Dear list,
we're using Q-Logic QLE2562 Fibre Channel adapters (qla2xxx driver) against a HPE 3PAR 7400c storage array in an OpenStack environment. The OpenStack 3PAR driver manages volume attachments from the array to the servers. There is 4 path multipath to every volume.

As the LUNs are removed, sometimes udev does not remove all links, particularly in /run/udev/links and /dev/disk/by-path. The symptoms are multiple records in one by-path directory under /run/udev/links, broken links to no longer attached luns in dev/disk/by-path and links between wrong LUNs and scsi devices there. I'm getting "multipathd: udev trigger error" in syslog.

OpenStack relies on these links. When another volume is attached using a LUN that has these leftover links and it happens that it is the first of the 4 paths, OpenStack incorrectly identifies the volume and attaches the same volume to multiple instances, leading to data loss.

What could be causing this behavior?

Ubuntu version 14.04
Linux version Ubuntu 4.4.0-47.68~14.04.1-generic 4.4.24
udev 204-5ubuntu20.19

Thanks for any troubleshooting tips, Tomas Vondra

             reply	other threads:[~2016-12-03 16:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-03 16:20 admin [this message]
2016-12-03 17:14 ` Dangling UDEV links after removing FC LUNs Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161203162005.Horde.7B1kAhbyMfoGECiY5wzO_1J@owncloud.homeatcloud.cz \
    --to=vondra@homeatcloud.cz \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).