Flags are required on the kernel command line to blacklist certain ARRAY vendor devices to deal with WRITE_SAME issues

Solution Verified - Updated -

Issue

We have found that some storage arrays at some firmware revisions return errors on WRITE SAME commands issued to perform discard operations. A new blacklist flag allows the kernel to avoid issuing commands that the array will incorrectly reject.

From the patch description:

Implement blacklist option for WRITE SAME w/ UNMAP

SBC-4 states:
  "A MAXIMUM UNMAP LBA COUNT field set to a non-zero value indicates the
   maximum number of LBAs that may be unmapped by an UNMAP command"

  "A MAXIMUM WRITE SAME LENGTH field set to a non-zero value indicates
   the maximum number of contiguous logical blocks that the device server
   allows to be unmapped or written in a single WRITE SAME command."

Despite the spec being clear on the topic, some devices incorrectly
expect WRITE SAME commands with the UNMAP bit set to be limited to the
value reported in MAXIMUM UNMAP LBA COUNT in the Block Limits VPD.

Implement a blacklist option that can be used to accommodate devices
with this behavior.

Environment

Array vendors that have LUNS provisioned supporting the thin provisioning functionality.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.