-
Notifications
You must be signed in to change notification settings - Fork 343
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
usbip: error: failed to record. out queue full. #16
Comments
@zjl-1991 : If you see the error message, some usb responses may be dropped. It's weird that USB device still worked correctly even with such an error. What kind of USB device did you test? And could you test by increasing a queue length? Please refer to #14 (comment) |
I use U-disk for testing. |
@zjl-1991 : USB disk had been tested successfully by many testers including me. Did you build vhci yourself or use binaries on release page ? |
@zjl-1991 Just to be sure so we can try to reproduce your setup, are you talking about a USB rotating disk, a USB flash disk or are you talking of a smartphone on which you turn on the UDISK feature? I'm asking because I've seen all these definitions for U-disk. |
I tested it with a USB flash disk, the vhci I used was compiled on Win7. |
@zjl-1991 Can you give us the USB flash disk model please? I'd like to know if this is the same as the one reported in issue #20 : Kingston Technology : DataTraveler G4 |
record_outq_seqnum() might be called multiple times. This case seems to happen more frequently under slow network. As the same sequence numbers were flooded into out queue slots, out queue became full. Quick remedy to this problem avoids marking duplicated sequence numbers. This commit resolves #20 and #16.
@zjl-1991 : Have you ever checked a recent usbip-win? |
I'll close, in hopes that this issue is resolved. |
usbip: error: failed to record. out queue full.
but It can be used normally.
On Windows 7
The text was updated successfully, but these errors were encountered: