The Linux "Copy Problem" and the Mint desktop.

Chat about Linux in general
Forum rules
Do not post support questions here. Before you post read the forum rules. Topics in this forum are automatically closed 6 months after creation.
Post Reply
mattlach
Level 4
Level 4
Posts: 323
Joined: Mon May 30, 2011 8:34 pm

The Linux "Copy Problem" and the Mint desktop.

Post by mattlach »

Recently I copied a large file from one NVMe drive to another, and I happened to have htop open in a console window during the operation.

What I noticed was that nemo was using 86% of one core just for the copy process. This is on a Threadripper 3960x, so we are talking zen2 cores with a max boost of 4.5Ghz.
nemo.png
The load in htop is in red, which suggests that the problematic load is in kernel time.

(note that the load fluctuated up and down, but at one point it peaked at 86%, I just didn't capture it in the screenshot.

I thought "weird" there must be something going on with Nemo and googled for Nemo and CPU use. IN the process I decided to do a comparison with cp.

Using cp with the same file copy was even worse:
cp.png
cp is pinning one CPU core at 100%.

Just like with nemo, the problematic load is still in kernel time.

In other words, copying large files from one fast drive to another fast drive is not drive speed limited, but rather it is CPU limited.

This - I thought - cannot be right. A modern CPU should always be faster than NVRAM.

I decided to do a speed test. Copying my 64.1GB (64,080,576,512 bytes) file from my 800GB Optane 905 to my 2TB Samsung 990 Pro completed in ~42 seconds. An average of ~1.53 GB/s

The drives are definitely capable of much more, and on this previous generation but still rather fast CPU, I am CPU limited in copying files at about 1.53GB/s.

This just doesn't seem right.

I did some googling, and came across this article from 2019 on LWN:
https://lwn.net/Articles/789623/

This article (or well, minutes from some sort of conference discussion) seems to suggest that it is a multifaceted issue with many disparate causes both in userspace and in the kernel. It looks like file operations are using lots of CPU and are otherwise not well designed for our era of fast NVMe storage, which is a little shocking considering NVMe storage has been around for almost a decade at this point, and in client machines at least since ~2015 for early adopters of drives like Intels SSD750 series.

Nemo appears to be trying to be smart, and distributing the load across more threads than the cp command does, but even so, copying the same file took 50 seconds this time, averaging about 1.28GB/s. There may just be other aspects loading up sdeparate threads at the same time the file copy is ongoing though.

I have a few questions for those who know more about this than I do:

1.) Is this a real Linux-wide problem, or something specific somehow to my machine?
2.) Is anyone working on fixing it?
3.) Is my issue typical or worse than average?
4.) Could the NVMe driver just be poorly written, or is this more directly related to the code in the copy operations themselves?
5.) Are there any known workarounds until this issue is fixed?

It seems like the issue is:
1.) Across multiple programs uin kernel as well as userspace, and throughout binutils, applications that rely on them, as well as applications that try to do their own thing.

2.) Can be mitigated somewhat through threading operations. parcp is mentioned in the link above. But it would seem that multithreading it - while great in our modern area where even modest machines have 8C/16T would just be masking the problem.

3.) The real problem seems to be that basic parts of the Linux system were designed in an era when NVRAM was really slow, and optimizing for CPU performance was more or less irrelevant, as it would never pose a significant load. In the era of common relatively inexpensive consumer drives having sequential write speeds over 10GB/s many of these old assumptions might need to be revisited.


As an interesting aside, I did the same file copy test, but this time over a 10gig Intel x520 NIC using NFS to a mount on my NAS server. File transfer speeds averaged about 1100MB/s, with similar CPU loads on the client side.

On the server side however, writing straight from NFS to ZFS on the server, CPU load was very low, and very well distributed between its many cores, which is amusing, because ZFS is calculating checksums for every block (dual RAIDz2 vdevs in ZFS equivalent RAID60 configuration) and also running compression on every block, something which isnt being done on the client machine. One would expect the CPU load from this operation to be HIGHER on the server, but it isn't.

Not sure if we have how NFS works or how ZFS works to be thankful for this.





My workstation particulars for reference:

24C/48T Threadripper 3960x with SMT disabled. Base clock 3800Mhz, Max boost clock 4500Mhz.
64GB DDR4-3600 Udimm (not ECC)

Code: Select all

$ sudo inxi -v8
System:
  Host: matt-desktop Kernel: 6.5.0-15-generic x86_64 bits: 64 compiler: N/A
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
    root=UUID=removed ro quiet splash
  Desktop: Cinnamon 5.8.4 tk: GTK 3.24.33 wm: muffin dm: LightDM 1.30.0
    Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
  Mobo: ASUSTeK model: ROG ZENITH II EXTREME ALPHA v: Rev 1.xx
    serial: sanitized UEFI: American Megatrends v: 1701 date: 12/13/2022
Battery:
  Message: No system battery data found. Is one present?
Memory:
  RAM: total: 62.63 GiB used: 3.49 GiB (5.6%)
  Array-1: capacity: 512 GiB slots: 8 EC: None max-module-size: 64 GiB
    note: est.
  Device-1: DIMM 0 size: No Module Installed
  Device-2: DIMM 1 size: 16 GiB speed: 3600 MT/s type: DDR4
    detail: synchronous unbuffered (unregistered) bus-width: 64 bits
    total: 64 bits manufacturer: G-Skill part-no: F4-3600C16-16GVKC
    serial: N/A
  Device-3: DIMM 0 size: No Module Installed
  Device-4: DIMM 1 size: 16 GiB speed: 3600 MT/s type: DDR4
    detail: synchronous unbuffered (unregistered) bus-width: 64 bits
    total: 64 bits manufacturer: G-Skill part-no: F4-3600C16-16GVKC
    serial: N/A
  Device-5: DIMM 0 size: No Module Installed
  Device-6: DIMM 1 size: 16 GiB speed: 3600 MT/s type: DDR4
    detail: synchronous unbuffered (unregistered) bus-width: 64 bits
    total: 64 bits manufacturer: G-Skill part-no: F4-3600C16-16GVKC
    serial: N/A
  Device-7: DIMM 0 size: No Module Installed
  Device-8: DIMM 1 size: 16 GiB speed: 3600 MT/s type: DDR4
    detail: synchronous unbuffered (unregistered) bus-width: 64 bits
    total: 64 bits manufacturer: G-Skill part-no: F4-3600C16-16GVKC
    serial: N/A
PCI Slots:
  Slot: 0 type: x16 PCI Express PCIEX16_1 status: In Use length: Long
  Slot: 1 type: x8 PCI Express PCIEX16_2 status: In Use length: Long
  Slot: 2 type: x16 PCI Express PCIEX16_3 status: In Use length: Long
  Slot: 3 type: x8 PCI Express PCIEX16_4 status: In Use length: Long
