From: Christoph Hellwig <hch@infradead.org>
To: Anton Brekhov <anton.brekhov@rsc-tech.ru>
Cc: linux-nvme@lists.infradead.org
Subject: Re: NVMe Over Fabrics Disconnect Kernel error
Date: Tue, 31 Mar 2020 06:26:32 -0700 [thread overview]
Message-ID: <20200331132632.GA9797@infradead.org> (raw)
In-Reply-To: <CABY-YC7eHFjb-TpKf2ioPJNhZ8RccYsrR-oU=wmt26z9AUNebg@mail.gmail.com>
On Sat, Mar 28, 2020 at 09:12:37AM +0300, Anton Brekhov wrote:
> Greetings!
>
> We're using nvme-cli technology with ZFS and Lustre Filesystem on top of it.
> But we constantly come across a kernel error while disconnecting
> remote disks from switched off nodes:
Which is totally your problem if you use out of tree modules that
violate licensing. *plonk*
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2020-03-31 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 6:12 NVMe Over Fabrics Disconnect Kernel error Anton Brekhov
2020-03-29 4:14 ` Sagi Grimberg
2020-03-29 8:50 ` Max Gurtovoy
2020-03-29 11:38 ` Anton Brekhov
2020-03-29 11:56 ` Max Gurtovoy
2020-03-29 14:40 ` Anton Brekhov
2020-03-30 4:38 ` Sagi Grimberg
2020-03-30 8:26 ` Anton Brekhov
2020-03-31 13:26 ` Christoph Hellwig [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=20200331132632.GA9797@infradead.org \
--to=hch@infradead.org \
--cc=anton.brekhov@rsc-tech.ru \
--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