* Namespaces on MZQL2960HCJR-00A07
@ 2021-10-09 8:53 Michael Fuckner
2021-10-11 19:12 ` Keith Busch
0 siblings, 1 reply; 4+ messages in thread
From: Michael Fuckner @ 2021-10-09 8:53 UTC (permalink / raw)
To: linux-nvme
I have a system with 2x PM9A3 (FW GDC5302Q) and nvme1 shall use namespacesfor testing.
I could use nvme detach-ns, delete-ns and create-ns, but it fails at attach-ns the new namespace to make it usable:
test135:~ # nvme id-ctrl /dev/nvme1|grep -e nn -e cntlid
cntlid : 0x6
nn : 32
test135:~ # nvme attach-ns /dev/nvme1 --namespace-id=1 -controllers=0x6
NVMe status: Controller List Invalid: The controller list provided contains invalid controller ids(0x211c)
Any idea how to attach this or other namespaces back so I can use the drive?
Regards,
Michael!
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Namespaces on MZQL2960HCJR-00A07
2021-10-09 8:53 Namespaces on MZQL2960HCJR-00A07 Michael Fuckner
@ 2021-10-11 19:12 ` Keith Busch
2021-10-12 8:28 ` Michael Fuckner
0 siblings, 1 reply; 4+ messages in thread
From: Keith Busch @ 2021-10-11 19:12 UTC (permalink / raw)
To: Michael Fuckner; +Cc: linux-nvme
On Sat, Oct 09, 2021 at 10:53:15AM +0200, Michael Fuckner wrote:
> I have a system with 2x PM9A3 (FW GDC5302Q) and nvme1 shall use namespacesfor testing.
>
> I could use nvme detach-ns, delete-ns and create-ns, but it fails at attach-ns the new namespace to make it usable:
>
> test135:~ # nvme id-ctrl /dev/nvme1|grep -e nn -e cntlid
> cntlid : 0x6
> nn : 32
> test135:~ # nvme attach-ns /dev/nvme1 --namespace-id=1 -controllers=0x6
The long options should use "--" rather than just the single "-". I'm
unsure if that changes the parsing, though.
> NVMe status: Controller List Invalid: The controller list provided contains invalid controller ids(0x211c)
>
> Any idea how to attach this or other namespaces back so I can use the drive?
Was the namespace attached to cntlid 0x6 prior to the detach/delete part
of the test?
When you created the namespace, did the output confirm the namespace was
created as nsid 1?
Is the namespace attached to any other controllers? You have to specify
multi-controller enabled when creating the namespace in that case.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Namespaces on MZQL2960HCJR-00A07
2021-10-11 19:12 ` Keith Busch
@ 2021-10-12 8:28 ` Michael Fuckner
2021-10-20 16:19 ` Michael Fuckner
0 siblings, 1 reply; 4+ messages in thread
From: Michael Fuckner @ 2021-10-12 8:28 UTC (permalink / raw)
To: Keith Busch; +Cc: linux-nvme
Hi,
On 11.10.21 21:12, Keith Busch wrote:
> On Sat, Oct 09, 2021 at 10:53:15AM +0200, Michael Fuckner wrote:
> The long options should use "--" rather than just the single "-". I'm
> unsure if that changes the parsing, though.
doesn't make a difference:
nvme attach-ns /dev/nvme7 -c 6 -n 1
NVMe status: Controller List Invalid: The controller list provided
contains invalid controller ids(0x211c)
> > Was the namespace attached to cntlid 0x6 prior to the detach/delete part
> of the test?
this is a similar system also all drives connected directly to EPYC
CPUs. This drive still has the default ns:
test220:~ # nvme id-ctrl /dev/nvme1
NVME Identify Controller:
vid : 0x144d
ssvid : 0x144d
sn : S64HNE0R902239
mn : SAMSUNG MZQL23T8HCLS-00A07
fr : GDC5302Q
rab : 2
ieee : 002538
cmic : 0
mdts : 9
cntlid : 0x6
ver : 0x10400
rtd3r : 0x7a1200
rtd3e : 0x7a1200
oaes : 0x300
ctratt : 0x80
rrls : 0
cntrltype : 1
fguid :
crdt1 : 0
crdt2 : 0
crdt3 : 0
oacs : 0x5f
acl : 7
aerl : 3
frmw : 0x17
lpa : 0xe
elpe : 63
npss : 1
avscc : 0x1
apsta : 0
wctemp : 353
cctemp : 356
mtfa : 0
hmpre : 0
hmmin : 0
tnvmcap : 3840755982336
unvmcap : 0
rpmbs : 0
edstt : 35
dsto : 1
fwug : 0
kas : 0
hctma : 0
mntmt : 0
mxtmt : 0
sanicap : 0x3
hmminds : 0
hmmaxd : 0
nsetidmax : 0
endgidmax : 0
anatt : 0
anacap : 0
anagrpmax : 0
nanagrpid : 0
pels : 0
sqes : 0x66
cqes : 0x44
maxcmd : 256
nn : 32
oncs : 0x5f
fuses : 0
fna : 0x4
vwc : 0x6
awun : 1023
awupf : 7
icsvscc : 1
nwpc : 0
acwu : 0
sgls : 0
mnan : 0
subnqn : nqn.1994-11.com.samsung:nvme:PM9A3:2.5-inch:S64HNE0R902239
ioccsz : 0
iorcsz : 0
icdoff : 0
fcatt : 0
msdbd : 0
ofcs : 0
ps 0 : mp:25.00W operational enlat:70 exlat:70 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:4.00W active_power:-
ps 1 : mp:8.00W operational enlat:70 exlat:70 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:4.00W active_power:-
test220:~ #
>
> When you created the namespace, did the output confirm the namespace was
> created as nsid 1?
yes, I can create and delete namespaces, but I can not attach them:
test220:~ # nvme create-ns /dev/nvme7 -s 26214387 -c 26214387 -b 4096
create-ns: Success, created nsid:1
test220:~ # nvme attach-ns /dev/nvme7 -n 1 -c 0x6
NVMe status: Controller List Invalid: The controller list provided
contains invalid controller ids(0x211c)
test220:~ # nvme delete-ns /dev/nvme7 -n 1
delete-ns: Success, deleted nsid:1
test220:~ #
> Is the namespace attached to any other controllers? You have to specify
> multi-controller enabled when creating the namespace in that case.
no, just 4 lanes from CPU to NVMe Drive.
Hope this helps,
Michael!
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: Namespaces on MZQL2960HCJR-00A07
2021-10-12 8:28 ` Michael Fuckner
@ 2021-10-20 16:19 ` Michael Fuckner
0 siblings, 0 replies; 4+ messages in thread
From: Michael Fuckner @ 2021-10-20 16:19 UTC (permalink / raw)
To: Keith Busch; +Cc: linux-nvme
> On 12/10/2021 10:28 Michael Fuckner <michael@fuckner.net> wrote:
> test220:~ # nvme create-ns /dev/nvme7 -s 26214387 -c 26214387 -b 4096
> create-ns: Success, created nsid:1
> test220:~ # nvme attach-ns /dev/nvme7 -n 1 -c 0x6
> NVMe status: Controller List Invalid: The controller list provided
> contains invalid controller ids(0x211c)
> test220:~ # nvme delete-ns /dev/nvme7 -n 1
> delete-ns: Success, deleted nsid:1
Hi,
got another drive to play with (Micron 7400) and I can use the nvme tool as expected- so I just consider Samsung Firmware broken?
ram1:~ # nvme create-ns /dev/nvme0 -s 26214387 -c 26214387 -b 4096 -dps 0 -nmic 0
create-ns: Success, created nsid:2
ram1:~ # nvme attach-ns /dev/nvme0 -n 2 -c 0
attach-ns: Success, nsid:2
ram1:~ # nvme list
Node SN Model Namespace Usage Format FW Rev
--------------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
nvme0n2 213331B0EE15 Micron_7400_MTFDKBG3T8TDZ 2 0.00 B / 107.37 GB 4 KiB + 0 B E1MU231W
nvme0n1 213331B0EE15 Micron_7400_MTFDKBG3T8TDZ 1 0.00 B / 107.37 GB 4 KiB + 0 B E1MU231W
ram1:~ #
Regards,
Michael!
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-10-20 16:19 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-09 8:53 Namespaces on MZQL2960HCJR-00A07 Michael Fuckner
2021-10-11 19:12 ` Keith Busch
2021-10-12 8:28 ` Michael Fuckner
2021-10-20 16:19 ` Michael Fuckner
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.