CPU:
  Info: model: AMD Ryzen Threadripper 3960X socket: SP3r2 (sTRX4) note: check
    bits: 64 type: MCP arch: Zen 2 family: 0x17 (23) model-id: 0x31 (49)
    stepping: 0 microcode: 0x830107A
  Topology: cpus: 1x cores: 24 smt: <unsupported> cache: L1: 1.5 MiB
    desc: d-24x32 KiB; i-24x32 KiB L2: 12 MiB desc: 24x512 KiB L3: 128 MiB
    desc: 8x16 MiB
  Speed (MHz): avg: 2266 high: 3800 min/max: 2200/3800 boost: enabled
    base/boost: 3800/4550 scaling: driver: acpi-cpufreq governor: schedutil
    volts: 1.1 V ext-clock: 100 MHz cores: 1: 3800 2: 2200 3: 2200 4: 2200
    5: 2200 6: 2200 7: 2200 8: 2200 9: 2200 10: 2200 11: 2200 12: 2200
    13: 2200 14: 2200 15: 2200 16: 2200 17: 2200 18: 2200 19: 2200 20: 2200
    21: 2200 22: 2200 23: 2200 24: 2200 bogomips: 182064
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid
    f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibs
    irperf lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe
    msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae
    pat pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb
    pfthreshold pge pni popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a
    rdtscp rep_good sep sev sev_es sha_ni skinit smap smca smep ssbd sse sse2
    sse4_1 sse4_2 sse4a ssse3 stibp succor svm svm_lock syscall tce topoext
    tsc tsc_scale umip v_spec_ctrl v_vmsave_vmload vgif vmcb_clean vme
    vmmcall wbnoinvd wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT disabled
  Type: spec_rstack_overflow mitigation: SMT disabled
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP:
    disabled, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA vendor: Micro-Star MSI driver: nvidia v: 545.29.06
    alternate: nvidiafb,nouveau,nvidia_drm pcie: gen: 1 speed: 2.5 GT/s
    lanes: 16 link-max: gen: 4 speed: 16 GT/s ports: active: none
    off: DP-1,DP-2,HDMI-A-1 empty: DP-3 bus-ID: 01:00.0 chip-ID: 10de:2684
    class-ID: 0300
  Display: server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 6240x2160 s-dpi: 95 s-size: 1669x578mm (65.7x22.8")
    s-diag: 1766mm (69.5")
  Monitor-1: DP-0 pos: right res: 1200x1920 hz: 60 dpi: 94
    size: 324x518mm (12.8x20.4") diag: 611mm (24.1")
  Monitor-2: DP-2 pos: primary,left res: 1200x1920 hz: 60 dpi: 94
    size: 324x518mm (12.8x20.4") diag: 611mm (24.1")
  Monitor-3: HDMI-0 pos: primary,center res: 3840x2160 dpi: 61
    size: 1600x900mm (63.0x35.4") diag: 1836mm (72.3")
  OpenGL: renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
    v: 4.6.0 NVIDIA 545.29.06 direct render: Yes
Audio:
  Device-1: NVIDIA vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:22ba
    class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: N/A
    alternate: snd_hda_intel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 24:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Schiit Audio Bifrost 2 Unison USB type: USB
    driver: snd-usb-audio bus-ID: 3-1.2:4 chip-ID: 30be:1000 class-ID: 0102
  Sound Server-1: ALSA v: k6.5.0-15-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Aquantia AQC107 NBase-T/IEEE 802.3bz Ethernet [AQtion]
    vendor: ASUSTeK driver: atlantic v: kernel pcie: gen: 3 speed: 8 GT/s
    lanes: 2 link-max: lanes: 4 port: N/A bus-ID: 45:00.0 chip-ID: 1d6a:07b1
    class-ID: 0200
  IF: enp69s0 state: up speed: 10000 Mbps duplex: full
    mac: 24:4b:fe:57:e9:2c
  IP v4: sybnet2sanitized type: noprefixroute scope: global
    broadcast: subnet2sanitized
  IP v6: fe80::264b:feff:fe57:e92c/64 scope: link
  Device-2: Intel 82599ES 10-Gigabit SFI/SFP+ Network driver: ixgbe
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 8 port: c020 bus-ID: 4b:00.0
    chip-ID: 8086:10fb class-ID: 0200
  IF: enp75s0f0 state: up speed: 10000 Mbps duplex: full
    mac: 90:e2:ba:13:11:c8
  IP v4: subnet1sanitized type: noprefixroute scope: global
    broadcast:  subnet1sanitized
  IP v6: fe80::92e2:baff:fe13:11c8/64 scope: link
  Device-3: Intel 82599ES 10-Gigabit SFI/SFP+ Network driver: ixgbe
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 8 port: c000 bus-ID: 4b:00.1
    chip-ID: 8086:10fb class-ID: 0200
  IF: enp75s0f1 state: down mac: 90:e2:ba:13:11:c9
  IF-ID-1: virbr0 state: down mac: 52:54:00:44:7e:93
  IP v4: 192.168.122.1/24 scope: global broadcast: 192.168.122.255
  WAN IP: ;; Connection to 193.108.88.1#53(193.108.88.1) for
    whoami.akamai.net failed: timed out.
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 7.24 TiB used: 777.51 GiB (10.5%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 type: SSD serial: sanitized rev: 4B2QJXD7 temp: 48.9 C
    scheme: GPT
  SMART: yes health: PASSED on: 6d 1h cycles: 230
    read-units: 15,017,139 [7.68 TB] written-units: 14,145,552 [7.24 TB]
  ID-2: /dev/nvme1n1 maj-min: 259:11 vendor: Samsung model: SSD 980 PRO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 type: SSD serial: sanitized rev: 5B2QGXA7 temp: 40.9 C
    scheme: MBR
  SMART: yes health: PASSED on: 19d 4h cycles: 609
    read-units: 27,317,214 [13.9 TB] written-units: 23,211,431 [11.8 TB]
  ID-3: /dev/nvme2n1 maj-min: 259:12 vendor: Samsung model: SSD 970 EVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B
    speed: 31.6 Gb/s lanes: 4 type: SSD serial: sanitized rev: 2B2QEXE7
    temp: 38.9 C scheme: MBR
  SMART: yes health: PASSED on: 25d 16h cycles: 1,587
    read-units: 22,084,842 [11.3 TB] written-units: 34,916,759 [17.8 TB]
  ID-4: /dev/nvme3n1 maj-min: 259:5 vendor: Intel model: SSDPE21D960GA
    size: 894.25 GiB block-size: physical: 512 B logical: 512 B
    speed: 31.6 Gb/s lanes: 4 type: SSD serial: sanitized
    rev: E2010603 temp: 46.9 C scheme: GPT
  SMART: yes health: PASSED on: 36d 3h cycles: 82
    read-units: 5,568,388 [2.85 TB] written-units: 5,850,149 [2.99 TB]
  ID-5: /dev/nvme4n1 maj-min: 259:1 vendor: Samsung model: SSD 990 PRO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 type: SSD serial: sanitized rev: 4B2QJXD7 temp: 46.9 C
    scheme: MBR
  SMART: yes health: PASSED on: 5d 18h cycles: 230
    read-units: 29,074,582 [14.8 TB] written-units: 12,542,854 [6.42 TB]
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 400.02 GiB size: 392.67 GiB (98.16%)
    used: 266.45 GiB (67.9%) fs: ext4 block-size: 4096 B dev: /dev/nvme3n1p5
    maj-min: 259:10 label: N/A uuid: removed
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 32.5 MiB (33.8%) fs: vfat block-size: 512 B dev: /dev/nvme3n1p1
    maj-min: 259:6 label: N/A uuid: removed
  ID-3: /home/matt/Documents/Docs raw-size: N/A size: 62.23 TiB
    used: 1.45 TiB (2.3%) fs: nfs4 remote: subnet2sanitized:/zfshome/matt
  ID-4: /media/matt/Samsung 990 Pro 2 raw-size: 1.82 TiB
    size: 1.82 TiB (100.00%) used: 511.03 GiB (27.4%) fs: ntfs
    block-size: 4096 B dev: /dev/nvme4n1p1 maj-min: 259:2
    label: Samsung 990 Pro 2 uuid: removed
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/nvme0n1p1 maj-min: 259:3 size: 16 MiB fs: N/A label: N/A
    uuid: N/A
  ID-2: /dev/nvme0n1p2 maj-min: 259:4 size: 1.82 TiB fs: ntfs
    label: Samsung 990 Pro 1 uuid: removed
  ID-3: /dev/nvme1n1p1 maj-min: 259:13 size: 1.82 TiB fs: ntfs
    label: Samsung 980 Pro uuid: removed
  ID-4: /dev/nvme2n1p1 maj-min: 259:14 size: 931.51 GiB fs: ntfs
    label: Samsung 970 Evo uuid: removed
  ID-5: /dev/nvme3n1p2 maj-min: 259:7 size: 16 MiB fs: N/A label: N/A
    uuid: N/A
  ID-6: /dev/nvme3n1p3 maj-min: 259:8 size: 493.49 GiB fs: ntfs
    label: Optane 905p uuid: removed
  ID-7: /dev/nvme3n1p4 maj-min: 259:9 size: 641 MiB fs: ntfs label: N/A
    uuid: removed
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 2-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-4: 3-1:2 info: StarTech.com USB 2.0 HUB ports: 4 rev: 2.1
    speed: 480 Mb/s chip-ID: 14b0:0136 class-ID: 0900
  Hub-5: 3-1.1:3 info: Genesys Logic Hub ports: 4 rev: 2.1 speed: 480 Mb/s
    chip-ID: 05e3:0610 class-ID: 0900
  Hub-6: 3-1.1.1:5 info: Realtek RTS5411 Hub ports: 5 rev: 2.1
    speed: 480 Mb/s chip-ID: 0bda:5411 class-ID: 0900
  Hub-7: 3-1.1.4:7 info: Genesys Logic Hub ports: 4 rev: 2.1
    speed: 480 Mb/s power: 100mA chip-ID: 05e3:0610 class-ID: 0900
  Device-1: 3-1.2:4 info: Schiit Audio Bifrost 2 Unison USB type: Audio
    driver: snd-usb-audio interfaces: 2 rev: 2.0 speed: 480 Mb/s power: 100mA
    chip-ID: 30be:1000 class-ID: 0102
  Device-2: 3-1.3:6 info: Logitech MX518 Gaming Mouse type: Mouse,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s
    power: 300mA chip-ID: 046d:c08e class-ID: 0300 serial: sanitized
  Device-3: 3-1.4:8 info: Microdia USB Keyboard type: Keyboard,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 12 Mb/s
    power: 500mA chip-ID: 0c45:7691 class-ID: 0300
  Hub-8: 4-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 20 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-9: 4-1:2 info: StarTech.com USB 3.1 Gen 2 HUB ports: 4 rev: 3.2
    speed: 5 Gb/s chip-ID: 14b0:012d class-ID: 0900
  Hub-10: 4-1.1:3 info: Genesys Logic USB3.2 Hub ports: 4 rev: 3.2
    speed: 10 Gb/s chip-ID: 05e3:0625 class-ID: 0900
  Hub-11: 4-1.1.1:4 info: Realtek Hub ports: 4 rev: 3.2 speed: 5 Gb/s
    chip-ID: 0bda:0411 class-ID: 0900
  Hub-12: 4-1.1.4:5 info: Genesys Logic USB3.1 Hub ports: 4 rev: 3.2
    speed: 5 Gb/s chip-ID: 05e3:0626 class-ID: 0900
  Hub-13: 5-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-14: 6-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-15: 7-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 7-1:2 info: Cyber Power System PR1500LCDRT2U UPS type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 2mA
    chip-ID: 0764:0601 class-ID: 0300 serial: sanitized
  Hub-16: 7-5:3 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s
    power: 100mA chip-ID: 05e3:0610 class-ID: 0900
  Device-1: 7-5.1:4 info: MCT Elektronikladen aquaero type: Keyboard,HID
    driver: aquacomputer_d5next,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s
    power: 100mA chip-ID: 0c70:f001 class-ID: 0300 serial: sanitized
  Device-2: 7-5.2:5 info: MCT Elektronikladen aquaero type: Keyboard,HID
    driver: aquacomputer_d5next,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s
    power: 100mA chip-ID: 0c70:f001 class-ID: 0300 serial: sanitized
  Device-3: 7-5.3:6 info: ASUSTek AURA LED Controller type: HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s
    power: 16mA chip-ID: 0b05:18f3 class-ID: 0300 serial: sanitized
  Device-4: 7-5.4:7 info: ASUSTek AURA LED Controller type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s
    power: 500mA chip-ID: 0b05:18bb class-ID: 0300 serial: sanitized
  Hub-17: 8-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-18: 9-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-19: 9-3:2 info: ASMedia ASM1074 High-Speed hub ports: 4 rev: 2.1
    speed: 480 Mb/s power: 100mA chip-ID: 174c:2074 class-ID: 0900
  Hub-20: 9-4:3 info: ASMedia ASM1074 High-Speed hub ports: 4 rev: 2.1
    speed: 480 Mb/s power: 100mA chip-ID: 174c:2074 class-ID: 0900
  Hub-21: 10-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-22: 10-3:2 info: ASMedia ASM1074 SuperSpeed hub ports: 4 rev: 3.0
    speed: 5 Gb/s power: 8mA chip-ID: 174c:3074 class-ID: 0900
  Hub-23: 10-4:3 info: ASMedia ASM1074 SuperSpeed hub ports: 4 rev: 3.0
    speed: 5 Gb/s power: 8mA chip-ID: 174c:3074 class-ID: 0900
Sensors:
  System Temperatures: cpu: 42.0 C mobo: 36.0 C gpu: nvidia temp: 27 C
  Fan Speeds (RPM): cpu: 0 gpu: nvidia fan: 0%
Repos:
  Packages: apt: 2725 lib: 1443
  No active apt repos in: /etc/apt/sources.list
  No active apt repos in: /etc/apt/sources.list.d/google-chrome.list
  Active apt repos in: /etc/apt/sources.list.d/graphics-drivers-ppa-jammy.list
    1: deb [signed-by=/etc/apt/keyrings/graphics-drivers-ppa-jammy.gpg] https://ppa.launchpadcontent.net/graphics-drivers/ppa/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/maarten-fonville-android-studio-jammy.list
    1: deb [signed-by=/etc/apt/keyrings/maarten-fonville-android-studio-jammy.gpg] https://ppa.launchpadcontent.net/maarten-fonville/android-studio/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http://packages.linuxmint.com victoria main upstream import backport
    2: deb http://archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http://archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http://archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main
  Active apt repos in: /etc/apt/sources.list.d/spotify.list
    1: deb http://repository.spotify.com stable non-free
  Active apt repos in: /etc/apt/sources.list.d/virtualbox.org.list
    1: deb [arch=amd64] http://download.virtualbox.org/virtualbox/debian jammy non-free contrib
  Active apt repos in: /etc/apt/sources.list.d/x2go-stable-jammy.list
    1: deb [arch=amd64 signed-by=/etc/apt/keyrings/x2go-stable-jammy.gpg] https://ppa.launchpadcontent.net/x2go/stable/ubuntu jammy main
Processes:
  CPU top: 5 of 430
  1: cpu: 6.0% command: firefox pid: 4956 mem: 582.2 MiB (0.9%)
  2: cpu: 5.2% command: nemo pid: 9245 mem: 88.4 MiB (0.1%)
  3: cpu: 2.5% command: firefox-bin pid: 9450 mem: 155.1 MiB (0.2%)
  4: cpu: 1.2% command: cinnamon pid: 4705 mem: 398.7 MiB (0.6%)
  5: cpu: 0.6% command: [kworker/u256:4+ixgbe] pid: 8967
    mem: 0.00 MiB (0.0%)
  Memory top: 5 of 430
  1: mem: 582.2 MiB (0.9%) command: firefox pid: 4956 cpu: 6.0%
  2: mem: 398.7 MiB (0.6%) command: cinnamon pid: 4705 cpu: 1.2%
  3: mem: 266.4 MiB (0.4%) command: firefox-bin pid: 5135 cpu: 0.1%
  4: mem: 189.8 MiB (0.2%) command: xorg pid: 1412 cpu: 0.5%
  5: mem: 188.7 MiB (0.2%) command: firefox-bin pid: 7533 cpu: 0.3%
Info:
  Processes: 430 Uptime: 3h 17m wakeups: 0 Init: systemd v: 249 runlevel: 5
  tool: systemctl Compilers: gcc: 11.4.0 alt: 11/12/9 Shell: Sudo (sudo)
  v: 1.9.9 default: Bash v: 5.1.16 running-in: gnome-terminal inxi: 3.3.13
My server particulars:
32C/64T Epyc 7543, Zen 3, base 2800Mhz, Boost 3700Mhz
512GB DDR4-3200 RDIMM's

Code: Select all

# zpool status
 state: ONLINE
  scan: scrub repaired 0B in 10:02:09 with 0 errors on Sun Nov 12 10:26:14 2023
config:

    NAME                                               STATE        READ  WRITE CKSUM
    pool                                               ONLINE       0     0     0
      raidz2-0                                         ONLINE       0     0     0
        Seagate Exos X18 16TB                          ONLINE       0     0     0
        Seagate Exos X18 16TB                          ONLINE       0     0     0
        Seagate Exos X18 16TB                          ONLINE       0     0     0
        Seagate Exos X18 16TB                          ONLINE       0     0     0
        Seagate Exos X18 16TB                          ONLINE       0     0     0
        Seagate Exos X18 16TB                          ONLINE       0     0     0
      raidz2-1                                         ONLINE       0     0     0
        Seagate Exos X18 16TB                          ONLINE       0     0     0
        Seagate Exos X18 16TB                          ONLINE       0     0     0
        Seagate Exos X18 16TB                          ONLINE       0     0     0
        Seagate Exos X18 16TB                          ONLINE       0     0     0
        Seagate Exos X18 16TB                          ONLINE       0     0     0
        Seagate Exos X18 16TB                          ONLINE       0     0     0
    special  
      mirror-4                                         ONLINE       0     0     0
        Inland Premium NVMe 2TB                        ONLINE       0     0     0
        Inland Premium NVMe 2TB                        ONLINE       0     0     0
        Inland Premium NVMe 2TB                        ONLINE       0     0     0
    logs  
      mirror-3                                         ONLINE       0     0     0
        Intel 280GB Optane 900p                        ONLINE       0     0     0
        Intel 280GB Optane 900p                        ONLINE       0     0     0
    cache
        WD Black SN850X 4TB                             ONLINE       0     0     0
        WD Black SN850X 4TB                             ONLINE       0     0     0

errors: No known data errors

Code: Select all

# inxi -v8
System:
  Host: proxmox Kernel: 6.5.11-7-pve arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: initrd=\EFI\proxmox\6.5.11-7-pve\initrd.img-6.5.11-7-pve root=ZFS=rpool/ROOT/pve-1
    boot=zfs
  Console: pty pts/0 Distro: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Server System: Supermicro product: Super Server v: 0123456789 serial: 0123456789 Chassis:
    type: 17 v: 0123456789 serial: 0123456789
  Mobo: Supermicro model: H12SSL-NT v: 1.02 serial: sanitized UEFI: American Megatrends
    v: 2.7 date: 10/25/2023
Battery:
  Message: No system battery data found. Is one present?
Memory:
  RAM: total: 503.5 GiB used: 401.35 GiB (79.7%)
  Array-1: capacity: 4 TiB note: check slots: 8 EC: Multi-bit ECC max-module-size: 512 GiB
    note: est.
  Device-1: DIMMA1 type: DDR4 detail: synchronous registered (buffered) size: 64 GiB
    speed: 3200 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits): data: 64 total: 72
    manufacturer: SK Hynix part-no: HMAA8GR7CJR4N-XN serial: sanitized
  Device-2: DIMMB1 type: DDR4 detail: synchronous registered (buffered) size: 64 GiB
    speed: 3200 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits): data: 64 total: 72
    manufacturer: SK Hynix part-no: HMAA8GR7CJR4N-XN serial: sanitized
  Device-3: DIMMC1 type: DDR4 detail: synchronous registered (buffered) size: 64 GiB
    speed: 3200 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits): data: 64 total: 72
    manufacturer: SK Hynix part-no: HMAA8GR7CJR4N-XN serial: sanitized
  Device-4: DIMMD1 type: DDR4 detail: synchronous registered (buffered) size: 64 GiB
    speed: 3200 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits): data: 64 total: 72
    manufacturer: SK Hynix part-no: HMAA8GR7CJR4N-XN serial: sanitized
  Device-5: DIMME1 type: DDR4 detail: synchronous registered (buffered) size: 64 GiB
    speed: 3200 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits): data: 64 total: 72
    manufacturer: SK Hynix part-no: HMAA8GR7CJR4N-XN serial: sanitized
  Device-6: DIMMF1 type: DDR4 detail: synchronous registered (buffered) size: 64 GiB
    speed: 3200 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits): data: 64 total: 72
    manufacturer: SK Hynix part-no: HMAA8GR7CJR4N-XN serial: sanitized
  Device-7: DIMMG1 type: DDR4 detail: synchronous registered (buffered) size: 64 GiB
    speed: 3200 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits): data: 64 total: 72
    manufacturer: SK Hynix part-no: HMAA8GR7CJR4N-XN serial: sanitized
  Device-8: DIMMH1 type: DDR4 detail: synchronous registered (buffered) size: 64 GiB
    speed: 3200 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits): data: 64 total: 72
    manufacturer: SK Hynix part-no: HMAA8GR7CJR4N-XN serial: sanitized
