Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignore BIO_FLUSH command if there is no volatile cache to flush #710

Closed

Commits on Apr 5, 2023

  1. When a storage device reports that it does not support cache flush, t…

    …he GEOM
    
    disk layer by default returns ENOTSUPP in response to a BIO_FLUSH command.
    
    On AWS, local volumes do not advertise themselves as having write-cache enabled.
    When they are selected for L3 on all HDD nodes, the L3 subsystem may inadvertently
    kick these L3 devices if a BIO_FLUSH command fails with an ENOTSUPP return code.
    The fix is to make GEOM disk return success (0) when this condition occurs and
    add a sysctl to make this error handling config-driven
    santhoshkumar-mani committed Apr 5, 2023
    Configuration menu
    Copy the full SHA
    1f838c2 View commit details
    Browse the repository at this point in the history

Commits on Apr 7, 2023

  1. Configuration menu
    Copy the full SHA
    2badeb7 View commit details
    Browse the repository at this point in the history