| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
Handle unsupported commands as not conflicting/blocking.
|
|
|
|
|
|
|
|
|
| |
sesX device number may change between reboots, so to properly identify
the instance we need more data. Name and ID reported here may mach ones
reported by SCSI device, but that is not really required by specs.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Introduce "ha_shared" port option, which being set to "on" moves the
port into separate port group, shared between HA nodes. This allows to
better handle cases when iSCSI portals are bound to CARP address that can
dynamically move between nodes. Some initiators (at least VMware) don't
detect that after iSCSI reconnect they've attached to different SCSI port
from different port group, that totally breakes ALUA status parsing.
In theory, I believe, it should be enough to have different iSCSI portal
group tags on different nodes to make initiators detect this condition,
but it seems like VMware ignores those values, and even full LUN retaste
forced by UA does not help.
- Make CTL report up to three port groups: 1 -- non-HA mode or ports
with "ha_shared" option set, 2 -- HA node 1, 3 -- HA node 2.
- Report Transitioning state for all port groups when HA interlink is
connected, but neither of nodes is primary for the LUN.
MFC after: 2 weeks
|
|
|
|
|
| |
Submitted by: Dmitry Luhtionov <dmitryluhtionov@gmail.com>
MFC after: 1 week
|
| |
|
| |
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
CTL itself still lives in flat LUN space, but it can generate extended
numbers if CAM SIM reports such capability.
|
|
|
|
|
|
|
|
| |
This change allows to decode respective functions in isp(4) in target mode
and pass them through CAM to CTL. Unfortunately neither CAM nor isp(4)
support returning response info for those task management functions now.
On the other side I just have no initiator to test this functionality.
|
|
|
|
| |
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
| |
This allows to set delete method via tunable, before device capabilities
are known. Also allow ZERO method for devices not reporting LBP, if user
explicitly requests it -- it may be useful if storage supports compression
and WRITE SAME, but does not support UNMAP.
MFC after: 2 weeks
|
| |
|
|
|
|
|
| |
We got new ATA stack in FreeBSD 8.x, switched to it at 9.x, completely
removed old stack at 10.x, so at 11.x it is time to remove compat shims.
|
|
|
|
|
|
|
|
| |
I am not sure what for it was done. Now open routine should automatically
fall back to read-only if open for writing is impossible. In such case
attempt to upgrade to write sounds strange.
MFC after: 1 week
|
|
|
|
|
| |
Submitted by: Richard Kojedzinszky
MFC after: 1 week
|
|
|
|
| |
On some tests I've measured 5% copy speedup from this.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Previous limitation of 64K (DFLTPHYS) is quite annoying.
|
| |
|
|
|
|
|
| |
While this bit is obsolete in SBC-3, behavior controlled by it is allowed
on device discretion.
|
| |
|
| |
|
|
|
|
| |
This page is obsolete since MMC-4, but still used by some software.
|
|
|
|
|
| |
In case of block backend eject really closes the backing store, while
load tries to open it back. Failed store open is reported as no media.
|
|
|
|
| |
Relnotes: yes
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
While there, make num_dmas accounted independently of CTL_TIME_IO.
|
| |
|
|
|
|
|
| |
Now from primary node point of view requests transferred from secondary
node should look almost normal and always have valid port.
|
| |
|
|
|
|
| |
This combination was originally forbidden, but allowed at spc4r3.
|
|
|
|
| |
This is only for completeness, since we have nothing new to report there.
|
|
|
|
|
| |
This is only a cosmetic change. We still don't support atomic boundary
field in the CDB, but at least now we do it formally.
|
| |
|
|
|
|
|
|
| |
We allow to modify only few fields in mode pages now, but still it is
not good if they unexpectedly change during failover. Also this fixes
reporting of "Mode parameters changed" UAs on secondary node.
|