PCI Slots:
  Slot: 1 type: PCIe gen: 4 lanes: 16 status: available length: long volts: 3.3 bus-ID: 80:03.1
  Slot: 2 type: PCIe gen: 4 lanes: 8 status: in use length: long volts: 3.3 bus-ID: 43:00.0
  Slot: 3 type: PCIe gen: 4 lanes: 16 status: available length: long volts: 3.3 bus-ID: c0:01.1
  Slot: 4 type: PCIe gen: 4 lanes: 8 status: in use length: long volts: 3.3 bus-ID: 44:00.0
  Slot: 5 type: PCIe gen: 4 lanes: 16 status: in use length: long volts: 3.3 bus-ID: c1:00.0
  Slot: 6 type: PCIe gen: 4 lanes: 16 status: in use length: long volts: 3.3 bus-ID: 01:00.0
  Slot: 7 type: PCIe gen: 4 lanes: 16 status: in use length: long volts: 3.3 bus-ID: 81:00.0
  Slot: N/A type: PCIe lanes: 4 status: in use info: M.2 length: short volts: 3.3
    bus-ID: 08:00.0
  Slot: N/A type: PCIe lanes: 4 status: in use info: M.2 length: short volts: 3.3
    bus-ID: 07:00.0
CPU:
  Info: model: AMD EPYC 7543 socket: SP3 bits: 64 type: MT MCP arch: Zen 3 gen: 4 level: v3
    note: check built: 2021-22 process: TSMC n7 (7nm) family: 0x19 (25) model-id: 1 stepping: 1
    microcode: 0xA0011D1
  Topology: cpus: 1x cores: 32 tpc: 2 threads: 64 smt: enabled cache: L1: 2 MiB desc: d-32x32
    KiB; i-32x32 KiB L2: 16 MiB desc: 32x512 KiB L3: 256 MiB desc: 8x32 MiB
  Speed (MHz): avg: 2800 min/max: 1500/3738 boost: enabled base/boost: 2800/3725 scaling:
    driver: acpi-cpufreq governor: performance volts: 1.1 V ext-clock: 100 MHz cores: 1: 2800
    2: 2800 3: 2800 4: 2800 5: 2800 6: 2800 7: 2800 8: 2800 9: 2800 10: 2800 11: 2800 12: 2800
    13: 2800 14: 2800 15: 2800 16: 2800 17: 2800 18: 2800 19: 2800 20: 2800 21: 2800 22: 2800
    23: 2800 24: 2800 25: 2800 26: 2800 27: 2800 28: 2800 29: 2800 30: 2800 31: 2800 32: 2800
    33: 2800 34: 2800 35: 2800 36: 2800 37: 2800 38: 2800 39: 2800 40: 2800 41: 2800 42: 2800
    43: 2800 44: 2800 45: 2800 46: 2800 47: 2800 48: 2800 49: 2800 50: 2800 51: 2800 52: 2800
    53: 2800 54: 2800 55: 2800 56: 2800 57: 2800 58: 2800 59: 2800 60: 2800 61: 2800 62: 2800
    63: 2800 64: 2800 bogomips: 358384
  Flags: 3dnowprefetch abm adx aes amd_ppin aperfmperf apic arat avx avx2 bmi1 bmi2 bpext brs
    cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy constant_tsc cpb cpuid cqm
    cqm_llc cqm_mbm_local cqm_mbm_total cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists erms
    extapic extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt ht hw_pstate ibpb
    ibrs ibs invpcid invpcid_single irperf lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext
    monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx ospke osvw overflow_recov pae
    pat pausefilter pcid pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge
    pku pni popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sha_ni
    skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor svm svm_lock
    syscall tce topoext tsc tsc_scale umip v_spec_ctrl v_vmsave_vmload vaes vgif vmcb_clean vme
    vmmcall vpclmulqdq wbnoinvd wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: always-on, RSB
    filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: ASPEED Graphics Family vendor: Super Micro H12SSL-i driver: ast v: kernel ports:
    active: VGA-1,Virtual-1 empty: none bus-ID: 47:00.0 chip-ID: 1a03:2000 class-ID: 0300
  Display: server: No display server data found. Headless machine? tty: 238x123
  Monitor-1: VGA-1 size-res: N/A in console modes: 1024x768, 800x600, 640x480
  Monitor-2: Virtual-1 size-res: N/A in console modes: 1024x768, 800x600, 640x480
  API: OpenGL Message: GL data unavailable in console for root.
Audio:
  Message: No device data found.
