All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@kernel.org
Subject: [Bug 196493] New: When LUN assignments on the target was changed, event must be triggered
Date: Wed, 26 Jul 2017 09:31:08 +0000	[thread overview]
Message-ID: <bug-196493-11613@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=196493

            Bug ID: 196493
           Summary: When LUN assignments on the target was changed, event
                    must be triggered
           Product: IO/Storage
           Version: 2.5
    Kernel Version: 3.13…4.4 and probably all other
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: SCSI
          Assignee: linux-scsi@vger.kernel.org
          Reporter: ds@vo-ix.ru
        Regression: No

1. The (e.g. SAN) device is unmapped and then the same LUN is reused by other
WWN, but no actions taken on linux-side.
2. Kernel receives indication and claims "Kernel: [15671249.097583] sd
8:0:15:9: Warning! Received an indication that the LUN assignments on this
target have changed. The Linux SCSI layer does not automatically remap LUN
assignments."
3. Observe no further actions at kernel-side. ioctl (requested via blockdev)
returns parameters of unmapped LUN.

Expect at least to cock the trigger on respective device (like mapped to sysfs
"/sys/block/sd*/device/evt_lun_change_reported") and thus provide the mechanism
to inform device mapper. In perspective, the feature of auto-invalidation and
rescan on changed path.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2017-07-26  9:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-196493-11613@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.