About iSCSI Hub

iSCSI SAN Targets, MPIO Multipathing & Block-Level Storage LUN Provisioning

What this site covers

iSCSI Hub is a reference for block storage over IP. iSCSI hands a client a raw disk rather than a share, and that single fact explains most of what is confusing about it: who owns the filesystem, why two hosts must not mount one LUN, why multipathing is not link aggregation, and why a healthy network can still deliver a device that behaves like a failing drive.

• Target, IQN and ACL configuration on Linux LIO, NAS appliances and Windows
• MPIO multipathing, path failover and the timers that govern it
• CHAP authentication, initiator masking, and what neither of them encrypts
• LUN provisioning: fileio versus block backstores, and thin-provisioning limits
• Network design for SAN throughput, including MTU and per-path subnetting
• Choosing between block and file protocols instead of defaulting to one

The scope is deliberately narrow. Anything that is really a general networking or general NAS question is out of scope unless block storage changes the answer.

6 articles are published so far, starting with iSCSI fundamentals and running through protocol selection, target setup on NAS hardware and fault diagnosis. The site also publishes a free iSCSI Throughput and MPIO Calculator that runs entirely in the browser. New articles are announced on the RSS feed.

How these articles are produced

Articles here are researched from primary sources: vendor and project documentation, published standards and specifications, research papers and preprints, and measurements published by whoever took them. Drafts are produced with AI assistance and then edited against those cited sources before anything is published.

No article on this site is based on first-hand testing in a private lab, and nothing here should be read as a measurement report of its own. Where a number appears, it comes from a source that is named, so you can check the original instead of taking this site's word for it.

Everything is published under a single editorial byline. That byline is a publishing identity for the site, not a claim about a named individual, and it does not carry professional credentials.

Corrections

Corrections are welcome. If something here is wrong, out of date, or attributed to the wrong source, email editor@iscsihub.com with the page address and what it should say. Substantive corrections are made in the article itself rather than quietly dropped.

How this site is funded

This site currently runs no affiliate links, sponsored posts, display advertising or paid placements. If that changes, the disclosure page will say so.

Contact

Email: editor@iscsihub.com
Site: iscsihub.com
Published by: iSCSI Hub Editorial

See also the privacy policy, the terms of use, and the editorial disclosure.