Network:
  Device-1: Intel 82599ES 10-Gigabit SFI/SFP+ Network driver: ixgbe v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 8 port: 2020 bus-ID: 44:00.0 chip-ID: 8086:10fb class-ID: 0200
  IF: enp68s0f0 state: up speed: 10000 Mbps duplex: full mac: 90:e2:ba:1f:c0:10
  Device-2: Intel 82599ES 10-Gigabit SFI/SFP+ Network driver: ixgbe v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 8 port: 2000 bus-ID: 44:00.1 chip-ID: 8086:10fb class-ID: 0200
  IF: enp68s0f1 state: up speed: 10000 Mbps duplex: full mac: 90:e2:ba:1f:c0:10
  Device-3: Broadcom BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet vendor: Super Micro
    driver: bnxt_en v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 4 link-max: lanes: 8 port: N/A
    bus-ID: 49:00.0 chip-ID: 14e4:16d8 class-ID: 0200 temp: 72.0 C
  IF: eno1np0 state: up speed: 10000 Mbps duplex: full mac: 3c:ec:ef:e6:62:5a
  Device-4: Broadcom BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet vendor: Super Micro
    driver: bnxt_en v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 4 link-max: lanes: 8 port: N/A
    bus-ID: 49:00.1 chip-ID: 14e4:16d8 class-ID: 0200
  IF: eno2np1 state: down mac: 3c:ec:ef:e6:62:5b
  IF-ID-1: bond0 state: up speed: 20000 Mbps duplex: full mac: 90:e2:ba:1f:c0:10
  IF-ID-2: bond0.3 state: up speed: 20000 Mbps duplex: full mac: 90:e2:ba:1f:c0:10
  IF-ID-3: bond0.7 state: up speed: 20000 Mbps duplex: full mac: 90:e2:ba:1f:c0:10
  IF-ID-4: bonding_masters state: N/A speed: N/A duplex: N/A mac: N/A
  IF-ID-5: enxbe3af2b6059f state: down mac: be:3a:f2:b6:05:9f
  IF-ID-6: fwbr101i0 state: up speed: 10000 Mbps duplex: unknown mac: 32:60:8d:d2:c9:29
  IF-ID-7: fwbr176i0 state: up speed: 10000 Mbps duplex: unknown mac: 16:08:f2:fc:5b:17
  IF-ID-8: fwln101i0 state: up speed: 10000 Mbps duplex: full mac: 32:60:8d:d2:c9:29
  IF-ID-9: fwln176i0 state: up speed: 10000 Mbps duplex: full mac: 16:08:f2:fc:5b:17
  IF-ID-10: fwpr101p0 state: up speed: 10000 Mbps duplex: full mac: 66:b2:b0:b0:eb:3b
  IF-ID-11: fwpr176p0 state: up speed: 10000 Mbps duplex: full mac: 92:bd:8e:a8:7a:be
  IF-ID-12: tap700i0 state: unknown speed: 10000 Mbps duplex: full mac: 9e:a9:db:a0:98:5f
  IF-ID-13: veth101i0 state: up speed: 10000 Mbps duplex: full mac: fe:ee:18:10:e3:c0
  IF-ID-14: veth102i0 state: up speed: 10000 Mbps duplex: full mac: fe:f7:f5:1c:e4:51
  IF-ID-15: veth102i1 state: up speed: 10000 Mbps duplex: full mac: fe:14:2c:24:9b:d9
  IF-ID-16: veth110i0 state: up speed: 10000 Mbps duplex: full mac: fe:a7:41:20:9d:0d
  IF-ID-17: veth110i2 state: up speed: 10000 Mbps duplex: full mac: fe:97:69:25:2a:12
  IF-ID-18: veth111i0 state: up speed: 10000 Mbps duplex: full mac: fe:09:57:a1:35:4c
  IF-ID-19: veth111i2 state: up speed: 10000 Mbps duplex: full mac: fe:89:ca:1d:bc:d7
  IF-ID-20: veth120i0 state: up speed: 10000 Mbps duplex: full mac: fe:6c:1f:b2:5f:27
  IF-ID-21: veth120i1 state: up speed: 10000 Mbps duplex: full mac: fe:3e:9e:09:ef:fa
  IF-ID-22: veth125i0 state: up speed: 10000 Mbps duplex: full mac: fe:1a:0b:97:a0:86
  IF-ID-23: veth140i0 state: up speed: 10000 Mbps duplex: full mac: fe:fa:b3:ee:a3:92
  IF-ID-24: veth176i0 state: up speed: 10000 Mbps duplex: full mac: fe:00:66:c6:67:6c
  IF-ID-25: vmbr0 state: up speed: 20000 Mbps duplex: unknown mac: 90:e2:ba:1f:c0:10
  Message: Output throttled. IPs: 2; Limit: 10; Override: --limit [1-x;-1 all]
  IF-ID-26: vmbr0v3 state: up speed: 20000 Mbps duplex: unknown mac: 90:e2:ba:1f:c0:10
  IF-ID-27: vmbr0v7 state: up speed: 20000 Mbps duplex: unknown mac: 90:e2:ba:1f:c0:10
  IF-ID-28: vmbr1 state: up speed: 10000 Mbps duplex: unknown mac: 3c:ec:ef:e6:62:5a
  Message: Output throttled. IPs: 2; Limit: 10; Override: --limit [1-x;-1 all]
  WAN IP: ;; Connection to 193.108.88.1#53(193.108.88.1) for whoami.akamai.net failed: timed
    out.
Bluetooth:
  Device-1: Insyde RNDIS/Ethernet Gadget type: USB driver: rndis_host v: kernel bus-ID: 5-1.2:4
    chip-ID: 0b1f:03ee class-ID: 0a00
  Report: This feature requires one of these tools: hciconfig/bt-adapter
Logical:
  Message: No logical block device data found.
RAID:
  Supported mdraid levels: raid1 linear multipath raid0 raid6 raid5 raid4 raid10
  Device-1: md0 maj-min: 9:0 type: mdraid level: mirror status: active state: clean
    size: 953.74 GiB
  Info: report: 2/2 UU blocks: 1000071168 chunk-size: N/A super-blocks: 1.2
  Components: Online:
  0: nvme5n1p1 maj-min: 259:18 size: 953.87 GiB state: active sync
  1: nvme12n1p1 maj-min: 259:14 size: 953.87 GiB state: active sync
  Device-2: cache type: zfs status: - level: linear zfs-fs: size: 116.07 TiB free: raw:
    size: 3.64 TiB free: 213 GiB allocated: 3.43 TiB
  Components: Online:
  1: nvme1n1 maj-min: 259:35 size: 3.64 TiB
  2: nvme4n1 maj-min: 259:36 size: 3.64 TiB
  Device-3: logs type: zfs status: - level: mirror-1 zfs-fs: size: 449.62 GiB free: raw:
    size: 65 GiB free: 64.5 GiB allocated: 128 KiB
  Components: Online:
  1: nvme10n1p2 maj-min: 259:28 size: 65 GiB
  2: nvme11n1p2 maj-min: 259:24 size: 65 GiB
  Device-4: logs type: zfs status: - level: mirror-2 zfs-fs: size: 901 GiB free: raw:
    size: 65 GiB free: 64.5 GiB allocated: 640 KiB
  Components: Online:
  1: nvme10n1p3 maj-min: 259:29 size: 65 GiB
  2: nvme11n1p3 maj-min: 259:25 size: 65 GiB
  Device-5: logs type: zfs status: - level: mirror-3 zfs-fs: size: 116.07 TiB free: raw:
    size: 65 GiB free: 64.5 GiB allocated: 648 KiB
  Components: Online:
  1: nvme10n1p1 maj-min: 259:27 size: 65 GiB
  2: nvme11n1p1 maj-min: 259:23 size: 65 GiB
  Device-6: rpool type: zfs status: DEGRADED level: mirror-0 raw: size: 464 GiB free: 461 GiB
    allocated: 2.62 GiB zfs-fs: size: 449.62 GiB free: 447 GiB
  Components: Online:
  1: nvme14n1p3 maj-min: 259:46 size: 464.76 GiB
  2: nvme15n1p3 maj-min: 259:41 size: 464.76 GiB
  Device-7: scheduled type: zfs status: ONLINE level: mirror-0 raw: size: 952 GiB free: 299 GiB
    allocated: 653 GiB zfs-fs: size: 922.5 GiB free: 269.06 GiB
  Components: Online:
  1: nvme13n1 maj-min: 259:11 size: 953.87 GiB
  2: nvme2n1 maj-min: 259:1 size: 953.87 GiB
  Device-8: special type: zfs status: - level: mirror-4 zfs-fs: size: 116.07 TiB free: raw:
    size: 1.86 TiB free: 1.75 TiB allocated: 113 GiB
  Components: Online:
  1: nvme3n1 maj-min: 259:0 size: 1.86 TiB
  2: nvme7n1 maj-min: 259:2 size: 1.86 TiB
  3: nvme9n1 maj-min: 259:9 size: 1.86 TiB
  Device-9: vmdata type: zfs status: ONLINE level: mirror-0 raw: size: 930 GiB free: 834 GiB
    allocated: 96.3 GiB zfs-fs: size: 901 GiB free: 800.16 GiB
  Components: Online:
  1: nvme0n1 maj-min: 259:32 size: 931.51 GiB
  2: nvme6n1 maj-min: 259:31 size: 931.51 GiB
  Device-10: zfshome type: zfs status: ONLINE raw: size: 176 TiB free: 96.6 TiB
    allocated: 79.9 TiB zfs-fs: size: 116.07 TiB free: 60.78 TiB
  Array-1: raidz2-0 status: N/A raw: size: 87.3 TiB free: 47.6 TiB
  Components: Online:
  1: sda maj-min: 8:0 size: 14.55 TiB
  2: sdc maj-min: 8:32 size: 14.55 TiB
  3: sdf maj-min: 8:80 size: 14.55 TiB
  4: sdg maj-min: 8:96 size: 14.55 TiB
  5: sdi maj-min: 8:128 size: 14.55 TiB
  6: sdk maj-min: 8:160 size: 14.55 TiB
  Array-2: raidz2-1 status: N/A raw: size: 87.2 TiB free: 47.2 TiB
  Components: Online:
  1: sdb maj-min: 8:16 size: 14.55 TiB
  2: sdd maj-min: 8:48 size: 14.55 TiB
  3: sde maj-min: 8:64 size: 14.55 TiB
  4: sdh maj-min: 8:112 size: 14.55 TiB
  5: sdj maj-min: 8:144 size: 14.55 TiB
  6: sdl maj-min: 8:176 size: 14.55 TiB
