Does the Seagate FireCuda 530 (2TB) support NVMe namespaces?

This drive looks cool but I’m trying to find out if I can create additional NVMe namespaces for managing storage for VMs. This doesn’t seem to be very easy information to locate! I can’t tell from the manual how many namespaces are supported.

I don’t have any NVMe drives at the moment so I can’t experiment with these commands, but it seems that running (on Linux, with nvme-cli):

nvme id-ctrl /dev/nvme0 | grep ^nn

will return the number of supported namespaces for a drive, at least according to:

If anyone has this drive and is happy to do a little investigation (or just know some other way I might find out) I’d really appreciate it.

Hi

No they don’t support namespaces.
root@zephir:~# nvme id-ctrl /dev/nvme0 | grep -E "^nn|^mn "
mn : Seagate FireCuda 530 ZP2000GM30013
nn : 1
root@zephir:~#

On the other hand the micron 7400 pro M.2 22110 supports nvme namespaces:
root@zephir:~# nvme id-ctrl /dev/nvme3 | grep -E "^nn|^mn "
mn : Micron_7400_MTFDKBG3T8TDZ
nn : 128
root@zephir:~#

3 Likes

Brilliant, that’s useful to me! Thanks a lot for checking @gysi :+1:

If I might hijack with a question -

Having a FireCuda 520 subject to this fine issue (abridged: fstrim impossibly slow) - have you experienced the same issue or anything objectionable on the 530 from Linux?

(let’s leave it implied that the fix was worse the problem, yet 530’s are still a better price than some)

Honestly I haven’t noticed anything, because it runs once a week in a background job.

But I just ran it:

root@zephir:~# time fstrim -v /
/: 125.3 GiB (134564364288 bytes) trimmed

real 0m22.585s
user 0m0.000s
sys 0m0.438s
root@zephir:~# lvs /dev/debian/root
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
root debian -wi-ao---- 279.39g
root@zephir:~#

1 Like

This topic was automatically closed 273 days after the last reply. New replies are no longer allowed.