From: Bart Van Assche <bvanassche@acm.org>
To: Vincent Chen <vincent.chen@sifive.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Josef Bacik <josef@toxicpanda.com>
Subject: Re: [bug report] block nbd0: Unexpected reply (15) 000000009c07859b
Date: Mon, 20 May 2024 14:49:52 -0700 [thread overview]
Message-ID: <162da790-2824-4090-97a0-564c15ac793f@acm.org> (raw)
In-Reply-To: <CABvJ_xhqBRXPLvVDmKg9Jub7hc6vXE02S=iSR7RWW-a8UtU7WQ@mail.gmail.com>
On 5/12/24 18:59, Vincent Chen wrote:
> Thank you very much for providing the fixed patches. I applied them to my environment, but unfortunately, I still encountered similar issues.
>
> [ 96.784384] block nbd0: Double reply on req 00000000619eb9fb, cmd_cookie 51, handle cookie 49
> [ 96.847731] block nbd0: Dead connection, failed to find a fallback
> [ 96.848661] block nbd0: shutting down sockets
Hi Vincent,
That's unfortunate. Since the provided qemu command did not work on my setup,
I have tried to reproduce this issue as follows (in a VM):
modprobe brd
nbd-server 1234 /dev/ram0
nbd-client localhost 1234 /dev/nbd0
mkfs.ext4 /dev/nbd0
mount /dev/nbd0 /mnt
cd /mnt
stress-ng --seq 0 -t 60 --pathological --verbose --times --tz --metrics --hdd 4
I ran the above stress-ng command several times and every time I run that command
it succeeds. I'm not sure how to proceed since I cannot reproduce the reported
issue.
Thanks,
Bart.
prev parent reply other threads:[~2024-05-20 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 5:04 [bug report] block nbd0: Unexpected reply (15) 000000009c07859b Vincent Chen
2024-05-10 12:50 ` Jens Axboe
2024-05-10 20:51 ` Bart Van Assche
[not found] ` <CABvJ_xhqBRXPLvVDmKg9Jub7hc6vXE02S=iSR7RWW-a8UtU7WQ@mail.gmail.com>
2024-05-13 13:20 ` Bart Van Assche
2024-05-20 21:49 ` Bart Van Assche [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162da790-2824-4090-97a0-564c15ac793f@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=vincent.chen@sifive.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.