Drives:
  Local Storage: total: raw: 194.24 TiB usable: 134.42 TiB used: 52.57 TiB (39.1%)
  ID-1: /dev/nvme0n1 maj-min: 259:32 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: sanitized rev: 5B2QGXA7 temp: 36.9 C scheme: GPT
  SMART: yes health: PASSED on: 29 hrs cycles: 7 read-units: 421,876 [216 GB]
    written-units: 1,991,956 [1.01 TB]
  ID-2: /dev/nvme10n1 maj-min: 259:22 vendor: Intel model: SSDPE21D280GA size: 260.83 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
    serial: sanitized rev: E2010435 temp: 42.9 C scheme: GPT
  SMART: yes health: PASSED on: 2y 190d 14h cycles: 71 read-units: 9,110 [4.66 GB]
    written-units: 52,620,491 [26.9 TB]
  ID-3: /dev/nvme11n1 maj-min: 259:15 vendor: Intel model: SSDPE21D280GA size: 260.83 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
    serial: sanitized rev: E2010435 temp: 43.9 C scheme: GPT
  SMART: yes health: PASSED on: 2y 190d 14h cycles: 79 read-units: 9,261 [4.74 GB]
    written-units: 52,620,522 [26.9 TB]
  ID-4: /dev/nvme12n1 maj-min: 259:3 model: PCIe SSD size: 953.87 GiB block-size:
    physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: sanitized
    rev: ECFM13.3 temp: 28.9 C scheme: GPT
  SMART: yes health: PASSED on: 2y 129d 16h cycles: 34 read-units: 5,396,568 [2.76 TB]
    written-units: 97,397,105 [49.8 TB]
  ID-5: /dev/nvme13n1 maj-min: 259:11 model: PCIe SSD size: 953.87 GiB block-size:
    physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: sanitized
    rev: ECFM13.3 temp: 28.9 C scheme: GPT
  SMART: yes health: PASSED on: 2y 129d 15h cycles: 34 read-units: 47,901,730 [24.5 TB]
    written-units: 26,825,824 [13.7 TB]
  ID-6: /dev/nvme15n1 maj-min: 259:33 vendor: Samsung model: SSD 980 PRO 500GB size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: sanitized rev: 5B2QGXA7 temp: 37.9 C scheme: GPT
  SMART: yes health: PASSED on: 4d 13h cycles: 42 read-units: 15,069 [7.71 GB]
    written-units: 1,151,101 [589 GB]
  ID-7: /dev/nvme1n1 maj-min: 259:35 vendor: Western Digital model: WD BLACK SN850X 4000GB
    size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: sanitized rev: 624361WD temp: 39.9 C scheme: GPT
  SMART: yes health: PASSED on: 30d 2h cycles: 6 read-units: 1,379,049 [706 GB]
    written-units: 7,405,836 [3.79 TB]
  ID-8: /dev/nvme2n1 maj-min: 259:1 model: PCIe SSD size: 953.87 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: sanitized rev: ECFM13.3
    temp: 28.9 C scheme: GPT
  SMART: yes health: PASSED on: 2y 129d 15h cycles: 34 read-units: 48,368,483 [24.7 TB]
    written-units: 25,539,127 [13.0 TB]
  ID-9: /dev/nvme3n1 maj-min: 259:0 model: PCIe SSD size: 1.86 TiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: sanitized rev: ECFM13.3
    temp: 28.9 C scheme: GPT
  SMART: yes health: PASSED on: 2y 129d 15h cycles: 34 read-units: 3,059,017 [1.56 TB]
    written-units: 29,020,530 [14.8 TB]
  ID-10: /dev/nvme4n1 maj-min: 259:36 vendor: Western Digital model: WD BLACK SN850X 4000GB
    size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: sanitized rev: 624361WD temp: 42.9 C scheme: GPT
  SMART: yes health: PASSED on: 30d 4h cycles: 8 read-units: 1,380,481 [706 GB]
    written-units: 7,405,305 [3.79 TB]
  ID-11: /dev/nvme5n1 maj-min: 259:8 model: PCIe SSD size: 953.87 GiB block-size:
    physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: sanitized
    rev: ECFM13.3 temp: 28.9 C scheme: GPT
  SMART: yes health: PASSED on: 2y 129d 15h cycles: 33 read-units: 9,841,057 [5.03 TB]
    written-units: 92,935,018 [47.5 TB]
  ID-12: /dev/nvme6n1 maj-min: 259:31 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: sanitized rev: 5B2QGXA7 temp: 37.9 C scheme: GPT
  SMART: yes health: PASSED on: 28 hrs cycles: 6 read-units: 471,769 [241 GB]
    written-units: 1,991,984 [1.01 TB]
  ID-13: /dev/nvme7n1 maj-min: 259:2 model: PCIe SSD size: 1.86 TiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: sanitized rev: ECFM13.3
    temp: 28.9 C scheme: GPT
  SMART: yes health: PASSED on: 2y 129d 15h cycles: 33 read-units: 3,060,249 [1.56 TB]
    written-units: 29,020,526 [14.8 TB]
  ID-14: /dev/nvme8n1 maj-min: 259:4 model: PCIe SSD size: 238.47 GiB block-size:
    physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: sanitized
    rev: ECFM13.3 temp: 27.9 C scheme: GPT
  SMART: yes health: PASSED on: 2y 129d 16h cycles: 34 read-units: 146,399 [74.9 GB]
    written-units: 33,175,449 [16.9 TB]
  ID-15: /dev/nvme9n1 maj-min: 259:9 model: PCIe SSD size: 1.86 TiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: sanitized rev: ECFM13.3
    temp: 28.9 C scheme: GPT
  SMART: yes health: PASSED on: 2y 129d 15h cycles: 34 read-units: 3,060,168 [1.56 TB]
    written-units: 29,020,530 [14.8 TB]
  ID-16: /dev/sda maj-min: 8:0 vendor: Seagate model: ST16000NM000J-2TW103 size: 14.55 TiB
    block-size: physical: 4096 B logical: 512 B sata: 3.3 speed: 6.0 Gb/s type: HDD rpm: 7200
    serial: sanitized rev: SN01 temp: 30 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 78d 0h cycles: 20 read: 34.94 PiB
    written: 94.85 TiB Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
  ID-17: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST16000NM000J-2TW103 size: 14.55 TiB
    block-size: physical: 4096 B logical: 512 B sata: 3.3 speed: 6.0 Gb/s type: HDD rpm: 7200
    serial: sanitized rev: SN01 temp: 31 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 78d 0h cycles: 19 read: 32.87 PiB
    written: 89.89 TiB Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
  ID-18: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST16000NM000J-2TW103 size: 14.55 TiB
    block-size: physical: 4096 B logical: 512 B sata: 3.3 speed: 6.0 Gb/s type: HDD rpm: 7200
    serial: sanitized rev: SN02 temp: 31 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 98d 5h cycles: 17 read: 41.15 PiB
    written: 66.48 TiB Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
  ID-19: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST16000NM000J-2TW103 size: 14.55 TiB
    block-size: physical: 4096 B logical: 512 B sata: 3.3 speed: 6.0 Gb/s type: HDD rpm: 7200
    serial: sanitized rev: SN01 temp: 31 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 121d 0h cycles: 23 read: 45.21 PiB
    written: 70.31 TiB Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
  ID-20: /dev/sde maj-min: 8:64 vendor: Seagate model: ST16000NM000J-2TW103 size: 14.55 TiB
    block-size: physical: 4096 B logical: 512 B sata: 3.3 speed: 6.0 Gb/s type: HDD rpm: 7200
    serial: sanitized rev: SN01 temp: 32 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 174d 20h cycles: 14 read: 50.11 PiB
    written: 65.24 TiB Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
  ID-21: /dev/sdf maj-min: 8:80 vendor: Seagate model: ST16000NM000J-2TW103 size: 14.55 TiB
    block-size: physical: 4096 B logical: 512 B sata: 3.3 speed: 6.0 Gb/s type: HDD rpm: 7200
    serial: sanitized rev: SN01 temp: 30 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 353d 9h cycles: 15 read: 69.67 PiB
    written: 66.47 TiB Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
  ID-22: /dev/sdg maj-min: 8:96 vendor: Seagate model: ST16000NM000J-2TW103 size: 14.55 TiB
    block-size: physical: 4096 B logical: 512 B sata: 3.3 speed: 6.0 Gb/s type: HDD rpm: 7200
    serial: sanitized rev: SB2C temp: 31 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 199d 14h cycles: 14 read: 32.27 PiB
    written: 65.23 TiB Pre-Fail: reallocated sector: 100 threshold: 10 attribute: Spin_Retry_Count
    value: 100 worst: 100 threshold: 97
  ID-23: /dev/sdh maj-min: 8:112 vendor: Seagate model: ST16000NM000J-2TW103 size: 14.55 TiB
    block-size: physical: 4096 B logical: 512 B sata: 3.3 speed: 6.0 Gb/s type: HDD rpm: 7200
    serial: sanitized rev: SN02 temp: 31 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 267d 11h cycles: 14 read: 67.07 PiB
    written: 65.55 TiB Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
  ID-24: /dev/sdi maj-min: 8:128 vendor: Seagate model: ST16000NM000J-2TW103 size: 14.55 TiB
    block-size: physical: 4096 B logical: 512 B sata: 3.3 speed: 6.0 Gb/s type: HDD rpm: 7200
    serial: sanitized rev: SN02 temp: 31 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 225d 14h cycles: 16 read: 60.47 PiB
    written: 50.88 TiB Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
  ID-25: /dev/sdj maj-min: 8:144 vendor: Seagate model: ST16000NM000J-2TW103 size: 14.55 TiB
    block-size: physical: 4096 B logical: 512 B sata: 3.3 speed: 6.0 Gb/s type: HDD rpm: 7200
    serial: sanitized rev: SN02 temp: 30 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 285d 0h cycles: 14 read: 62.71 PiB
    written: 65.57 TiB Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
  ID-26: /dev/sdk maj-min: 8:160 vendor: Seagate model: ST16000NM000J-2TW103 size: 14.55 TiB
    block-size: physical: 4096 B logical: 512 B sata: 3.3 speed: 6.0 Gb/s type: HDD rpm: 7200
    serial: sanitized rev: SN02 temp: 30 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 2y 19d 17h cycles: 15 read: 80.14 PiB
    written: 22.53 TiB Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
  ID-27: /dev/sdl maj-min: 8:176 vendor: Seagate model: ST16000NM000J-2TW103 size: 14.55 TiB
    block-size: physical: 4096 B logical: 512 B sata: 3.3 speed: 6.0 Gb/s type: HDD rpm: 7200
    serial:sanitized rev: SN02 temp: 29 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 321d 12h cycles: 14 read: 71.44 PiB
    written: 65.59 TiB Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: N/A size: 449.45 GiB used: 2.45 GiB (0.5%) fs: zfs logical: rpool/ROOT/pve-1
  ID-2: /etc/pve raw-size: N/A size: 128 MiB used: 24 KiB (0.0%) fs: fuse dev: /dev/fuse
    label: N/A uuid: N/A
  ID-3: /mnt/mythbuntu/live1 raw-size: 238.47 GiB size: 233.67 GiB (97.99%) used: 36 KiB (0.0%)
    fs: ext4 block-size: 4096 B dev: /dev/nvme8n1p1 maj-min: 259:16 label: N/A
    uuid: removed
  ID-4: /mnt/mythbuntu/scheduled raw-size: N/A size: 922.44 GiB used: 653.38 GiB (70.8%) fs: zfs
    logical: scheduled
  ID-5: /rpool raw-size: N/A size: 447.01 GiB used: 256 KiB (0.0%) fs: zfs logical: rpool
  ID-6: /rpool/ROOT raw-size: N/A size: 447.01 GiB used: 256 KiB (0.0%) fs: zfs
    logical: rpool/ROOT
  ID-7: /rpool/data raw-size: N/A size: 447.01 GiB used: 256 KiB (0.0%) fs: zfs
    logical: rpool/data
  ID-8: /var/lib/vz raw-size: N/A size: 447.13 GiB used: 124.1 MiB (0.0%) fs: zfs
    logical: rpool/var-lib-vz
  ID-9: /vmdata raw-size: N/A size: 800.16 GiB used: 128 KiB (0.0%) fs: zfs logical: vmdata
  ID-10: /vmdata/subvol-101-disk-0 raw-size: N/A size: 8 GiB used: 1.14 GiB (14.3%) fs: zfs
    logical: vmdata/subvol-101-disk-0
  ID-11: /vmdata/subvol-102-disk-0 raw-size: N/A size: 8 GiB used: 1.84 GiB (23.1%) fs: zfs
    logical: vmdata/subvol-102-disk-0
  ID-12: /vmdata/subvol-110-disk-0 raw-size: N/A size: 32 GiB used: 7.19 GiB (22.5%) fs: zfs
    logical: vmdata/subvol-110-disk-0
  ID-13: /vmdata/subvol-111-disk-0 raw-size: N/A size: 8 GiB used: 1.98 GiB (24.7%) fs: zfs
    logical: vmdata/subvol-111-disk-0
  ID-14: /vmdata/subvol-120-disk-0 raw-size: N/A size: 16 GiB used: 1.75 GiB (11.0%) fs: zfs
    logical: vmdata/subvol-120-disk-0
  ID-15: /vmdata/subvol-125-disk-0 raw-size: N/A size: 8 GiB used: 1.52 GiB (19.0%) fs: zfs
    logical: vmdata/subvol-125-disk-0
  ID-16: /vmdata/subvol-140-disk-0 raw-size: N/A size: 32 GiB used: 12.29 GiB (38.4%) fs: zfs
    logical: vmdata/subvol-140-disk-0
  ID-17: /vmdata/subvol-170-disk-0 raw-size: N/A size: 16 GiB used: 1.87 GiB (11.7%) fs: zfs
    logical: vmdata/subvol-170-disk-0
  ID-18: /vmdata/subvol-176-disk-0 raw-size: N/A size: 16 GiB used: 736.6 MiB (4.5%) fs: zfs
    logical: vmdata/subvol-176-disk-0
  ID-19: /zfshome raw-size: N/A size: 60.78 TiB used: 13.8 MiB (0.0%) fs: zfs logical: zfshome
  ID-20: /zfshome/sanitized raw-size: N/A size: 61.34 TiB used: 569.4 GiB (0.9%) fs: zfs
    logical: zfshome/sanitized
  ID-21: /zfshome/sanitized raw-size: N/A size: 60.83 TiB used: 48.58 GiB (0.1%) fs: zfs
    logical: zfshome/sanitized
  ID-22: /zfshome/sanitized raw-size: N/A size: 60.78 TiB used: 128 KiB (0.0%) fs: zfs
    logical: zfshome/sanitized
  ID-23: /zfshome/sanitized raw-size: N/A size: 62.23 TiB used: 1.45 TiB (2.3%) fs: zfs
    logical: zfshome/sanitized
  ID-24: /zfshome/sanitized raw-size: N/A size: 84.08 TiB used: 23.3 TiB (27.7%) fs: zfs
    logical: zfshome/sanitized
  ID-25: /zfshome/sanitized raw-size: N/A size: 60.78 TiB used: 2.86 GiB (0.0%) fs: zfs
    logical: zfshome/sanitized
  ID-26: /zfshome/sanitized raw-size: N/A size: 68.03 TiB used: 7.25 TiB (10.7%) fs: zfs
    logical: zfshome/sanitized
  ID-27: /zfshome/rsyslogd raw-size: N/A size: 60.79 TiB used: 7.61 GiB (0.0%) fs: zfs
    logical: zfshome/sanitized
  ID-28: /zfshome/sanitized raw-size: N/A size: 78.86 TiB used: 18.08 TiB (22.9%) fs: zfs
    logical: zfshome/sanitized
  ID-29: /zfshome/share raw-size: N/A size: 60.86 TiB used: 79.31 GiB (0.1%) fs: zfs
    logical: zfshome/sanitized
  ID-30: /zfshome/sanitized raw-size: N/A size: 61 TiB used: 229.83 GiB (0.4%) fs: zfs
    logical: zfshome/sanitized
  ID-31: /zfshome/sanitized raw-size: N/A size: 61.64 TiB used: 879.08 GiB (1.4%) fs: zfs
    logical: zfshome/sanitized
  ID-32: /zfshome/sanitized raw-size: N/A size: 60.83 TiB used: 52.47 GiB (0.1%) fs: zfs
    logical: zfshome/sanitized
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 953.74 GiB used: 739.8 MiB (0.1%) priority: -2
    dev: /dev/md0p1 maj-min: 259:51 label: N/A uuid: removed
