[Bug 196493] New: When LUN assignments on the target was changed, event must be triggered

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxx
          Reporter: ds@xxxxxxxx
        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.



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]

  Powered by Linux