drivers/scsi/esas2r

ATTO ExpressSAS R6xx 6Gb SAS/SATA RAID HBAs

A family of 6Gb/s SAS and SATA RAID host bus adapters that ATTO Technology sold under the ExpressSAS R6xx name (R680, R608, R60F, R6F0, R644, R648) for workstations and servers, used mainly in media production and storage appliances during the early-to-mid 2010s.

deprecate conf=0.80 deploy=low replacement=none subsystem=scsi category=storage-scsi-ata
80%

recommendation

A candidate for future removal because the hardware is on ATTO's own discontinued-products list, with the vendor saying it is no longer actively supported and only shipping legacy Linux packages for old distributions. Upstream activity since 2022 has been treewide SCSI API cleanup rather than real feature work, and ATTO's current lineup has moved to 12Gb and 24Gb parts. It still builds for the dwindling pool of existing deployments, so outright removal would be premature, but it should be flagged as legacy.

repository signals

16 files
15,396 source lines
23 commits, 5y
+78 / −104 lines added / removed, 5y
12 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 23 total · active in 15/61 months
2021 2022 2023 2024 2025 2026 2021-04: 1 commit · +1 −1 2021-05: 2 commits · +2 −1 2021-06: 0 commits · +0 −0 2021-07: 0 commits · +0 −0 2021-08: 0 commits · +0 −0 2021-09: 0 commits · +0 −0 2021-10: 1 commit · +4 −4 2021-11: 0 commits · +0 −0 2021-12: 0 commits · +0 −0 2022-01: 0 commits · +0 −0 2022-02: 0 commits · +0 −0 2022-03: 0 commits · +0 −0 2022-04: 0 commits · +0 −0 2022-05: 1 commit · +1 −1 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 0 commits · +0 −0 2022-09: 1 commit · +2 −2 2022-10: 2 commits · +11 −8 2022-11: 0 commits · +0 −0 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 2 commits · +2 −2 2023-04: 0 commits · +0 −0 2023-05: 0 commits · +0 −0 2023-06: 0 commits · +0 −0 2023-07: 0 commits · +0 −0 2023-08: 0 commits · +0 −0 2023-09: 1 commit · +6 −10 2023-10: 0 commits · +0 −0 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 0 commits · +0 −0 2024-02: 0 commits · +0 −0 2024-03: 0 commits · +0 −0 2024-04: 0 commits · +0 −0 2024-05: 0 commits · +0 −0 2024-06: 0 commits · +0 −0 2024-07: 0 commits · +0 −0 2024-08: 2 commits · +4 −6 2024-09: 0 commits · +0 −0 2024-10: 0 commits · +0 −0 2024-11: 1 commit · +0 −21 2024-12: 1 commit · +22 −22 2025-01: 0 commits · +0 −0 2025-02: 0 commits · +0 −0 2025-03: 0 commits · +0 −0 2025-04: 1 commit · +1 −1 2025-05: 2 commits · +4 −4 2025-06: 0 commits · +0 −0 2025-07: 0 commits · +0 −0 2025-08: 0 commits · +0 −0 2025-09: 0 commits · +0 −0 2025-10: 0 commits · +0 −0 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 1 commit · +4 −2 2026-02: 4 commits · +14 −19 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. git.kernel.org

    In-tree Kconfig describes this as the driver for ATTO Technology ExpressSAS R6xx SAS/SATA RAID controllers.

  2. git.kernel.org

    Driver source header and module metadata identify ATTO ExpressSAS R6xx RAID hardware.

  3. lore.kernel.org

    Recent upstream touches still reach this driver, but the visible activity is treewide maintenance/API churn rather than product-specific enablement.

  4. atto.com

    ATTO lists ExpressSAS RAID 6Gb HBAs under discontinued products, says these products are no longer actively supported, and Linux packages target old distributions/kernels.

  5. atto.com

    ATTO's current download catalog focuses on newer ExpressSAS 12Gb/24Gb families rather than the older ExpressSAS RAID 6Gb line.

codex reasoning notes (technical)

Local shell read of Kconfig/esas2r_main.c/esas2r.h identified ATTO ExpressSAS R6xx models (R680/R608/R60F/R6F0/R644/R648) plus related ATTO-branded variants. lore_activity on drivers/scsi/esas2r/esas2r_main.c showed 2022-2026 upstream traffic, but it is mostly treewide SCSI API cleanups/constification, with no clear removal thread and little sign of feature work. Web search found ATTO's discontinued-products page explicitly marking ExpressSAS RAID 6Gb as no longer actively supported and only shipping legacy software, so new 2025 sales look effectively gone. That argues for deprecate, not remove: legacy deployments likely remain, upstream still keeps it buildable, but the hardware family is firmly in legacy territory and has no obvious upstream successor driver.