Unmounted:
  ID-1: /dev/nvme0n1p9 maj-min: 259:44 size: 8 MiB fs: N/A label: N/A uuid: N/A
  ID-2: /dev/nvme10n1p4 maj-min: 259:30 size: 65 GiB fs: N/A label: N/A uuid: N/A
  ID-3: /dev/nvme11n1p4 maj-min: 259:26 size: 65 GiB fs: N/A label: N/A uuid: N/A
  ID-4: /dev/nvme13n1p9 maj-min: 259:20 size: 8 MiB fs: N/A label: N/A uuid: N/A
  ID-5: /dev/nvme15n1p1 maj-min: 259:39 size: 1007 KiB fs: N/A label: N/A uuid: N/A
  ID-6: /dev/nvme15n1p2 maj-min: 259:40 size: 1024 MiB fs: vfat label: N/A uuid: removed
  ID-7: /dev/nvme1n1p9 maj-min: 259:50 size: 8 MiB fs: N/A label: N/A uuid: N/A
  ID-8: /dev/nvme2n1p9 maj-min: 259:12 size: 8 MiB fs: N/A label: N/A uuid: N/A
  ID-9: /dev/nvme3n1p9 maj-min: 259:7 size: 8 MiB fs: N/A label: N/A uuid: N/A
  ID-10: /dev/nvme4n1p9 maj-min: 259:49 size: 8 MiB fs: N/A label: N/A uuid: N/A
  ID-11: /dev/nvme6n1p9 maj-min: 259:38 size: 8 MiB fs: N/A label: N/A uuid: N/A
  ID-12: /dev/nvme7n1p9 maj-min: 259:13 size: 8 MiB fs: N/A label: N/A uuid: N/A
  ID-13: /dev/nvme9n1p9 maj-min: 259:21 size: 8 MiB fs: N/A label: N/A uuid: N/A
  ID-14: /dev/zd0 maj-min: 230:0 size: 32 GiB fs: N/A label: N/A uuid: N/A
  ID-15: /dev/zd0p1 maj-min: 230:1 size: 30 GiB fs: ext4 label: N/A
    uuid: removed
  ID-16: /dev/zd0p2 maj-min: 230:2 size: 1 KiB fs: N/A label: N/A uuid: N/A
  ID-17: /dev/zd0p5 maj-min: 230:5 size: 2 GiB fs: swap label: N/A
    uuid: removed
  ID-18: /dev/zd16 maj-min: 230:16 size: 2 TiB fs: N/A label: N/A uuid: N/A
  ID-19: /dev/zd16p1 maj-min: 230:17 size: 2 TiB fs: ext4 label: N/A
    uuid: removed
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 2-0:1 info: Super-speed hub ports: 2 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-4: 4-0:1 info: Super-speed hub ports: 2 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-5: 5-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-6: 5-1:2 info: Hi-speed hub with single TT ports: 5 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0107 class-ID: 0900
  Device-1: 5-1.1:3 info: ATEN SMCI HID KM type: Keyboard,Mouse driver: hid-generic,usbhid
    interfaces: 2 rev: 1.1 speed: 480 Mb/s power: 2mA chip-ID: 0557:9241 class-ID: 0301
  Device-2: 5-1.2:4 info: Insyde RNDIS/Ethernet Gadget type: Bluetooth,CDC-Data
    driver: rndis_host interfaces: 2 rev: 2.0 speed: 480 Mb/s power: 2mA chip-ID: 0b1f:03ee
    class-ID: 0a00
  Hub-7: 6-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-8: 7-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 7-1:2 info: American Power Conversion UPS type: HID driver: hid-generic,usbhid
    interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 2mA chip-ID: 051d:0003 class-ID: 0300
    serial: sanitized
  Hub-9: 8-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  Src: ipmi System Temperatures: cpu: 46 C mobo: 35 C
  Fan Speeds (RPM): fan-1: 2520 fan-2: 1680 fan-3: 1680 fan-4: 1680 fan-5: 1260 fan-10: 420
    fan-11: 980
  Power: 12v: 11.856 5v: 5.020 3.3v: 3.361 vbat: N/A dimm-p1: N/A dimm-p2: N/A
  Src: lm-sensors System Temperatures: cpu: 47.9 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 779 libs: 450 tools: apt,apt-get
  Active apt repos in: /etc/apt/sources.list
    1: deb http://ftp.us.debian.org/debian bookworm main contrib
    2: deb http://ftp.us.debian.org/debian bookworm-updates main contrib
    3: deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription
    4: deb http://security.debian.org bookworm-security main contrib
  No active apt repos in: /etc/apt/sources.list.d/ceph.list
  No active apt repos in: /etc/apt/sources.list.d/pve-enterprise.list
Processes:
  CPU top: 5 of 2065
  1: cpu: 2.3% command: sanitized pid: 661708 mem: 172.7 MiB (0.0%)
  2: cpu: 1.8% command: ./sanitized pid: 1189100 mem: 64.2 MiB (0.0%)
  3: cpu: 1.5% command: pvestatd pid: 5251 mem: 90.8 MiB (0.0%)
  4: cpu: 1.1% command: kvm pid: 9923 mem: 2045.9 MiB (0.3%)
  5: cpu: 1.1% command: mythbackend pid: 11935 mem: 753.0 MiB (0.1%)
  Memory top: 5 of 2065
  1: mem: 2045.9 MiB (0.3%) command: kvm pid: 9923 cpu: 1.1%
  2: mem: 753.0 MiB (0.1%) command: mythbackend pid: 11935 cpu: 1.1%
  3: mem: 601.1 MiB (0.1%) command: java pid: 9590 cpu: 0.1%
  4: mem: 348.7 MiB (0.0%) command: systemd-journald pid: 11308 cpu: 0.0%
  5: mem: 294.4 MiB (0.0%) command: mariadbd pid: 3804779 cpu: 1.1%
Info:
  Processes: 2065 Uptime: 29d 2h 20m wakeups: 0 Init: systemd v: 252 target: graphical (5)
  default: graphical tool: systemctl Compilers: N/A Shell: Bash v: 5.2.15
  running-in: pty pts/0 (SSH) inxi: 3.3.26
Phew, took some work to sanitize the inxi output to not give away all of my serial numbers and varous account names in file systems....
Last edited by mattlach on Sat Jan 27, 2024 10:38 pm, edited 1 time in total.
Corsair 1000D, Threadripper 3960x, Asus ROG Zenith II, 64GB, Samsung 990 Pro, Geforce RTX 4090, 42" LG C3, 2x Dell U2412M, Schiit Bifrost Multibit DAC
Server: AMD EPYC 7543(32C/64T), SuperMicro H12SSL-NT, 512GB RAM, 192TB ZFS
Top
motoryzen
Level 10
Level 10
Posts: 3497
Joined: Sun Dec 08, 2019 12:25 am

Re: The Linux "Copy Problem" and the Mint desktop.

Post by motoryzen »

Mint isn't a " Desktop". Mint is a distribution.

Cinnamon, Mate, XFCE are desktops

inxi -v8 Doesn't give all the details.

Follow the steps in how to get help, step 5, 2nd dot aka bulletin point. Shows the gui way which is simpler and already auto encloses the results in code tags.

Serial numbers to your storage drives doesn't mean your security is exposed or vulnerable.

