* "nvme0c1n1: detected capacity change from 0 to 268435456000" message in controller reset @ 2017-11-15 21:10 Sagi Grimberg 2017-12-04 22:24 ` Christoph Hellwig 0 siblings, 1 reply; 3+ messages in thread From: Sagi Grimberg @ 2017-11-15 21:10 UTC (permalink / raw) I get this message when running nvme reset /dev/nvme0 ^ permalink raw reply [flat|nested] 3+ messages in thread
* "nvme0c1n1: detected capacity change from 0 to 268435456000" message in controller reset 2017-11-15 21:10 "nvme0c1n1: detected capacity change from 0 to 268435456000" message in controller reset Sagi Grimberg @ 2017-12-04 22:24 ` Christoph Hellwig 2017-12-05 7:30 ` Sagi Grimberg 0 siblings, 1 reply; 3+ messages in thread From: Christoph Hellwig @ 2017-12-04 22:24 UTC (permalink / raw) On Wed, Nov 15, 2017@11:10:50PM +0200, Sagi Grimberg wrote: > I get this message when running nvme reset /dev/nvme0 What's the exact setup? ^ permalink raw reply [flat|nested] 3+ messages in thread
* "nvme0c1n1: detected capacity change from 0 to 268435456000" message in controller reset 2017-12-04 22:24 ` Christoph Hellwig @ 2017-12-05 7:30 ` Sagi Grimberg 0 siblings, 0 replies; 3+ messages in thread From: Sagi Grimberg @ 2017-12-05 7:30 UTC (permalink / raw) >> I get this message when running nvme reset /dev/nvme0 > > What's the exact setup? Nothing special, just connect with a single fabrics controller (pick your favorite transport, I used loop) and just reset it. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-12-05 7:30 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2017-11-15 21:10 "nvme0c1n1: detected capacity change from 0 to 268435456000" message in controller reset Sagi Grimberg 2017-12-04 22:24 ` Christoph Hellwig 2017-12-05 7:30 ` Sagi Grimberg
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.