From: Maurizio Lombardi <mlombard@redhat.com>
To: Forza <forza@tnonline.net>,
Mike Christie <michael.christie@oracle.com>,
target-devel@vger.kernel.org
Subject: Re: Stability of FILEIO as backing store?
Date: Tue, 2 Mar 2021 12:22:16 +0100 [thread overview]
Message-ID: <08682666-d350-6cbd-14e1-f550f49d75b6@redhat.com> (raw)
In-Reply-To: <2feabdd.b5c9def5.177ee7128e8@tnonline.net>
Hello, I'm trying to reproduce the problem you reported on Fedora 33
Dne 01. 03. 21 v 16:38 Forza napsal(a):
>
> Also, the "aio" attribute is different. Perhaps I set it manually in Fedora, but I cannot remember. It is not visible in /sys but is in the saveconfig.json.
> Ubuntu:
> "storage_objects": [
> {
> "aio": false,
> Fedora:
> "storage_objects": [
> {
> "aio": true,
>
> Does "aio" mean Async I/O in this case? I could not find any documentation for this attribute.
Yes, it means "async I/O" but I don't understand why it's set to true.
Looking at the rtslib/targetcli sources, aio by default is set to false and
it's not even possible to change it via targetcli.
You likely changed it manually in the saveconfig.json file.
Btw, there is a possible race condition in kernel versions < v5.12-rc1
when async i/o is enabled:
In the fd_execute_rw_aio() function, the bvec pointer is freed before the
async command is completed, might be the reason behind the disk corruptions?
This has been fixed with commit ecd7fba0ade1d6d8d49d320df9caf96922a376b2
Maurizio
prev parent reply other threads:[~2021-03-03 4:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 21:36 Stability of FILEIO as backing store? Forza
2021-02-25 22:09 ` Chaitanya Kulkarni
2021-02-25 22:20 ` Chaitanya Kulkarni
2021-02-26 3:41 ` michael.christie
2021-02-26 7:19 ` Forza
2021-02-26 16:12 ` Mike Christie
2021-03-01 15:38 ` Forza
2021-03-02 11:22 ` Maurizio Lombardi [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=08682666-d350-6cbd-14e1-f550f49d75b6@redhat.com \
--to=mlombard@redhat.com \
--cc=forza@tnonline.net \
--cc=michael.christie@oracle.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.