The gui way doesn't provide your account names nor serial numbers of your storage drives.
Mint 21.2 Cinnamon 5.8.4
asrock x570 taichi ...bios p5.00
ryzen 5900x
128GB Kingston Fury @ 3600mhz
Corsair mp600 pro xt NVME ssd 4TB
three 4TB ssds
dual 1TB ssds
Two 16TB Toshiba hdd's
24GB amd 7900xtx vid card
Viewsonic Elite UHD 32" 144hz monitor
Top
mattlach
Level 4
Level 4
Posts: 323
Joined: Mon May 30, 2011 8:34 pm

Re: The Linux "Copy Problem" and the Mint desktop.

Post by mattlach »

motoryzen wrote: ⤴Sat Jan 27, 2024 7:57 pm Mint isn't a " Desktop". Mint is a distribution.

Cinnamon, Mate, XFCE are desktops
I'm well aware thank you. It was just a case of fingers faster than brain. Sorry that bothered you.
motoryzen wrote: ⤴Sat Jan 27, 2024 7:57 pm inxi -v8 Doesn't give all the details.

Follow the steps in how to get help, step 5, 2nd dot aka bulletin point. Shows the gui way which is simpler and already auto encloses the results in code tags.
I'm not necessarily looking for help/support. I'm more interested in a conversation about Linux and its capabilities in this regard.
motoryzen wrote: ⤴Sat Jan 27, 2024 7:57 pm Serial numbers to your storage drives doesn't mean your security is exposed or vulnerable.

The gui way doesn't provide your account names nor serial numbers of your storage drives.
No, but it can lead to people committing warranty fraud using my serial numbers. Further more some support sites will leak information about you if you enter serial numbers. (its really scary how bad many hardware vendors customer service portals are designed) Its just best practice to not leave them hanging out there.
Corsair 1000D, Threadripper 3960x, Asus ROG Zenith II, 64GB, Samsung 990 Pro, Geforce RTX 4090, 42" LG C3, 2x Dell U2412M, Schiit Bifrost Multibit DAC
Server: AMD EPYC 7543(32C/64T), SuperMicro H12SSL-NT, 512GB RAM, 192TB ZFS
Top
mattlach
Level 4
Level 4
Posts: 323
Joined: Mon May 30, 2011 8:34 pm

Re: The Linux "Copy Problem" and the Mint desktop.

Post by mattlach »

So,

just because I was curious, I went and repeated the same tests on an older Xeon workstation I use for backup purposes.

(Dual Socket Xeon E5-2697 v2, 24C/48T Ivy Bridge era, base 2.7, Turbo 3.5, 256GB DDR3-1600 ECC RDIMMS)

This issue is replicated there. Same transfer of file, high CPU load, and data transfer CPU limited at approximately where one would expect it to be based on the difference in single core performance of the two machines.

So, very different era, manufacturer, chipsets drives (but same x520 NIC).

It really does appear as if there is an issue with CPU load from disk operations under Linux that transcends hardware manufacturers and generation.
Corsair 1000D, Threadripper 3960x, Asus ROG Zenith II, 64GB, Samsung 990 Pro, Geforce RTX 4090, 42" LG C3, 2x Dell U2412M, Schiit Bifrost Multibit DAC
Server: AMD EPYC 7543(32C/64T), SuperMicro H12SSL-NT, 512GB RAM, 192TB ZFS
Top
motoryzen
Level 10
Level 10
Posts: 3497
Joined: Sun Dec 08, 2019 12:25 am

Re: The Linux "Copy Problem" and the Mint desktop.

Post by motoryzen »

I'm not necessarily looking for help/support. I'm more interested in a conversation about Linux and its capabilities in this regard
Your title talks about a " problem" literally in the topic title.

You didn't post this in a general chat section..so I naturally assumed you were seeking help to try to resolve that " problem".
No, but it can lead to people committing warranty fraud using my serial numbers
...talking about Serial numbers being shown/mentioned..

Not if the system details posting method ..doesn't show any serial numbers ...TO enable any thieves to use that info to commit warranty fraud. Which the gui method I've already explained...does not show (shrugs)

Either trust this site and that step 5 2nd dot's gui instructions work as I explained..or don't. (shrugs). It's your PC.not mine. Just pointing out the Forum rules.

. I'm not trying to sound rude, but I've been using Mint Cinnamon since late 2010 and have been a member of this sight for a long time and have never been given any reason to suspect my privacy at any level could or would be leaked.

The Site management/moderators and/or whoever is in charge of security has done a good job respecting everyone's privacy. I don't recall seeing any proof that someone's personal data or storage drives' serial numbers leaked from this site ...ever.

Yes..some hardware vendors' customer service portals' privacy efforts are garbage...yes I couldn't agree more..legit, But this site isn't one of those.

