NVMe ketta kasutamine
Allikas: Imre kasutab arvutit
Mine navigeerimisribaleMine otsikasti
Sissejuhatus
Misc
- Võib olla on tark füüsilise seadme valikul arvestada kuidas kõnealune tootja jaga firmware uuendusi; nt Samsung paistab olevat asjalik -
Tööpõhimõte
TODO
- Töötab PCIe siinil, st on näha lspci väljundis
Misc
nvme utiilidi paigaldamiseks sobib öelda
# apt-get install nvme-cli
ja kasutamiseks nt
# nvme list Node SN Model Namespace Usage Format FW Rev ---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- -------- /dev/nvme0n1 50026B728245640E KINGSTON SKC2000M81000G 1 1.00 TB / 1.00 TB 512 B + 0 B S2780101 /dev/nvme1n1 S466NB0K423925X Samsung SSD 970 EVO 500GB 1 346.22 GB / 500.11 GB 512 B + 0 B 1B2QEXE7
Kingston KC2000
smartctl andmed
# smartctl -a /dev/nvme0n1 smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.3.13-3-pve] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: KINGSTON SKC2000M81000G Serial Number: 50026B728245640E Firmware Version: S2780101 PCI Vendor/Subsystem ID: 0x2646 IEEE OUI Identifier: 0x000000 Controller ID: 1 Number of Namespaces: 1 Namespace 1 Size/Capacity: 1,000,204,886,016 [1.00 TB] Namespace 1 Utilization: 0 Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 0026b7 28245640e5 Local Time is: Sat Feb 8 23:36:52 2020 EET Firmware Updates (0x14): 2 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Maximum Data Transfer Size: 64 Pages Warning Comp. Temp. Threshold: 75 Celsius Critical Comp. Temp. Threshold: 80 Celsius Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 9.00W - - 0 0 0 0 0 0 1 + 4.60W - - 1 1 1 1 0 0 2 + 3.80W - - 2 2 2 2 0 0 3 - 0.0450W - - 3 3 3 3 2000 2000 4 - 0.0040W - - 4 4 4 4 6000 8000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 0 1 - 4096 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 31 Celsius Available Spare: 100% Available Spare Threshold: 10% Percentage Used: 0% Data Units Read: 41,160 [21.0 GB] Data Units Written: 0 Host Read Commands: 117,206 Host Write Commands: 0 Controller Busy Time: 0 Power Cycles: 3 Power On Hours: 4 Unsafe Shutdowns: 1 Media and Data Integrity Errors: 0 Error Information Log Entries: 0 Warning Comp. Temperature Time: 0 Critical Comp. Temperature Time: 0 Error Information (NVMe Log 0x01, max 256 entries) No Errors Logged
Samsung SSD 970 EVO 500GB
Jõudlus
# dd if=/dev/nvme0n1 of=/dev/null bs=1M 476940+1 records in 476940+1 records out 500107862016 bytes (500 GB, 466 GiB) copied, 238.902 s, 2.1 GB/s
lspci väljundis
# lspci | grep -i nvme 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981
scsi seadmete nimekirjas
# lsscsi [2:0:0:0] disk ATA Samsung SSD 860 2B6Q /dev/sda [4:0:0:0] disk ATA Samsung SSD 860 2B6Q /dev/sdb [9:0:0:0] disk LIO-ORG iscsi_block_1 4.0 /dev/sdc [N:0:4:1] disk Samsung SSD 970 EVO 500GB__1 /dev/nvme0n1
Ketta smart info
# smartctl -a /dev/nvme0n1 smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.3.13-3-pve] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: Samsung SSD 970 EVO 500GB Serial Number: S466NB0K423925X Firmware Version: 1B2QEXE7 PCI Vendor/Subsystem ID: 0x144d IEEE OUI Identifier: 0x002538 Total NVM Capacity: 500,107,862,016 [500 GB] Unallocated NVM Capacity: 0 Controller ID: 4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 500,107,862,016 [500 GB] Namespace 1 Utilization: 354,080,468,992 [354 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 002538 5481b3e78b Local Time is: Sat Feb 8 18:03:58 2020 EET Firmware Updates (0x16): 3 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Maximum Data Transfer Size: 512 Pages Warning Comp. Temp. Threshold: 85 Celsius Critical Comp. Temp. Threshold: 85 Celsius Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 6.20W - - 0 0 0 0 0 0 1 + 4.30W - - 1 1 1 1 0 0 2 + 2.10W - - 2 2 2 2 0 0 3 - 0.0400W - - 3 3 3 3 210 1200 4 - 0.0050W - - 4 4 4 4 2000 8000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 35 Celsius Available Spare: 98% Available Spare Threshold: 10% Percentage Used: 2% Data Units Read: 186,789,370 [95.6 TB] Data Units Written: 34,224,216 [17.5 TB] Host Read Commands: 3,141,407,873 Host Write Commands: 1,500,589,648 Controller Busy Time: 7,275 Power Cycles: 78 Power On Hours: 8,920 Unsafe Shutdowns: 60 Media and Data Integrity Errors: 12 Error Information Log Entries: 13 Warning Comp. Temperature Time: 0 Critical Comp. Temperature Time: 0 Temperature Sensor 1: 35 Celsius Temperature Sensor 2: 37 Celsius Error Information (NVMe Log 0x01, max 64 entries) Num ErrCount SQId CmdId Status PELoc LBA NSID VS 0 13 7 0x0031 0x4502 0x000 98996012 1 -
Vead dmesg väljundis
[ 1121.232279] blk_update_request: critical medium error, dev nvme0n1, sector 98995200 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Vigu andva salvestusseadme asendamine töökorras seadmega
Lähtepunktiks on selline olukord
- arvutis on kahe füüsilise nvme seadme kasutamise võimalus
- arvutis on üks vigu andev füüsiline nvme seade
# dmesg .. [Sun Nov 21 19:40:34 2021] blk_update_request: critical medium error, dev nvme0n1, sector 1823429504 op 0x0:(READ) flags 0x0 phys_seg 45 prio class 0 [Sun Nov 21 19:40:34 2021] blk_update_request: critical medium error, dev nvme0n1, sector 1823429632 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 0 ...
- arvutis on üks töökorras füüsiline nvme seade
- vigu andev nvme seade on kasutusel raid mdadm ühe õlalises lülituses
- lisaks on kasutada veel üks töökorras nvme seade
Asendamise protseduur
- töökorras seade partitsioneeritake selliselt, et üks partitsioon on samasuguse suurusega kui vigu andva seadme mdadm partitsioon
- ühendada mirror kokku
- oodatakse kuni mdadm sünkroniseerib (osutub, et mdadm sünk läheb vigadest nö üle)
- eemaldadakse mirrorist vigu andnud seade
- lisatakse mirrorisse juurde töökorras teine nvme seade
Tulemusena on arvutis töökorras nvme põhine mdadm lülitus.
Sellise protseduuriga kaasneb huvitav nähtus, kui lugeda medium erroritele vastavaid kohti, siis paistavad nad töökorras ketastelt nii (antud juhul on see proxmox virtuaalsele arvutile vastav ressurss)
root@pm60-trt:~# dd if=/dev/pve_trt2/vm-169-disk-0 of=/dev/null bs=1M dd: error reading '/dev/pve_trt2/vm-169-disk-0': Input/output error 2246+1 records in 2246+1 records out 2355425280 bytes (2.4 GB, 2.2 GiB) copied, 2.1705 s, 1.1 GB/s
ja dmesg sissekanne
[Mon Nov 22 20:20:10 2021] Buffer I/O error on dev dm-15, logical block 575055, async page read [Mon Nov 22 20:20:10 2021] Buffer I/O error on dev dm-15, logical block 575055, async page read [Mon Nov 22 20:20:10 2021] Buffer I/O error on dev dm-15, logical block 575055, async page read
Kusjuures iseenesest saab vigadest lahti kirjutades vastavad plokid üle, nt
root@pm60-trt:~# dd of=/dev/pve_trt2/vm-169-disk-0 if=/dev/zero bs=1M dd: error writing '/dev/pve_trt2/vm-169-disk-0': No space left on device 65537+0 records in 65536+0 records out 68719476736 bytes (69 GB, 64 GiB) copied, 67.1265 s, 1.0 GB/s root@pm60-trt:~# dd if=/dev/pve_trt2/vm-169-disk-0 of=/dev/null bs=1M 65536+0 records in 65536+0 records out 68719476736 bytes (69 GB, 64 GiB) copied, 66.5542 s, 1.0 GB/s
Kui kõnealusest virtuaalsest arvutist on vaja andmeid kätte saada, sobib arvuti käivitada nt live linux cd pealt, monteerida failisüsteemid ja kopeerida mida saab; nt rsync paistab minevat ka vigadest mööda.
retimer adapteri kasutamine
Väited
- tundub, et nt 'AOC-SLG4-4E4T' seade ei paista iseseisva seadmena lspci väljundis
- lspci väljundis on paista retimer adapteri külge kinnitatud nvme seadmed
root@pve-wrx90e:~# lspci | grep -i micron c1:00.0 Non-Volatile memory controller: Micron Technology Inc 7450 PRO NVMe SSD (rev 01) c2:00.0 Non-Volatile memory controller: Micron Technology Inc 7450 PRO NVMe SSD (rev 01)
Salvestada igaks juhuks algne olukord
root@pve-wrx90e:~# smartctl -a /dev/nvme1n1 > smartctl-a-nvme1n1-20250315.orig root@pve-wrx90e:~# smartctl -a /dev/nvme1 > smartctl-a-nvme1-20250315.orig root@pve-wrx90e:~# nvme id-ctrl /dev/nvme1 -H > id-ctrl-nvme1-H-20250315.orig root@pve-wrx90e:~# nvme id-ctrl /dev/nvme1 > id-ctrl-nvme1-20250315.orig
Namespace seadistamine, küsida seadmega seotud controller id väärtust
root@pve-wrx90e:~# nvme id-ctrl /dev/nvme0 | grep ^cntlid cntlid : 0
Küsida seadmega seotud namespaceide väärtusid
root@pve-wrx90e:~# nvme list-ns /dev/nvme1 -a -o json
{
"nsid_list":[
{
"nsid":1
}
]
}
Küsida kogu ja kasutada olevaid mahte
root@pve-wrx90e:~# nvme id-ctrl /dev/nvme1 | grep mcap tnvmcap : 15,362,991,415,296 unvmcap : 15,362,991,415,296
namespace eemaldada kontrolleri küljest
root@pve-wrx90e:~# nvme detach-ns /dev/nvme1 -n 1 -c 0 detach-ns: Success, nsid:1
kustutada olemasolev namespace
root@pve-wrx90e:~# nvme delete-ns /dev/nvme1 -n 1 delete-ns: Success, deleted nsid:1
Tulemusena on kogu seadme ressurss kasutada
root@pve-wrx90e:~# nvme id-ctrl /dev/nvme1 | grep mcap tnvmcap : 15,362,991,415,296 unvmcap : 15,362,991,415,296
Moodustada 200G suurune nö operatsioonisüsteemi namespace
imre@moraal:~$ bc .. scale=2 200*1024^3 214748364800 ./512 419430400.00
ning ülejäänud ressurss andmete namespace
imre@moraal:~$ bc .. scale=2 .. 15362991415296/512 30005842608.00 .-419430400 29586412208.00 root@pve-wrx90e:~# nvme create-ns /dev/nvme1 --nsze=29586412208 --ncap=29586412208 -b 512 create-ns: Success, created nsid:2
Tulemusena
root@pve-wrx90e:~# nvme list /dev/nvme0 -v Subsystem Subsystem-NQN Controllers ---------------- ------------------------------------------------------------------------------------------------ ---------------- nvme-subsys2 nqn.1994-11.com.samsung:nvme:980PRO:M.2:S6P1NX0TA24974B nvme2 nvme-subsys1 nqn.2016-08.com.micron:nvme:nvm-subsystem-sn-25024DA4607E nvme1 nvme-subsys0 nqn.2016-08.com.micron:nvme:nvm-subsystem-sn-24484CBAC2EA nvme0 Device SN MN FR TxPort Address Subsystem Namespaces -------- -------------------- ---------------------------------------- -------- ------ -------------- ------------ ---------------- nvme2 S6P1NX0TA24974B Samsung SSD 970 EVO Plus 2TB 4B2QEXM7 pcie 0000:89:00.0 nvme-subsys2 nvme2n1 nvme1 25024DA4607E Micron_7450_MTFDKCC15T3TFR E2MU200 pcie 0000:c2:00.0 nvme-subsys1 nvme1n2, nvme1n1 nvme0 24484CBAC2EA Micron_7450_MTFDKCC15T3TFR E2MU200 pcie 0000:c1:00.0 nvme-subsys0 nvme0n2, nvme0n1 Device Generic NSID Usage Format Controllers ------------ ------------ -------- -------------------------- ---------------- ---------------- /dev/nvme2n1 /dev/ng2n1 1 992.50 GB / 2.00 TB 512 B + 0 B nvme2 /dev/nvme1n2 /dev/ng1n2 2 0.00 B / 15.15 TB 512 B + 0 B nvme1 /dev/nvme1n1 /dev/ng1n1 1 0.00 B / 214.75 GB 512 B + 0 B nvme1 /dev/nvme0n2 /dev/ng0n2 2 0.00 B / 15.15 TB 512 B + 0 B nvme0 /dev/nvme0n1 /dev/ng0n1 1 0.00 B / 214.75 GB 512 B + 0 B nvme0 root@pve-wrx90e:~# nvme id-ctrl /dev/nvme1 | grep mcap tnvmcap : 15,362,991,415,296 unvmcap : 0
Namespace
Misc
Üks tavalisel viisil kasutuses nvme seade paistab välja selline
root@pve-wrx90e:~# ls -ld /dev/nvme2* crw------- 1 root root 242, 2 Mar 15 14:40 /dev/nvme2 brw-rw---- 1 root disk 259, 2 Mar 15 14:40 /dev/nvme2n1 brw-rw---- 1 root disk 259, 3 Mar 15 14:40 /dev/nvme2n1p1 brw-rw---- 1 root disk 259, 4 Mar 15 14:40 /dev/nvme2n1p2 brw-rw---- 1 root disk 259, 5 Mar 15 14:40 /dev/nvme2n1p3 brw-rw---- 1 root disk 259, 6 Mar 15 14:40 /dev/nvme2n1p4
kus
- /dev/nvme2 on character seade
- namespace on plokkseade
- namespace sisse tehtud partitsioonid on plokkseadmed
Namespace omadusi saab küsida nt nii
root@pve-wrx90e:~# nvme id-ns /dev/nvme0n1 NVME Identify Namespace 1: nsze : 0x6fc7cd2b0 ncap : 0x6fc7cd2b0 nuse : 0 ...
Väited
- nvme namespace pakub nö õigema lahenduse kui seni on pakkunud partitsioon (nt namespace jaoks on isiklik submit ja completion queue jms)
- nvme namespace on füüsilise plokkseadme moodi ressurss kuna nt 'smartctl -a /dev/nvme0n1' ja 'smartclt -a /dev/nvme0n2' näitavad erinevaid mahte jms
namespace käsundamine
namespace võimekuse küsimine
root@pve-wrx90e:~# nvme id-ctrl /dev/nvme0 | grep ^nn nn : 132 root@pve-wrx90e:~# nvme id-ctrl /dev/nvme1 | grep ^nn nn : 132 root@pve-wrx90e:~# nvme id-ctrl /dev/nvme2 | grep ^nn nn : 1
namespace nimekirja küsimine
TODO
kustutamine
root@pve-wrx90e:~# nvme delete-ns /dev/nvme0 -n 1 delete-ns: Success, deleted nsid:1 root@pve-wrx90e:~# dmesg -T | tail -n 2 [Sat Mar 15 16:18:31 2025] Key type psk registered [Sat Mar 15 16:46:16 2025] nvme nvme0: rescanning namespaces.
Lähtepunktiks on et kõnealune nvme seade ei ole seotud ühegi namespace'iga
root@pve-wrx90e:~# nvme list-ns /dev/nvme0 -a -o json
{
"nsid_list":[
]
}
namespace tekitamiseks sobib öelda
root@pve-wrx90e:~# nvme create-ns /dev/nvme0 --nsze=419430400 --ncap=419430400 -b 512 create-ns: Success, created nsid:1 root@pve-wrx90e:~# nvme create-ns /dev/nvme0 --nsze=1677721600 --ncap=1677721600 -b 512 create-ns: Success, created nsid:2
attachimata aga olemasolevate namespace'ide nimekirja küsimine, võti -a
root@pve-wrx90e:~# nvme list-ns /dev/nvme0 -a -o json
{
"nsid_list":[
{
"nsid":1
},
{
"nsid":2
}
]
}
kusjuures, kuna nad pole attachitud siis nad ei esine 'nvme list -v' väljundis
root@pve-wrx90e:~# nvme list -v Subsystem Subsystem-NQN Controllers ---------------- ------------------------------------------------------------------------------------------------ ---------------- nvme-subsys2 nqn.1994-11.com.samsung:nvme:980PRO:M.2:S6P1NX0TA24974B nvme2 nvme-subsys1 nqn.2016-08.com.micron:nvme:nvm-subsystem-sn-25024DA4607E nvme1 nvme-subsys0 nqn.2016-08.com.micron:nvme:nvm-subsystem-sn-24484CBAC2EA nvme0 Device SN MN FR TxPort Address Subsystem Namespaces -------- -------------------- ---------------------------------------- -------- ------ -------------- ------------ ---------------- nvme2 S6P1NX0TA24974B Samsung SSD 970 EVO Plus 2TB 4B2QEXM7 pcie 0000:89:00.0 nvme-subsys2 nvme2n1 nvme1 25024DA4607E Micron_7450_MTFDKCC15T3TFR E2MU200 pcie 0000:c2:00.0 nvme-subsys1 nvme1n1 nvme0 24484CBAC2EA Micron_7450_MTFDKCC15T3TFR E2MU200 pcie 0000:c1:00.0 nvme-subsys0 Device Generic NSID Usage Format Controllers ------------ ------------ -------- -------------------------- ---------------- ---------------- /dev/nvme2n1 /dev/ng2n1 1 992.00 GB / 2.00 TB 512 B + 0 B nvme2 /dev/nvme1n1 /dev/ng1n1 1 419.43 GB / 15.36 TB 512 B + 0 B nvme1
attach kontrolleriga
root@pve-wrx90e:~# nvme attach-ns /dev/nvme0 -n 1 -c 0 attach-ns: Success, nsid:1 root@pve-wrx90e:~# nvme attach-ns /dev/nvme0 -n 2 -c 0 attach-ns: Success, nsid:2
tulemusena
root@pve-wrx90e:~# nvme list -v Subsystem Subsystem-NQN Controllers ---------------- ------------------------------------------------------------------------------------------------ ---------------- nvme-subsys2 nqn.1994-11.com.samsung:nvme:980PRO:M.2:S6P1NX0TA24974B nvme2 nvme-subsys1 nqn.2016-08.com.micron:nvme:nvm-subsystem-sn-25024DA4607E nvme1 nvme-subsys0 nqn.2016-08.com.micron:nvme:nvm-subsystem-sn-24484CBAC2EA nvme0 Device SN MN FR TxPort Address Subsystem Namespaces -------- -------------------- ---------------------------------------- -------- ------ -------------- ------------ ---------------- nvme2 S6P1NX0TA24974B Samsung SSD 970 EVO Plus 2TB 4B2QEXM7 pcie 0000:89:00.0 nvme-subsys2 nvme2n1 nvme1 25024DA4607E Micron_7450_MTFDKCC15T3TFR E2MU200 pcie 0000:c2:00.0 nvme-subsys1 nvme1n1 nvme0 24484CBAC2EA Micron_7450_MTFDKCC15T3TFR E2MU200 pcie 0000:c1:00.0 nvme-subsys0 nvme0n2, nvme0n1 Device Generic NSID Usage Format Controllers ------------ ------------ -------- -------------------------- ---------------- ---------------- /dev/nvme2n1 /dev/ng2n1 1 992.01 GB / 2.00 TB 512 B + 0 B nvme2 /dev/nvme1n1 /dev/ng1n1 1 419.43 GB / 15.36 TB 512 B + 0 B nvme1 /dev/nvme0n2 /dev/ng0n2 2 0.00 B / 858.99 GB 512 B + 0 B nvme0 /dev/nvme0n1 /dev/ng0n1 1 0.00 B / 214.75 GB 512 B + 0 B nvme0
kontrolleri id küsimine, seda väärtust sobib kasutada attach-ns jms käskude juures
root@pve-wrx90e:~# nvme id-ctrl /dev/nvme0 | grep ^cntlid cntlid : 0
Viimase namespace suuruse arvutamine
root@pve-wrx90e:~# nvme id-ctrl /dev/nvme0 | grep mcap tnvmcap : 15,362,991,415,296 unvmcap : 14,289,249,591,296
ning
imre@moraal:~$ bc scale=2 14289249591296/512 27908690608.00
ning moodustamiseks
root@pve-wrx90e:~# nvme create-ns /dev/nvme0 --nsze=27908690608 --ncap=27908690608 -b 512 create-ns: Success, created nsid:3
Kui proovida teha suuremat, siis
root@pve-wrx90e:~# nvme create-ns /dev/nvme0 --nsze=27908690609 --ncap=27908690609 -b 512 NVMe status: Namespace Insufficient Capacity: Creating the namespace requires more free space than is currently available(0x4115)
Kui proovida nö thin-provisioneerida, ei pruugi riistvara alati toetada
root@pve-wrx90e:~# nvme create-ns /dev/nvme0 --nsze=27824804529 --ncap=27824804520 -b 512 NVMe status: Thin Provisioning Not Supported: Thin provisioning is not supported by the controller(0x411b)
Millegipärast lsscsi ei esita nvme namespace puhul tulemust viisakalt, küllap sisuliselt ei ole probleeme
root@pve-svc-01:~# lsscsi -s [2:0:0:0] disk ATA CT4000MX500SSD1 045 /dev/sda 4.00TB [6:0:0:0] cd/dvd AMI Virtual CDROM0 1.00 /dev/sr0 1.07GB [7:0:0:0] disk AMI Virtual HDisk0 1.00 /dev/sdb - sdev_scandir_sort: left parse failed: nvme0n2 sdev_scandir_sort: left parse failed: nvme0n1 [N:0:0:1] disk Micron_7450_MTFDKCC15T3TFR__1 /dev/nvme0n1 214GB [N:0:0:2] disk Micron_7450_MTFDKCC15T3TFR__2 /dev/nvme0n2 7.69TB [N:0:0:3] disk Micron_7450_MTFDKCC15T3TFR__3 /dev/nvme0n3 7.45TB sdev_scandir_sort: left parse failed: nvme1n3 sdev_scandir_sort: left parse failed: nvme1n2 [N:1:0:2] disk Micron_7450_MTFDKCC15T3TFR__2 /dev/nvme1n2 7.69TB [N:1:0:3] disk Micron_7450_MTFDKCC15T3TFR__3 /dev/nvme1n3 7.45TB [N:1:0:1] disk Micron_7450_MTFDKCC15T3TFR__1 /dev/nvme1n1 214GB
Kasutusjuhtum - ceph
Väited
- mingitel andmetel on ceph puhul otstarbekas kasutada ühe füüsilise osd ketta kohta kahte namespace ressurssi
Kasulikud lisamaterjalid
- https://nvmexpress.org/resource/nvme-namespaces/
- https://www.youtube.com/watch?v=7MYw-0qfpH8 - 'Understanding NVMe Namespaces'
- https://www.drewthorst.com/posts/nvme/namespaces/readme/
- 'Under the Hood with NVMe over Fabrics' - https://www.snia.org/sites/default/files/DSI/2016/presentations/protocols/JMetz_Under_the_Hood_with_NVMe_over_Fabrics.pdf
- https://www.cnblogs.com/cobbliu/p/12975853.html
