-
Notifications
You must be signed in to change notification settings - Fork 25
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
TLS messages lager than 14KB #53
Comments
Would you please provide the drive firmware version that caused the issue? |
model: ST4000NK001-1NX668 |
It is under review within the drive firmware team. Will update the status when there is a resolution. |
Minor remark: Setting the TCP sending buffer (kinetic_socket.c, line 101) to 14000 didn't impact the described behavior. |
@chiaming2000 Are there any news about the issue? |
Thanks for the message. Seagate firmware team is aware of the issue and will respond to this shortly. |
@rcrane I'm on the Kinetic firmware team and have replicated this bug on a 1st gen, 4TB Kinetic drive. I also confirmed that we have fixed this bug for our 2nd gen, 8TB Kinetic drive. Unfortunately, we no longer are supporting the 1st gen drive so we do not plan on providing a fix. |
It appears that the disk (not the simulator) is not able to handle write requests through TLS that are larger than 14427 bytes. The disk will terminate the session and reply with an operation failed error.
To demonstrate the issue and a workaround, I have created this repo:
https://github.com/rcrane/kinetic_tls_bug
Still puzzling is that writing an object of 15KB through TLS fails but continuously writing objects with increasing size (starting at sizes below 14KB) can circumvent the bug.
The text was updated successfully, but these errors were encountered: