New answers tagged


Dell's iSCSI mode just tracks targets and initiators, all you should really be doing is follow the specific best practices for that switch/SAN, usually this is MTU 9k+ (Force10 use 12k) Flow control rx on tx off Never do port channels, each interface should have a single ip, use multipath to aggregate links. Avoid vlan tagging


No - iSCSI runs over IP, the switch doesn't need to know how to specifically handle it for iSCSI to run.


This appears to be an SELinux policy choice. The discovery session is running within iscsiadm, but iscsid is restricted in which ports it can connect to. One option is to use the audit2why/audit2allow utils from policycoreutils to create a local policy module, extending the default system SELinux policy to allow this.


The iSCSI intiator (client) service are split to facilitate various use cases while making use of systemd socket activation so that long running services (iscsid) are only started if needed. The iscsi.service is used to manage automatic login/logout of persistent records. The iscsid.service manages the lifetime of iscsid, it will start automatically using ...


"COMPARE AND WRITE" opcode usually means that your writing queue is continuously growing because of low disk write performance. The reason for such behavior may be a very highly loaded OS (Synology DSM) or faulty disk drive assuming that network connection from your ESX host to NAS is OK. First of all check CPU/RAM usage on your Synology box. Also check the ...


You cannot do what you're intended to do with a built-in software RAID from Microsoft. Reason is within Windows network stack comes earlier than storage stack so your RAID will always start in broken state and will do long and painful resyncs and rebalances and rechecks. You may however use some third-party software to aggregate iSCSI volumes into sort of a ...


Wanting to glue together multiple iscsi targets is a perfectly valid idea. There are plenty of reasons you'd want to do it. Here is a simple scenario: 1) I've got 2 servers, and each has 12 disks in a Raid6, giving me 36TB usable space on each server. All of that storage is already RAIDed, to provide redundancy and protect from disk failures etc. 2) I ...


For closure, there were multiple things wrong. The hosts were configured for a 1500 byte MTU, whereas the storage SAN was using 9216 byte MTU. One of the hosts had a subtly-different IQN from reality - the SAN listed the correct IQN as "unassigned" even though it was visually the same as the IQN in use. My original two nodes had management IPs ...

Top 50 recent answers are included