I couldn't help but notice ...
ID-3: /home/matt/Documents/Docs raw-size: N/A size: 62.23 TiB
used: 1.45 TiB (2.3%) fs: nfs4 remote: subnet2sanitized:/[color=#BF4000]zfs[/color]home/matt... I've never used zfs before but I've heard a few times here and there throughout the years of oddities using it with Mint, but not as often those same oddities/results using it with other distros such as Arch Based.

Oh..and btw

if you're concerned about serial numbers... some say a uuid can be just as vulnerable..which your inxi method you chose shows one

Code: Select all

ID-1: / raw-size: 400.02 GiB size: 392.67 GiB (98.16%)
    used: 266.45 GiB (67.9%) fs: ext4 block-size: 4096 B dev: /dev/nvme3n1p5
    maj-min: 259:10 label: N/A uuid: [color=#BF4080]f90b05e5-0ad2-4ac3-8dac-247144aa436d[/color]
so instead of doing your own thing..maybe follow the rules of step 5 2nd dot from now on? (shrugs).
Mint 21.2 Cinnamon 5.8.4
asrock x570 taichi ...bios p5.00
ryzen 5900x
128GB Kingston Fury @ 3600mhz
Corsair mp600 pro xt NVME ssd 4TB
three 4TB ssds
dual 1TB ssds
Two 16TB Toshiba hdd's
24GB amd 7900xtx vid card
Viewsonic Elite UHD 32" 144hz monitor
Top
mattlach
Level 4
Level 4
Posts: 323
Joined: Mon May 30, 2011 8:34 pm

Re: The Linux "Copy Problem" and the Mint desktop.

Post by mattlach »

I don't understand why this exchange has taken such a confrontational turn.
motoryzen wrote: ⤴Sat Jan 27, 2024 9:04 pm Your title talks about a " problem" literally in the topic title.
Yes, but if you read the entire post, I'm pointing towards what seems to be a linux-wide issue right now, not a tech support request for myself.
motoryzen wrote: ⤴Sat Jan 27, 2024 9:04 pm You didn't post this in a general chat section..so I naturally assumed you were seeking help to try to resolve that " problem".
My bad. That is what I thought the "other" section was for and why I posted it there.
motoryzen wrote: ⤴Sat Jan 27, 2024 9:04 pm ...talking about Serial numbers being shown/mentioned..

Not if the system details posting method ..doesn't show any serial numbers ...TO enable any thieves to use that info to commit warranty fraud. Which the gui method I've already explained...does not show (shrugs)
That is great, I was unaware of the GUI method. I will look at it next time.
motoryzen wrote: ⤴Sat Jan 27, 2024 9:04 pm I'm not trying to sound rude, but I've been using Mint Cinnamon since late 2010 and have been a member of this sight for a long time and have never been given any reason to suspect my privacy at any level could or would be leaked.

The Site management/moderators and/or whoever is in charge of security has done a good job respecting everyone's privacy. I don't recall seeing any proof that someone's personal data or storage drives' serial numbers leaked from this site ...ever.
So have I. (I forget when I actually joined, but I was a lurker for a while). I have no reason to suspect the Mint team or admins have any ill intent (though to be fair, their security track record is not exactly perfect but they did respond to it right, and deal with it appropriately.)

My take is that it is a good idea to minimize any information posted to a public forum. Anyone with an internet connection can read and/or scrape these forums with or without the Mint teams approval. Such is life on public forums.

If I post hardware serial numbers, and then someone uses those serial numbers on the hardware vendors support systems, it can seriously mess with my ability to get warranty service in the future. It's not an "end of the world" type of risk, but the less information you put out there the better.

So, yeah, I am talking about th elikes of Asus, Gigabyte, Sabrent, Samsung, etc. etc. Their customer service/warranty portals are of VERY mixed quality.
motoryzen wrote: ⤴Sat Jan 27, 2024 9:04 pm Oh..and btw

if you're concerned about serial numbers... some say a uuid can be just as vulnerable..which your inxi method you chose shows one
I do not see how filesystem UUID's might be used like that, but maybe I have overlooked something here. Maybe - since they tend to be relatively unique - if the same UUID is found in multiple locations it can be used to link your miltiple forum or other accounts, but that seems like a little bit of a stretch. I'll keep it in mind in the future though. Thanks.

motoryzen wrote: ⤴Sat Jan 27, 2024 9:04 pm ID-3: /home/matt/Documents/Docs raw-size: N/A size: 62.23 TiB
used: 1.45 TiB (2.3%) fs: nfs4 remote: subnet2sanitized:/[color=#BF4000]zfs[/color]home/matt... I've never used zfs before but I've heard a few times here and there throughout the years of oddities using it with Mint, but not as often those same oddities/results using it with other distros such as Arch Based.
IN this case ZFS is not running on the Mint workstation. This mount location is an NFS share, which resides on a remote server. That server uses "ZFS on Linux" under Debian Bookworm.
Corsair 1000D, Threadripper 3960x, Asus ROG Zenith II, 64GB, Samsung 990 Pro, Geforce RTX 4090, 42" LG C3, 2x Dell U2412M, Schiit Bifrost Multibit DAC
Server: AMD EPYC 7543(32C/64T), SuperMicro H12SSL-NT, 512GB RAM, 192TB ZFS
Top
motoryzen
Level 10
Level 10
Posts: 3497
Joined: Sun Dec 08, 2019 12:25 am

Re: The Linux "Copy Problem" and the Mint desktop.

Post by motoryzen »

I don't understand why this exchange has taken such a confrontational turn
Um..I wasn't being confrontational nor rude. Just stating some facts.

Gees..what is with people these days. Relax or grow some skin.

I'm out.
Mint 21.2 Cinnamon 5.8.4
asrock x570 taichi ...bios p5.00
ryzen 5900x
128GB Kingston Fury @ 3600mhz
Corsair mp600 pro xt NVME ssd 4TB
three 4TB ssds
dual 1TB ssds
Two 16TB Toshiba hdd's
24GB amd 7900xtx vid card
Viewsonic Elite UHD 32" 144hz monitor
Top
User avatar
Moem
Level 22
Level 22
Posts: 16239
Joined: Tue Nov 17, 2015 9:14 am
Location: The Netherlands
Contact:
Contact Moem

Re: The Linux "Copy Problem" and the Mint desktop.

Post by Moem »

mattlach wrote: ⤴Sat Jan 27, 2024 10:35 pm I'm pointing towards what seems to be a linux-wide issue right now, not a tech support request for myself.
That is fine, and the 'Chat aboout Linux' section is a good fit for such a topic; the topic has been moved.
Image

If your issue is solved, kindly indicate that by editing the first post in the topic, and adding [SOLVED] to the title. Thanks!
Top
t42
Level 11
Level 11
Posts: 3747
Joined: Mon Jan 20, 2014 6:48 pm

Re: The Linux "Copy Problem" and the Mint desktop.

Post by t42 »

mattlach wrote: ⤴Sat Jan 27, 2024 6:58 pm took some work to sanitize the inxi output
I'm using sudo inxi -v8 often and sudo inxi -v8z is doing even better sanitizing job.
If you need to filter UUIDs as well then run

Code: Select all

sudo inxi -v8 --zu
I read that 2019 article and it seems there were some changes in coreutils since then https://git.savannah.gnu.org/cgit/coreu ... ep&q=cp%3A, not that things are noticeably better.
Last edited by t42 on Sun Jan 28, 2024 12:39 pm, edited 1 time in total.
-=t42=-
Top
User avatar
Pjotr
Level 24
Level 24
Posts: 20142
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland) 🇳🇱
Contact:
Contact Pjotr

Re: The Linux "Copy Problem" and the Mint desktop.

Post by Pjotr »

Perhaps Nemo in 21.3 Virginia does a better job? You might try an upgrade.

Finally: it's a shot in the dark, but you can also try whether fiddling with dirty_ratio and dirty_background_ratio helps:
https://easylinuxtipsproject.blogspot.c ... .html#ID11
(item 11)
Tip: 10 things to do after installing Linux Mint 21.3 Virginia
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
Top
t42
Level 11
Level 11
Posts: 3747
Joined: Mon Jan 20, 2014 6:48 pm

Re: The Linux "Copy Problem" and the Mint desktop.

Post by t42 »

Pjotr wrote: ⤴Sun Jan 28, 2024 5:26 am whether fiddling with dirty_ratio and dirty_background_ratio helps:
https://easylinuxtipsproject.blogspot.c ... .html#ID11
(item 11)
Please note that proposed there values are about 0.5 - 0.3 per cent for 64 GB RAM shown by inxi.
-=t42=-
Top
DisturbedDragon
Level 5
Level 5
Posts: 574
Joined: Mon Oct 29, 2012 6:29 pm
Location: Texas

Re: The Linux "Copy Problem" and the Mint desktop.

Post by DisturbedDragon »

Not sure about the CPU usage issue. Never even tried to monitor such a mundane task. Most writes are complete without a progress window ever opening. That said, you are getting full network bandwidth from between server and client.

My setup is very similar to yours with Mint Cinnamon running on R9 5950x but with 5.15.0-52-lowlatency and TrueNAS on VM, though I am using eSXi on SM board with Epyc CPU.

The writes between internal NVMe drives is not uncommon. Depends on the file system chosen for each, slot assignment and if that slot is properly configured for the installed device. I would start by confirming latest firmware on the board and drives. I suspect the Optane drive though I leave it to you to confirm. Internal writes between my Inland (Gen4 in a Gen4 slot), Mushkin Pilot( Gen3 on PCIe card) and Samsung Gen3 on PCIe card) are 3GB/s to 4GB/s. Between the two internal Gen4 Inlands it's around 7GB/s.

I highly recommend checking your kernel version for possible bugs and firmware for all devices. You could also try connecting another M.2 to see how it performs with the Samsung drive.
Last edited by DisturbedDragon on Mon Jan 29, 2024 7:28 am, edited 1 time in total.
AMD Ryzen 9 5950X 16C/32T | MSI MPG x570 Gaming Plus | 2TB Mushkin Pilot-E NVMe | 1TB Crucial P1 NVMe | 2x 2TB Inland Gen4 NVMe | 32GB Trident Z DDR4 3600 | Nvidia RTX4090 | Fedora 39 Cinnamon | Linux Mint 21.3 Cinnamon | Kernel 5.15.x lowlatency
Top
User avatar
Bleys
Level 4
Level 4
Posts: 431
Joined: Wed Apr 20, 2022 4:17 am
Location: Essen, Germany

Re: The Linux "Copy Problem" and the Mint desktop.

Post by Bleys »

Ryzen 5 5600G From m.2 nvme to USB 3 nvme:
https://vimeo.com/manage/videos/907187896
Ryzen 5 5600G, 16GB RAM, 2TB M.2 Crucial P3, Asrock Deskmeet X300, Samsung Odyssey 49", Linux Mint 21
Top
User avatar
PaulL
Level 6
Level 6
Posts: 1089
Joined: Mon Apr 24, 2023 10:57 am
Location: Connecticut

Re: The Linux "Copy Problem" and the Mint desktop.

Post by PaulL »

The block size used for the copy is also relevant; a larger size means more data copied per set of CPU read/write instructions. But there is a point of diminishing returns, especially if there are a number of files in the transfer that have sizes that are not multiples of the block size chosen.

The number of files involved also matters; a thousand small files will inevitably take longer than copying a single file containing the same amount of data. I would also expect a transfer made in a GUI app to take longer, because of the extra overhead. Fastest performance should appear on the command line. (You probably know that already, but just in case. . . .)

If you want to dig into this, try the copying with dd using various block sizes (cp doesn't appear to take a blocksize parameter).

To some extent, the file copying utility can be made smarter about how to perform a large copy without much thought on the user's part, up to the point where investigating the situation starts increasing the total time of the operation.

Remember also that file copies originally were usually between tape and disk, and tape machines had a hard maximum limit to their read/write speed, because magnetic tape is a fragile medium. In such transfers, adjusting the block size to fit the data really helped. Caches integrated into the drive circuitry have helped the situation in some ways (regardless of the type of drive), but to some extent it only appears better to the user, since a lot of the work is being done behind the scenes. Just be glad that the transfer you are dealing with is entirely electronic; at least you are not dealing with spinning platters and tape moving past a read/write head. But even with all-electronic transfers, do you really expect mutli-threaded file transfers to work? How would you keep all the threads and CPU's in synch? One little mistiming, and your data would be garbled.

The moral is that it's tradeoffs all the way down. Advances in technology only change the relative values of the parameters.
Top
CJRoss
Level 1
Level 1
Posts: 30
Joined: Tue Feb 20, 2024 7:42 am

Re: The Linux "Copy Problem" and the Mint desktop.

Post by CJRoss »

I've seen a couple of different threads about the various copying speeds with NVMe, but ATM I can't recall if they were on the TrueNAS or L1Techs forums. IIRC, there was a bottleneck using cp as it's single threaded but I can't remember the comparisons with dd or what the multithreaded suggestions were. That said, here is one thread where people are having some issues with Samsung drive performance. https://forum.level1techs.com/t/samsung ... eed/207006

As has been mentioned here, not all drives and slots are equal. You may be going through the chipset, etc instead of directly to the CPU. If there's a RAID or HBA involved, that will affect things as well.

In regards to NFS to a ZFS server, NFS is multithreaded and spreads the load out well. Depending on the setup, I can get 10G wire speed transfers using it to a ZFS HDD pool. If the ZFS compression is set to lz4, not only is it very fast, but it also quickly aborts if it turns out to not be compressible data. Compression also means less to write to the drives and wide vdevs mean higher sequential performance.
Top
CJRoss
Level 1
Level 1
Posts: 30
Joined: Tue Feb 20, 2024 7:42 am

Re: The Linux "Copy Problem" and the Mint desktop.

Post by CJRoss »

PaulL wrote: ⤴Sat Feb 17, 2024 11:21 pm The moral is that it's tradeoffs all the way down. Advances in technology only change the relative values of the parameters.
It's funny how many people forget that there's always a weakest link. Fixing it just moves the link to some place else that might not be as obvious.
Top
User avatar
AndyMH
Level 21
Level 21
Posts: 13759
Joined: Fri Mar 04, 2016 5:23 pm
Location: Wiltshire

Re: The Linux "Copy Problem" and the Mint desktop.

Post by AndyMH »

If I post hardware serial numbers, and then someone uses those serial numbers on the hardware vendors support systems
Purely for information and alluded to in T42's post, using the z option in inxi suppresses anything sensitive. man inxi for more info. The GUI way with system reports does this automatically. If someone asks for an inxi output and does not include z in the options, I hope someone else on the forum would jump on them.
Thinkcentre M720Q - LM21.3 cinnamon, 4 x T430 - LM21.3 cinnamon, Homebrew desktop i5-8400+GTX1080 Cinnamon 19.0
Top
User avatar
MikeNovember
Level 7
Level 7
Posts: 1856
Joined: Fri Feb 28, 2020 7:37 am
Location: Nice, Paris, France

Re: The Linux "Copy Problem" and the Mint desktop.

Post by MikeNovember »

Hi,

AFAIK, copying a large file has always been a tedious and long task, on Windows, macOS, Linux...

It is not just a question of hardware (of course, the better the hardware, the faster is the copy).

It is also a question of programming and compiling; as an example, in Windows terminal, copying with the command line is much faster than copying using the File Manager and the GUI mode. It seems the GUI mode is more complex, makes some checks that are not there in terminal mode.

I have not made the comparison between Linux cli / GUI. I know that, in GUI mode, Timeshift uses rsync, not bad, but FreeFileSync uses its own way to copy files and is much faster.

You can program a copy function using a low level compiler, or directly make processor calls; you can use GNU logic, that may not be optimized for your processor; you can use a file manager from a Desktop Environment. In simpler Linux distros, you may use a Window Manager instead of a Desktop Environment.

Note also that very few programs are able to use all the processor cores, in parallel processing. When transcoding a video using VLC, it is able to use the 8 cores of my processor; LibreOffice Calc also. Simple GNU logic commands such as move or copy use one core only.

Regards,

MN
_____________________________
Linux Mint 21.3 Mate host with Ubuntu Pro enabled, VMware Workstation Player with Windows 10 Pro guest, ASUS G74SX (i7-2670QM, 16 GB RAM, GTX560M with 3GB RAM, 1TB SSD).
Top
User avatar
Lady Fitzgerald
Level 15
Level 15
Posts: 5821
Joined: Tue Jan 07, 2020 3:12 pm
Location: AZ, SSA (Squabbling States of America)

Re: The Linux "Copy Problem" and the Mint desktop.

Post by Lady Fitzgerald »

MikeNovember wrote: ⤴Wed Mar 06, 2024 1:29 pm ...FreeFileSync uses its own way to copy files and is much faster...
FreeFileSync (FFS), in addition to being my weapon...er...tool of choice for backing up my personal data, is also what I use when I need to move a large number of files in one operation because it is faster, doesn't tie up the computer while it is working, and it can be set to verify each file copy (verifying does slow down the copying process significantly but I value accuracy far more than mere speed).

Cloning a large drive with a lot of data in it, using cloning software, such as Foxclone, Rescuezilla, or Clonezilla (in order of preference), will tie up the computer for a long time. Using FFS to copy the data from one drive to the other will also take a long time but, while FFS is working, you can continue to use the computer. Another advantage of using FFS instead of cloning is the process can be automagically verified for you and any bad copies will appear in a report after FFS is finished. The only disadvantage of using FFS instead of cloning is the UUID of the drive being "cloned" isn't replicated on the "cloned" drive but there is a way to restore the original UUID afterwards in the terminal which takes far, far less time than the amount of time the computer would have been tied up while actually cloning.
Jeannie

To ensure the safety of your data, you have to be proactive, not reactive, so, back it up!
Top
Post Reply

Return to “Chat about Linux”