-
Notifications
You must be signed in to change notification settings - Fork 93
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
9.1.6 drbd_req_destroy: Logic BUG #27
Comments
Thanks for the report. What are the results of this test with DRBD 9.1.5 and 9.0.32? What load are you applying with fio? |
For the record, The disassembly around
|
One more test to perform would be blocking both directions with iptables. This is a particularly unusual test because the network connection is only broken in one direction. Try blocking both for comparison. |
fio cmdline:
(or randwrite, but that is going to ext4 inside a vm on this device) I tried the test again with blocking both directions. Read test resulted in the same outcome, but for the write test it's different, now there's an IO error reported to the application and a stuck request, but not the logic bug (this could be due to random chance, only tried it once):
Testing symmetric blocking with 9.1.5:
Read: same as before, IO error as soon as the second connection times out. Write: similar to 9.1.6, with IO error after nodeA reconnecting, but also the logic bug:
With 9.0.32 (only on nodeC, A/B are still 9.1.6): Read: as before, IO error on second disconnect Write: results in a kernel crash instead of complaining of logic bugs:
|
I would like to finish evaluating diskless mode, but unfortunately haven't gotten past the first test. Do you need any help fixing the bugs? |
Regarding the errors on read, it appears that Regarding the write errors, we have applied some fixes to the Also, you probably want to enable quorum, since you are configuring |
@koszik Please test again with |
Given that there has been no information to the contrary, I am assuming that this is fixed in |
I have two secondary nodes with disks (A, B) and one diskless node acting as primary, and I wanted to know what happens if the connection between C and A/B experiences a problem.
To test that, while sending requests to the device, I drop packets on node C going to A and then B as well, then re-enable the connections, like this:
Configuration:
When sending read requests, the result is drbd854: IO ERROR: neither local nor remote data, sector xxx, and it returns the error to fio (even though the configuration forbids that).
Using write requests, the logic BUG appears:
I can consistently reproduce these bugs.
The text was updated successfully, but these errors were encountered: