skler

Hi all, I understand that after a vdev expansion, old blocks keep the old data-to-parity ratio and only newly written data uses the new ratio, so usable space stays lower until data is rewritten. What I’m looking for is a tool or reliable method to detect which blocks/data in the pool have already been rewritten using the new data-to-parity ratio vs which are still using the old layout. Ideally it would let me: detect or list files/blocks that are already rewritten distinguish them from those still using the old parity scheme I am aware of this tool: https://github.com/markusressel/zfs-inplace-rebalancing but as far as I can tell it just rewrites files and doesn’t actually check which blocks are already using the new ratio. Also, does anyone know if zfs rewrite can be used for this purpose? Thanks!

Hi everyone, I have a ZFS Raidz2 pool running on Unraid 7.2, and one of the disks is showing SMART errors. Before it fails completely, I’d like to replace it — what’s the proper procedure to follow in Unraid 7.2? Can this be done directly from the GUI, or does it still require manual commands from the terminal (e.g., zpool replace)? Any step-by-step guidance or best practices would be appreciated :-) Thanks!

Ok, got it. I’m still on 7.1, once 7.2 is released as stable, I’ll upgrade. In the meantime, I’ll use the same approach as the GUI from the CLI (create a new partition and add it by the Linux device name). Thanks a lot!

Maybe I’m wrong, but to expand a pool I’ve used the device ID instead of the Linux device name, and it seems to work: zpool status storage pool: storage state: ONLINE scan: scrub repaired 1000K in 1 days 00:03:24 with 0 errors on Mon Oct 13 03:30:25 2025 expand: expansion of raidz2-0 in progress since Mon Oct 13 10:49:25 2025 65.2G / 87.8T copied at 642M/s, 0.07% done, 1 days 15:48:19 to go config: NAME STATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 sdk1 ONLINE 0 0 0 sdn1 ONLINE 0 0 0 sdr1 ONLINE 0 0 0 sds1 ONLINE 0 0 0 sdt1 ONLINE 0 0 0 sdh1 ONLINE 0 0 0 ata-ST20000NE000-XXXXXX_XXXXXXXX ONLINE 0 0 0 errors: No known data errorsMy question is: if I move, for example, the disk currently in sdk to another slot, or to another controller (e.g., in a JBOD), will the pool still recognize the same disk based on its device name, or would I need to reference its ID again?

Hi Unraid team, I’d like to suggest a feature for future ZFS support in Unraid. Currently, ZFS pools are typically created using Linux device names like sda, sdb, etc. While this works, it can cause issues if disks are moved between systems, controllers, or after hardware changes, since device names are not guaranteed to stay the same. I guess that It would be helpful to have an option to create ZFS pools using persistent device IDs (e.g., /dev/disk/by-id/...). This would: Make pools more portable and robust across hardware changes Reduce the risk of import or resilvering issues caused by device renaming Improve reliability for NAS setups with multiple disks This could be offered as an optional toggle during pool creation, so existing workflows are not affected. However, it’s worth considering potential downsides, that actually I don't know. Additionally, there could be compatibility concerns with certain hardware or Unraid’s current implementation. What do you think about it?

uhm maybe I'm missing something, the mover can move data from one disk of the array to a zfs pool (not included into the array)? I'm quite sure is possible to do it with your unbalancer gui but with the mover I can only empty a disk moving data to the other array disks, or from cache to array etc

Sorry Jorge if I bother you bat can you confirm that "remove pool" doesn't remove the pool (with all my data) from zfs but is something related only to the gui? Ref: Step "on main, click on the first device for that pool and then "remove pool"" from https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/3/#findComment-1537164 One more thing, to move files from the an array disk to this new pool is safe to use unbalanced with -H for hardlink support?

I'm doing it, and seems to work # zpool status zfs pool: zfs state: ONLINE expand: expansion of raidz1-0 in progress since Fri Mar 28 16:58:13 2025 63.5G / 39.6T copied at 349M/s, 0.16% done, 1 days 09:00:19 to go But the GUI is not aligned. It will be fixed to the next array start or I have to wait a system update?

I don't understand how shares will handle pools. One of my shares has been setup to use all disks, but my new ZFS Pool is not recognized. I've created a folder on my pool with the same name of the share, and I'm moving there all data, but if I check the free space on that share there is the ZFS folder. Is it included into the share or not? Which is the practice to move files from disks to the Pool in order to empty any disk one by one and add it to the ZFS Pool?

With the recent release of Unraid 7.1, is it now possible to expand a ZFS Raidz pool?

someone can help me to understand what was the problem? Nvidia drivers? syslog: Oct 28 04:43:38 littleboy php-fpm[16195]: [WARNING] [pool www] child 43401 exited on signal 9 (SIGKILL) after 19.083199 seconds from start Oct 28 05:05:19 littleboy emhttpd: spinning down /dev/sdt Oct 28 05:05:19 littleboy emhttpd: spinning down /dev/sds Oct 28 05:05:58 littleboy php-fpm[16195]: [WARNING] [pool www] child 77142 exited on signal 9 (SIGKILL) after 19.692044 seconds from start Oct 28 05:06:09 littleboy php-fpm[16195]: [WARNING] [pool www] child 83314 exited on signal 9 (SIGKILL) after 11.809331 seconds from start Oct 28 05:10:26 littleboy emhttpd: read SMART /dev/sds Oct 28 05:10:36 littleboy emhttpd: read SMART /dev/sdt Oct 28 05:16:56 littleboy kernel: br-d57e35029abe: port 5(vethba97a0a) entered disabled state Oct 28 05:16:56 littleboy kernel: veth7687662: renamed from eth0 Oct 28 05:16:56 littleboy kernel: br-d57e35029abe: port 5(vethba97a0a) entered disabled state Oct 28 05:16:56 littleboy kernel: device vethba97a0a left promiscuous mode Oct 28 05:16:56 littleboy kernel: br-d57e35029abe: port 5(vethba97a0a) entered disabled state Oct 28 05:16:58 littleboy kernel: br-d57e35029abe: port 5(vethf86f92f) entered blocking state Oct 28 05:16:58 littleboy kernel: br-d57e35029abe: port 5(vethf86f92f) entered disabled state Oct 28 05:16:58 littleboy kernel: device vethf86f92f entered promiscuous mode Oct 28 05:17:27 littleboy kernel: eth0: renamed from vethf4a2473 Oct 28 05:17:27 littleboy kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethf86f92f: link becomes ready Oct 28 05:17:27 littleboy kernel: br-d57e35029abe: port 5(vethf86f92f) entered blocking state Oct 28 05:17:27 littleboy kernel: br-d57e35029abe: port 5(vethf86f92f) entered forwarding state Oct 28 05:43:08 littleboy emhttpd: spinning down /dev/sdo Oct 28 05:43:59 littleboy emhttpd: spinning down /dev/sdk Oct 28 05:49:26 littleboy emhttpd: spinning down /dev/sdt Oct 28 05:54:03 littleboy emhttpd: spinning down /dev/sds Oct 28 06:00:19 littleboy kernel: br-d57e35029abe: port 8(veth0a6e27d) entered disabled state Oct 28 06:00:19 littleboy kernel: vethc1800e3: renamed from eth0 Oct 28 06:00:19 littleboy kernel: br-d57e35029abe: port 8(veth0a6e27d) entered disabled state Oct 28 06:00:19 littleboy kernel: device veth0a6e27d left promiscuous mode Oct 28 06:00:19 littleboy kernel: br-d57e35029abe: port 8(veth0a6e27d) entered disabled state Oct 28 06:00:19 littleboy kernel: br-d57e35029abe: port 8(vethad12f8e) entered blocking state Oct 28 06:00:19 littleboy kernel: br-d57e35029abe: port 8(vethad12f8e) entered disabled state Oct 28 06:00:19 littleboy kernel: device vethad12f8e entered promiscuous mode Oct 28 06:00:19 littleboy kernel: br-d57e35029abe: port 8(vethad12f8e) entered blocking state Oct 28 06:00:19 littleboy kernel: br-d57e35029abe: port 8(vethad12f8e) entered forwarding state Oct 28 06:00:20 littleboy kernel: br-d57e35029abe: port 8(vethad12f8e) entered disabled state Oct 28 06:00:30 littleboy kernel: eth0: renamed from veth4933074 Oct 28 06:00:30 littleboy kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethad12f8e: link becomes ready Oct 28 06:00:30 littleboy kernel: br-d57e35029abe: port 8(vethad12f8e) entered blocking state Oct 28 06:00:30 littleboy kernel: br-d57e35029abe: port 8(vethad12f8e) entered forwarding state Oct 28 06:00:39 littleboy Parity Check Tuning: Send notification: mover running: (type=normal link=/Settings/Scheduler) Oct 28 06:00:48 littleboy emhttpd: read SMART /dev/sds Oct 28 06:00:48 littleboy emhttpd: read SMART /dev/sdo Oct 28 06:00:49 littleboy kernel: mdcmd (72): nocheck PAUSE Oct 28 06:00:49 littleboy kernel: Oct 28 06:00:50 littleboy kernel: md: recovery thread: exit status: -4 Oct 28 06:00:51 littleboy crond[3291]: failed parsing crontab for user root: php /usr/local/emhttp/plugins/appdata.backup/scripts/backup.php > /dev/null 2>&1 Oct 28 06:01:01 littleboy Parity Check Tuning: Send notification: Paused: Automatic Correcting Parity-Check (81.4% completed) (type=normal link=/Settings/Scheduler) Oct 28 06:01:02 littleboy emhttpd: read SMART /dev/sdk Oct 28 06:01:08 littleboy emhttpd: read SMART /dev/sdt Oct 28 06:02:41 littleboy kernel: BUG: unable to handle page fault for address: ffffc902b6118200 Oct 28 06:02:41 littleboy kernel: #PF: supervisor write access in kernel mode Oct 28 06:02:41 littleboy kernel: #PF: error_code(0x0002) - not-present page Oct 28 06:02:41 littleboy kernel: PGD 100000067 P4D 100000067 PUD 5098f3067 PMD 0 Oct 28 06:02:41 littleboy kernel: Oops: 0002 [#1] PREEMPT SMP PTI Oct 28 06:02:41 littleboy kernel: CPU: 14 PID: 2325 Comm: nv_open_q Tainted: P O 6.1.106-Unraid #1 Oct 28 06:02:41 littleboy kernel: Hardware name: VxRack AS PowerEdge R740xd/0RR8YK, BIOS 2.21.2 02/19/2024 Oct 28 06:02:41 littleboy kernel: RIP: 0010:os_mem_copy+0x26/0x5c [nvidia] Oct 28 06:02:41 littleboy kernel: Code: 79 cb 86 df 0f 1f 44 00 00 83 fa 7f 49 89 f8 48 89 f9 76 2e 48 89 f8 48 09 f0 83 e0 03 75 23 89 d1 83 e2 03 c1 e9 02 8b 3c 86 <41> 89 3c 80 48 ff c0 39 c1 75 f2 89 c8 48 c1 e0 02 49 8d 0c 00 48 Oct 28 06:02:41 littleboy kernel: RSP: 0018:ffffc9000fb07940 EFLAGS: 00010206 Oct 28 06:02:41 littleboy kernel: RAX: 0000000000000000 RBX: ffff88823d6f74d8 RCX: 0000000000000200 Oct 28 06:02:41 littleboy kernel: RDX: 0000000000000000 RSI: ffff8885b1061008 RDI: 000000000000000c Oct 28 06:02:41 littleboy kernel: RBP: ffff88897d25ab80 R08: ffffc902b6118200 R09: 0000000000000000 Oct 28 06:02:41 littleboy kernel: R10: 000000000010a804 R11: 0000000000000000 R12: 000000000000000c Oct 28 06:02:41 littleboy kernel: R13: ffff888c16b70008 R14: ffff88912f228018 R15: ffff88912f228d73 Oct 28 06:02:41 littleboy kernel: FS: 0000000000000000(0000) GS:ffff889fff7c0000(0000) knlGS:0000000000000000 Oct 28 06:02:41 littleboy kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 28 06:02:41 littleboy kernel: CR2: ffffc902b6118200 CR3: 000000030cfea006 CR4: 00000000007706e0 Oct 28 06:02:41 littleboy kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Oct 28 06:02:41 littleboy kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Oct 28 06:02:41 littleboy kernel: PKRU: 55555554 Oct 28 06:02:41 littleboy kernel: Call Trace: Oct 28 06:02:41 littleboy kernel: <TASK> Oct 28 06:02:41 littleboy kernel: ? __die_body+0x1a/0x5c Oct 28 06:02:41 littleboy kernel: ? page_fault_oops+0x329/0x376 Oct 28 06:02:41 littleboy kernel: ? search_bpf_extables+0x5d/0x68 Oct 28 06:02:41 littleboy kernel: ? fixup_exception+0x22/0x24b Oct 28 06:02:41 littleboy kernel: ? exc_page_fault+0xf4/0x11d Oct 28 06:02:41 littleboy kernel: ? asm_exc_page_fault+0x22/0x30 Oct 28 06:02:41 littleboy kernel: ? os_mem_copy+0x26/0x5c [nvidia] Oct 28 06:02:41 littleboy kernel: _nv012530rm+0x5c/0x100 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv012511rm+0x6e/0x1e0 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv026376rm+0x1a3/0x290 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv047707rm+0x425/0xac2 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv047728rm+0x141/0x3f0 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv047728rm+0x103/0x3f0 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv053958rm+0x6d/0xb0 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv053958rm+0x35/0xb0 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv015274rm+0x43/0x90 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv048250rm+0x1fd/0x260 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv046902rm+0x27/0xb0 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv014211rm+0xb6/0x120 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv048250rm+0x1fd/0x260 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv046108rm+0xd1/0x1d0 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv014003rm+0x5a/0xd0 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv048250rm+0x1fd/0x260 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv011731rm+0x101/0x160 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv048250rm+0x1fd/0x260 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv015558rm+0xd1/0x200 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv048250rm+0x1fd/0x260 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv015606rm+0xf1/0x2f0 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv048250rm+0x1fd/0x260 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv018681rm+0x35/0x110 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv019854rm+0x151/0x400 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv028628rm+0x98/0x1f0 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv000804rm+0x1e8/0x347 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _nv000753rm+0x486/0x20c0 [nvidia] Oct 28 06:02:41 littleboy kernel: ? rm_init_adapter+0xcd/0xf0 [nvidia] Oct 28 06:02:41 littleboy kernel: ? ttwu_queue_wakelist+0x9a/0xcf Oct 28 06:02:41 littleboy kernel: ? nv_open_device+0x586/0x875 [nvidia] Oct 28 06:02:41 littleboy kernel: ? nvidia_open_deferred+0x33/0x7f [nvidia] Oct 28 06:02:41 littleboy kernel: ? _raw_q_schedule+0x69/0x69 [nvidia] Oct 28 06:02:41 littleboy kernel: ? _main_loop+0xf1/0x115 [nvidia] Oct 28 06:02:41 littleboy kernel: ? kthread+0xe4/0xef Oct 28 06:02:41 littleboy kernel: ? kthread_complete_and_exit+0x1b/0x1b Oct 28 06:02:41 littleboy kernel: ? ret_from_fork+0x1f/0x30 Oct 28 06:02:41 littleboy kernel: </TASK> Oct 28 06:02:41 littleboy kernel: Modules linked in: af_packet bluetooth ecdh_generic ecc xt_connmark xt_mark iptable_mangle xt_comment iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha nvidia_uvm(PO) veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter bridge xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod tcp_diag inet_diag ipmi_devintf ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs 8021q garp mrp stp llc macvtap macvlan tap bonding tls ixgbe xfrm_algo mdio igb intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal coretemp zfs(PO) nvidia_drm(PO) nvidia_modeset(PO) kvm_intel zunicode(PO) zzstd(O) kvm zlua(O) zavl(PO) nvidia(PO) icp(PO) crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel Oct 28 06:02:41 littleboy kernel: crypto_simd cryptd zcommon(PO) rapl znvpair(PO) mgag200 ipmi_ssif video drm_shmem_helper intel_cstate drm_kms_helper wmi_bmof spl(O) i2c_i801 drm nvme backlight i2c_smbus syscopyarea i2c_algo_bit mei_me sysfillrect ahci intel_uncore sysimgblt acpi_ipmi megaraid_sas nvme_core i2c_core fb_sys_fops mei intel_pch_thermal libahci wmi ipmi_si acpi_power_meter button unix [last unloaded: xfrm_algo] Oct 28 06:02:41 littleboy kernel: CR2: ffffc902b6118200 Oct 28 06:02:41 littleboy kernel: ---[ end trace 0000000000000000 ]--- Oct 28 06:02:41 littleboy kernel: RIP: 0010:os_mem_copy+0x26/0x5c [nvidia] Oct 28 06:02:41 littleboy kernel: Code: 79 cb 86 df 0f 1f 44 00 00 83 fa 7f 49 89 f8 48 89 f9 76 2e 48 89 f8 48 09 f0 83 e0 03 75 23 89 d1 83 e2 03 c1 e9 02 8b 3c 86 <41> 89 3c 80 48 ff c0 39 c1 75 f2 89 c8 48 c1 e0 02 49 8d 0c 00 48 Oct 28 06:02:41 littleboy kernel: RSP: 0018:ffffc9000fb07940 EFLAGS: 00010206 Oct 28 06:02:41 littleboy kernel: RAX: 0000000000000000 RBX: ffff88823d6f74d8 RCX: 0000000000000200 Oct 28 06:02:41 littleboy kernel: RDX: 0000000000000000 RSI: ffff8885b1061008 RDI: 000000000000000c Oct 28 06:02:41 littleboy kernel: RBP: ffff88897d25ab80 R08: ffffc902b6118200 R09: 0000000000000000 Oct 28 06:02:41 littleboy kernel: R10: 000000000010a804 R11: 0000000000000000 R12: 000000000000000c Oct 28 06:02:41 littleboy kernel: R13: ffff888c16b70008 R14: ffff88912f228018 R15: ffff88912f228d73 Oct 28 06:02:41 littleboy kernel: FS: 0000000000000000(0000) GS:ffff889fff7c0000(0000) knlGS:0000000000000000 Oct 28 06:02:41 littleboy kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 28 06:02:41 littleboy kernel: CR2: ffffc902b6118200 CR3: 000000030cfea006 CR4: 00000000007706e0 Oct 28 06:02:41 littleboy kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Oct 28 06:02:41 littleboy kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Oct 28 06:02:41 littleboy kernel: PKRU: 55555554 Oct 28 06:02:41 littleboy kernel: note: nv_open_q[2325] exited with irqs disabled

I've the crash report now, there was a problem with that docker but sometimes also my NVIDIA GPU seems to crash Could be due to the driver update done without a reboot? Jul 24 06:30:38 littleboy kernel: NVRM: GPU 0000:af:00.0: RmInitAdapter failed! (0x25:0x51:1589) Jul 24 06:30:38 littleboy kernel: NVRM: GPU 0000:af:00.0: rm_init_adapter failed, device minor number 0 Jul 24 06:31:23 littleboy kernel: BUG: unable to handle page fault for address: ffffc90287112a00 Jul 24 06:31:23 littleboy kernel: #PF: supervisor write access in kernel mode Jul 24 06:31:23 littleboy kernel: #PF: error_code(0x0002) - not-present page Jul 24 06:31:23 littleboy kernel: PGD 100000067 P4D 100000067 PUD 3d339b9067 PMD 0 Jul 24 06:31:23 littleboy kernel: Oops: 0002 [#1] PREEMPT SMP PTI Jul 24 06:31:23 littleboy kernel: CPU: 50 PID: 2329 Comm: nv_open_q Tainted: P O 6.1.79-Unraid #1 Jul 24 06:31:23 littleboy kernel: Hardware name: VxRack AS PowerEdge R740xd/0RR8YK, BIOS 2.21.2 02/19/2024 Jul 24 06:31:23 littleboy kernel: RIP: 0010:os_mem_copy_custom+0x2c/0x60 [nvidia] Jul 24 06:31:23 littleboy kernel: Code: 44 00 00 83 fa 7f 49 89 f8 48 89 f9 76 0b 48 89 f8 48 09 f0 83 e0 03 74 06 89 d2 31 c0 eb 25 89 d1 83 e2 03 c1 e9 02 8b 3c 86 <41> 89 3c 80 48 ff c0 39 c1 75 f2 89 c8 48 c1 e0 02 49 8d 0c 00 48 Jul 24 06:31:23 littleboy kernel: RSP: 0018:ffffc9000f477930 EFLAGS: 00010206 Jul 24 06:31:23 littleboy kernel: RAX: 0000000000000000 RBX: ffff8882faf61cd8 RCX: 0000000000000200 Jul 24 06:31:23 littleboy kernel: RDX: 0000000000000000 RSI: ffff888eb7b24008 RDI: 000000000000000d Jul 24 06:31:23 littleboy kernel: RBP: ffff88af099aab80 R08: ffffc90287112a00 R09: 0000000000000000 Jul 24 06:31:23 littleboy kernel: R10: 000000000010a804 R11: 0000000000000000 R12: 000000000000000d Jul 24 06:31:23 littleboy kernel: R13: ffff889924c88008 R14: ffff8885b15a2010 R15: ffff8885b15a2f13 Jul 24 06:31:23 littleboy kernel: FS: 0000000000000000(0000) GS:ffff889fffc40000(0000) knlGS:0000000000000000 Jul 24 06:31:23 littleboy kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 24 06:31:23 littleboy kernel: CR2: ffffc90287112a00 CR3: 00000023a29d6001 CR4: 00000000007706e0 Jul 24 06:31:23 littleboy kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jul 24 06:31:23 littleboy kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jul 24 06:31:23 littleboy kernel: PKRU: 55555554 Jul 24 06:31:23 littleboy kernel: Call Trace: Jul 24 06:31:23 littleboy kernel: <TASK> Jul 24 06:31:23 littleboy kernel: ? __die_body+0x1a/0x5c Jul 24 06:31:23 littleboy kernel: ? page_fault_oops+0x329/0x376 Jul 24 06:31:23 littleboy kernel: ? fixup_exception+0x22/0x24b Jul 24 06:31:23 littleboy kernel: ? exc_page_fault+0xf4/0x11d Jul 24 06:31:23 littleboy kernel: ? asm_exc_page_fault+0x22/0x30 Jul 24 06:31:23 littleboy kernel: ? os_mem_copy_custom+0x2c/0x60 [nvidia] Jul 24 06:31:23 littleboy kernel: _nv011987rm+0x5c/0x100 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv011968rm+0x6e/0x1d0 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv024663rm+0x1a3/0x290 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv043897rm+0x428/0xad2 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv043916rm+0x148/0x3f0 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv043916rm+0x10d/0x3f0 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv049576rm+0x6d/0xb0 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv049576rm+0x35/0xb0 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv014517rm+0x51/0xc0 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv044401rm+0x1fd/0x260 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv013557rm+0xa8/0x210 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv044401rm+0x1fd/0x260 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv042458rm+0xd1/0x1d0 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv013346rm+0x5a/0xd0 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv044401rm+0x1fd/0x260 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv011239rm+0xe1/0x160 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv044401rm+0x1fd/0x260 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv050979rm+0x20/0x2e0 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv014771rm+0x50/0x100 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv044401rm+0x1fd/0x260 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv014815rm+0xf1/0x2f0 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv044401rm+0x1fd/0x260 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv017529rm+0x35/0x110 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv018649rm+0x13b/0x3d0 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv026712rm+0x97/0x1a0 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv000773rm+0x1b3/0x313 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _nv000720rm+0x482/0x20e0 [nvidia] Jul 24 06:31:23 littleboy kernel: ? rm_init_adapter+0xcd/0xf0 [nvidia] Jul 24 06:31:23 littleboy kernel: ? ttwu_queue_wakelist+0x9a/0xcf Jul 24 06:31:23 littleboy kernel: ? nv_open_device+0x57a/0x869 [nvidia] Jul 24 06:31:23 littleboy kernel: ? nvidia_open_deferred+0x33/0x7f [nvidia] Jul 24 06:31:23 littleboy kernel: ? _raw_q_schedule+0x69/0x69 [nvidia] Jul 24 06:31:23 littleboy kernel: ? _main_loop+0xf1/0x115 [nvidia] Jul 24 06:31:23 littleboy kernel: ? kthread+0xe4/0xef Jul 24 06:31:23 littleboy kernel: ? kthread_complete_and_exit+0x1b/0x1b Jul 24 06:31:23 littleboy kernel: ? ret_from_fork+0x1f/0x30 Jul 24 06:31:23 littleboy kernel: </TASK> Jul 24 06:31:23 littleboy kernel: Modules linked in: joydev uinput af_packet bluetooth ecdh_generic ecc xt_connmark xt_mark iptable_mangle xt_comment iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha nvidia_uvm(PO) veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter bridge xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod tcp_diag inet_diag ipmi_devintf ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs 8021q garp mrp stp llc macvtap macvlan tap bonding tls ixgbe xfrm_algo mdio igb intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal nvidia_drm(PO) coretemp nvidia_modeset(PO) kvm_intel zfs(PO) kvm nvidia(PO) zunicode(PO) zzstd(O) crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 mgag200 zlua(O) sha1_ssse3 Jul 24 06:31:23 littleboy kernel: ipmi_ssif video drm_shmem_helper zavl(PO) aesni_intel crypto_simd drm_kms_helper icp(PO) cryptd zcommon(PO) znvpair(PO) drm rapl spl(O) wmi_bmof backlight intel_cstate i2c_i801 acpi_ipmi mei_me syscopyarea nvme i2c_algo_bit i2c_smbus intel_uncore sysfillrect ahci sysimgblt mei i2c_core nvme_core megaraid_sas fb_sys_fops libahci intel_pch_thermal wmi ipmi_si acpi_power_meter button unix [last unloaded: xfrm_algo] Jul 24 06:31:23 littleboy kernel: CR2: ffffc90287112a00 Jul 24 06:31:23 littleboy kernel: ---[ end trace 0000000000000000 ]--- Jul 24 06:31:23 littleboy kernel: RIP: 0010:os_mem_copy_custom+0x2c/0x60 [nvidia] Jul 24 06:31:23 littleboy kernel: Code: 44 00 00 83 fa 7f 49 89 f8 48 89 f9 76 0b 48 89 f8 48 09 f0 83 e0 03 74 06 89 d2 31 c0 eb 25 89 d1 83 e2 03 c1 e9 02 8b 3c 86 <41> 89 3c 80 48 ff c0 39 c1 75 f2 89 c8 48 c1 e0 02 49 8d 0c 00 48 Jul 24 06:31:23 littleboy kernel: RSP: 0018:ffffc9000f477930 EFLAGS: 00010206 Jul 24 06:31:23 littleboy kernel: RAX: 0000000000000000 RBX: ffff8882faf61cd8 RCX: 0000000000000200 Jul 24 06:31:23 littleboy kernel: RDX: 0000000000000000 RSI: ffff888eb7b24008 RDI: 000000000000000d Jul 24 06:31:23 littleboy kernel: RBP: ffff88af099aab80 R08: ffffc90287112a00 R09: 0000000000000000 Jul 24 06:31:23 littleboy kernel: R10: 000000000010a804 R11: 0000000000000000 R12: 000000000000000d Jul 24 06:31:23 littleboy kernel: R13: ffff889924c88008 R14: ffff8885b15a2010 R15: ffff8885b15a2f13 Jul 24 06:31:23 littleboy kernel: FS: 0000000000000000(0000) GS:ffff889fffc40000(0000) knlGS:0000000000000000 Jul 24 06:31:23 littleboy kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 24 06:31:23 littleboy kernel: CR2: ffffc90287112a00 CR3: 00000023a29d6001 CR4: 00000000007706e0 Jul 24 06:31:23 littleboy kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jul 24 06:31:23 littleboy kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jul 24 06:31:23 littleboy kernel: PKRU: 55555554 Jul 24 06:31:23 littleboy kernel: note: nv_open_q[2329] exited with irqs disabled Jul 24 06:31:26 littleboy kernel: BUG: unable to handle page fault for address: ffffc9000f477df8 Jul 24 06:31:26 littleboy kernel: #PF: supervisor read access in kernel mode Jul 24 06:31:26 littleboy kernel: #PF: error_code(0x0000) - not-present page Jul 24 06:31:26 littleboy kernel: PGD 100000067 P4D 100000067 PUD 1001be067 PMD 208b1de067 PTE 0 Jul 24 06:31:26 littleboy kernel: Oops: 0000 [#2] PREEMPT SMP PTI Jul 24 06:31:26 littleboy kernel: CPU: 78 PID: 50540 Comm: nvidia-smi Tainted: P D O 6.1.79-Unraid #1 Jul 24 06:31:26 littleboy kernel: Hardware name: VxRack AS PowerEdge R740xd/0RR8YK, BIOS 2.21.2 02/19/2024 Jul 24 06:31:26 littleboy kernel: RIP: 0010:_nv012504rm+0x3c/0x310 [nvidia] Jul 24 06:31:26 littleboy kernel: Code: 48 63 47 08 48 01 c2 48 8b 07 48 85 c0 75 1b e9 2b 02 00 00 66 2e 0f 1f 84 00 00 00 00 00 48 8b 48 10 48 85 c9 74 17 48 89 c8 <48> 39 30 77 ef 0f 83 f9 01 00 00 48 8b 48 18 48 85 c9 75 e9 48 89 Jul 24 06:31:26 littleboy kernel: RSP: 0018:ffffc9002a203d98 EFLAGS: 00010082 Jul 24 06:31:26 littleboy kernel: RAX: ffffc9000f477df8 RBX: ffffffffa2910a67 RCX: fffffffdda3e82fd Jul 24 06:31:26 littleboy kernel: RDX: ffffc9002a203e10 RSI: 000000000000c56c RDI: ffffffffa4f1e5d8 Jul 24 06:31:26 littleboy kernel: RBP: ffff888321f86000 R08: 0000000000000000 R09: ffffc9002a203e38 Jul 24 06:31:26 littleboy kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffffc9002a203dc0 Jul 24 06:31:26 littleboy kernel: R13: ffff888ddf6d1780 R14: 0000000000000048 R15: 000000000000001f Jul 24 06:31:26 littleboy kernel: FS: 000014e2068e31c0(0000) GS:ffff889ffffc0000(0000) knlGS:0000000000000000 Jul 24 06:31:26 littleboy kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 24 06:31:26 littleboy kernel: CR2: ffffc9000f477df8 CR3: 00000006cfee8004 CR4: 00000000007706e0 Jul 24 06:31:26 littleboy kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jul 24 06:31:26 littleboy kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jul 24 06:31:26 littleboy kernel: PKRU: 55555554 Jul 24 06:31:26 littleboy kernel: Call Trace: Jul 24 06:31:26 littleboy kernel: <TASK> Jul 24 06:31:26 littleboy kernel: ? __die_body+0x1a/0x5c Jul 24 06:31:26 littleboy kernel: ? page_fault_oops+0x329/0x376 Jul 24 06:31:26 littleboy kernel: ? fixup_exception+0x22/0x24b Jul 24 06:31:26 littleboy kernel: ? exc_page_fault+0xf4/0x11d Jul 24 06:31:26 littleboy kernel: ? asm_exc_page_fault+0x22/0x30 Jul 24 06:31:26 littleboy kernel: ? rm_perform_version_check+0x37/0x150 [nvidia] Jul 24 06:31:26 littleboy kernel: ? _nv012504rm+0x3c/0x310 [nvidia] Jul 24 06:31:26 littleboy kernel: ? rm_perform_version_check+0x37/0x150 [nvidia] Jul 24 06:31:26 littleboy kernel: ? _nv049845rm+0xd6/0x1d0 [nvidia] Jul 24 06:31:26 littleboy kernel: ? rm_perform_version_check+0x37/0x150 [nvidia] Jul 24 06:31:26 littleboy kernel: ? nvidia_unlocked_ioctl+0x4b1/0x6c2 [nvidia] Jul 24 06:31:26 littleboy kernel: ? _raw_spin_unlock+0x14/0x29 Jul 24 06:31:26 littleboy kernel: ? do_fcntl+0x19a/0x569 Jul 24 06:31:26 littleboy kernel: ? vfs_ioctl+0x1b/0x2f Jul 24 06:31:26 littleboy kernel: ? __do_sys_ioctl+0x52/0x78 Jul 24 06:31:26 littleboy kernel: ? do_syscall_64+0x68/0x81 Jul 24 06:31:26 littleboy kernel: ? entry_SYSCALL_64_after_hwframe+0x64/0xce Jul 24 06:31:26 littleboy kernel: </TASK> Jul 24 06:31:26 littleboy kernel: Modules linked in: joydev uinput af_packet bluetooth ecdh_generic ecc xt_connmark xt_mark iptable_mangle xt_comment iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha nvidia_uvm(PO) veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter bridge xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod tcp_diag inet_diag ipmi_devintf ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs 8021q garp mrp stp llc macvtap macvlan tap bonding tls ixgbe xfrm_algo mdio igb intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal nvidia_drm(PO) coretemp nvidia_modeset(PO) kvm_intel zfs(PO) kvm nvidia(PO) zunicode(PO) zzstd(O) crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 mgag200 zlua(O) sha1_ssse3 Jul 24 06:31:26 littleboy kernel: ipmi_ssif video drm_shmem_helper zavl(PO) aesni_intel crypto_simd drm_kms_helper icp(PO) cryptd zcommon(PO) znvpair(PO) drm rapl spl(O) wmi_bmof backlight intel_cstate i2c_i801 acpi_ipmi mei_me syscopyarea nvme i2c_algo_bit i2c_smbus intel_uncore sysfillrect ahci sysimgblt mei i2c_core nvme_core megaraid_sas fb_sys_fops libahci intel_pch_thermal wmi ipmi_si acpi_power_meter button unix [last unloaded: xfrm_algo] Jul 24 06:31:26 littleboy kernel: CR2: ffffc9000f477df8 Jul 24 06:31:26 littleboy kernel: ---[ end trace 0000000000000000 ]--- Jul 24 06:31:26 littleboy kernel: RIP: 0010:os_mem_copy_custom+0x2c/0x60 [nvidia] Jul 24 06:31:26 littleboy kernel: Code: 44 00 00 83 fa 7f 49 89 f8 48 89 f9 76 0b 48 89 f8 48 09 f0 83 e0 03 74 06 89 d2 31 c0 eb 25 89 d1 83 e2 03 c1 e9 02 8b 3c 86 <41> 89 3c 80 48 ff c0 39 c1 75 f2 89 c8 48 c1 e0 02 49 8d 0c 00 48 Jul 24 06:31:26 littleboy kernel: RSP: 0018:ffffc9000f477930 EFLAGS: 00010206 Jul 24 06:31:26 littleboy kernel: RAX: 0000000000000000 RBX: ffff8882faf61cd8 RCX: 0000000000000200 Jul 24 06:31:26 littleboy kernel: RDX: 0000000000000000 RSI: ffff888eb7b24008 RDI: 000000000000000d Jul 24 06:31:26 littleboy kernel: RBP: ffff88af099aab80 R08: ffffc90287112a00 R09: 0000000000000000 Jul 24 06:31:26 littleboy kernel: R10: 000000000010a804 R11: 0000000000000000 R12: 000000000000000d Jul 24 06:31:26 littleboy kernel: R13: ffff889924c88008 R14: ffff8885b15a2010 R15: ffff8885b15a2f13 Jul 24 06:31:26 littleboy kernel: FS: 000014e2068e31c0(0000) GS:ffff889ffffc0000(0000) knlGS:0000000000000000 Jul 24 06:31:26 littleboy kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 24 06:31:26 littleboy kernel: CR2: ffffc9000f477df8 CR3: 00000006cfee8004 CR4: 00000000007706e0 Jul 24 06:31:26 littleboy kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jul 24 06:31:26 littleboy kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jul 24 06:31:26 littleboy kernel: PKRU: 55555554 Jul 24 06:31:26 littleboy kernel: note: nvidia-smi[50540] exited with irqs disabled Jul 24 06:31:26 littleboy kernel: note: nvidia-smi[50540] exited with preempt_count 1 Jul 24 11:04:12 littleboy kernel: mdcmd (36): set md_write_method 1 Jul 24 11:04:12 littleboy kernel:

This has fixed the issue for me

In my system there is a memory leak on QbittorrentVPN container. The ram grow up until crash the system. I've limited my resource on docker to 94GB of RAM (from 22.30 to 9.00 the system runs in power saving mode) And the system should be limited to 32GB + 8GB for torrent checks: Someone can help me to understand what I can do to avoid it?

well.. I have a docker container with the same footprint. is it possible to limit the ram usage of a container?