From: Tony Asleson <tasleson@redhat.com>
To: linux-nvme@lists.infradead.org
Subject: Re: nvmet: Kernel oops when doing mkfs on nvme-tcp device
Date: Mon, 23 Mar 2020 15:10:17 -0500 [thread overview]
Message-ID: <1c882509-0a76-81c3-76ca-eba67de2fe34@redhat.com> (raw)
In-Reply-To: <d09a86be-01eb-1665-d596-886beedf53b4@grimberg.me>
On 3/23/20 2:42 PM, Sagi Grimberg wrote:
>
>>> nvmet does support file backend, please have a look at blktests [1]
>>> under the test 025 in {BLKTEST_HOME}/tests/nvme about how to setup
>>> target with file backend.
>>
>> I created a sparse file and used nvmetcli to change device to the
>> specified file. I connected the client, ran dd and that worked fine. I
>> tried using mkfs.ext4 and I got the same kernel oops. Apparently it
>> doesn't matter if I use a file or device as the backing store for this
>> issue.
>
> Interesting, did you see the write_zeroes error though?
Yes, write zeros error is still present.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-03-23 20:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 21:36 nvmet: Kernel oops when doing mkfs on nvme-tcp device Tony Asleson
2020-03-20 22:23 ` Chaitanya Kulkarni
2020-03-20 23:24 ` Tony Asleson
2020-03-20 22:54 ` Sagi Grimberg
2020-03-20 22:59 ` Sagi Grimberg
2020-03-20 23:46 ` Tony Asleson
2020-03-21 0:43 ` Chaitanya Kulkarni
2020-03-23 17:56 ` Tony Asleson
2020-03-23 19:42 ` Sagi Grimberg
2020-03-23 20:10 ` Tony Asleson [this message]
2020-03-20 23:43 ` Tony Asleson
2020-03-23 8:33 ` Sagi Grimberg
2020-03-23 15:57 ` Tony Asleson
2020-03-23 19:41 ` Sagi Grimberg
2020-03-23 20:46 ` Chaitanya Kulkarni
2020-03-23 20:52 ` Sagi Grimberg
2020-03-23 22:02 ` Sagi Grimberg
2020-03-23 23:37 ` Tony Asleson
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=1c882509-0a76-81c3-76ca-eba67de2fe34@redhat.com \
--to=tasleson@redhat.com \
--cc=linux-nvme@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox