From: Mike Christie <mchristi@redhat.com>
To: target-devel@vger.kernel.org
Subject: Re: tcmu-runner info
Date: Tue, 17 Apr 2018 16:43:40 +0000 [thread overview]
Message-ID: <5AD6243C.9000309@redhat.com> (raw)
In-Reply-To: <CALtL6BdjcZeqMQFmiLum3HR3MdAZieyBmiFRMYHgLzd22RmD5g@mail.gmail.com>
On 04/17/2018 09:54 AM, Raghuram Devarakonda wrote:
> I am working on a plugin based on tcmu-runner and would appreciate
> some help. I took the sample file plugin (file_example.c) and modified
> it. In my testing, I noticed that reads/writes to the TCMU device hang
> and in all these cases, tcmu-runner daemon crashed. I understand that
> the crashes are most probably due to the code I added but I am
> wondering if there is any way to prevent the hang. For example, is
> there a timeout in lio that would eventually fails the reads and
> writes?
Each tcmu device has a cmd_time_out attribute which is 30 seconds by
default. If we do not get a response within that time out the command
gets failed.
When runner restarts and when using 4.16, it will fail all out standing
commands in case you have cmd_time_out disabled.
>
> More over, any help in debugging crashes would also be greatly
> appreciated. It would be great if someone can share any pointers in
> working with tcmu-runner in general.
>
> Thanks for the help,
> Raghu
>
> PS. I hope this is the right mailing list for "tcmu-runner".
> --
> To unsubscribe from this list: send the line "unsubscribe target-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2018-04-17 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 14:54 tcmu-runner info Raghuram Devarakonda
2018-04-17 16:43 ` Mike Christie [this message]
2018-04-17 21:07 ` Raghuram Devarakonda
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=5AD6243C.9000309@redhat.com \
--to=mchristi@redhat.com \
--cc=target-devel@vger.kernel.org \
/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.