TheSkaz

Members
  • Posts

    106
  • Joined

  • Last visited

Everything posted by TheSkaz

  1. I have enabled NFS in both places, I am not trying to share out a "device", but a mountpoint/folder. for example, I want to share out /fast/ and /tank/
  2. can you use UD to share out a folder through NFS? if so, are there instructions somewhere?
  3. For shares done in the traditional Unraid way, I know how to share a folder via NFS. I would like to share a zfs mountpoint through NFS, to another Unraid Server. I know that normally, you edit the /etc/exports file and add the mount points in there, but after a few hours or so, unraid clears it and drops the shares. this is not during a reboot. I was told before that unraid loads everything from the boot drive, so I editied the go file to add the lines to /etc/exports, and that doesnt really work either. is there a known way to ensure that an exported folder will persist?
  4. thats the thing. I would like to be able to read these GPFs and get to the bottom of what it is. if its Plex, or Grafana, or whatever, I can address it. My ask is not what caused the GPF, its more "how can I read it" so that I can become more self-sufficient, i guess.
  5. I have done 10+ full MemTest86 runs over the course of past year. Every response to a fault has been about memory trying write to an invalid address, or other memory issues. I have replaced the RAM with 2 different kits. did, in fact, RMA one kit. but I have ran a recent memtest (takes 3-4 days) and 0 issues.
  6. I have had 1000s of these over the past year, and I cant read them. I have a quasi-software eng background so I should be able to pick it up quickly. Can someone break this down and tell me what the issue is? seems its zfs, but what in zfs is the issue? Dec 12 06:26:23 Tower kernel: general protection fault, probably for non-canonical address 0x454848a8154e84c5: 0000 [#4] SMP NOPTI Dec 12 06:26:23 Tower kernel: CPU: 105 PID: 55009 Comm: grafana-server Tainted: P S D O 5.14.15-Unraid #1 Dec 12 06:26:23 Tower kernel: Hardware name: ASUS System Product Name/ROG ZENITH II EXTREME ALPHA, BIOS 1402 01/15/2021 Dec 12 06:26:23 Tower kernel: RIP: 0010:kmem_cache_alloc+0x9c/0x176 Dec 12 06:26:23 Tower kernel: Code: 48 89 04 24 74 05 48 85 c0 75 16 4c 89 f1 83 ca ff 89 ee 4c 89 e7 e8 17 ff ff ff 48 89 04 24 eb 26 41 8b 4c 24 28 49 8b 3c 24 <48> 8b 1c 08 48 8d 4a 01 65 48 0f c7 0f 0f 94 c0 84 c0 74 a9 41 8b Dec 12 06:26:23 Tower kernel: RSP: 0018:ffffc9001271f7b0 EFLAGS: 00010202 Dec 12 06:26:23 Tower kernel: RAX: 454848a8154e84ad RBX: ffff8881242c1e00 RCX: 0000000000000018 Dec 12 06:26:23 Tower kernel: RDX: 0000000000069ad6 RSI: 0000000000042c00 RDI: 00006040c103eae0 Dec 12 06:26:23 Tower kernel: RBP: 0000000000042c00 R08: ffffe8ffff87eae0 R09: 0000000000000200 Dec 12 06:26:23 Tower kernel: R10: ffffc9001271fa98 R11: ffff888121c40000 R12: ffff888186a3c400 Dec 12 06:26:23 Tower kernel: R13: ffff888186a3c400 R14: ffffffffa0060cbc R15: ffff88b749691e00 Dec 12 06:26:23 Tower kernel: FS: 0000151080106f20(0000) GS:ffff88bf3e840000(0000) knlGS:0000000000000000 Dec 12 06:26:23 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 12 06:26:23 Tower kernel: CR2: 00000078000fdf50 CR3: 00000035541d8000 CR4: 0000000000350ee0 Dec 12 06:26:23 Tower kernel: Call Trace: Dec 12 06:26:23 Tower kernel: spl_kmem_cache_alloc+0x4a/0x609 [spl] Dec 12 06:26:23 Tower kernel: ? spl_kmem_cache_alloc+0x5e0/0x609 [spl] Dec 12 06:26:23 Tower kernel: zio_add_child+0x3a/0x14f [zfs] Dec 12 06:26:23 Tower kernel: zio_create+0x2e5/0x303 [zfs] Dec 12 06:26:23 Tower kernel: zio_read+0x62/0x67 [zfs] Dec 12 06:26:23 Tower kernel: ? arc_buf_alloc_impl.isra.0+0x28c/0x28c [zfs] Dec 12 06:26:23 Tower kernel: arc_read+0xe51/0xef3 [zfs] Dec 12 06:26:23 Tower kernel: dbuf_read_impl.constprop.0+0x4ce/0x54a [zfs] Dec 12 06:26:23 Tower kernel: dbuf_read+0x2be/0x4ce [zfs] Dec 12 06:26:23 Tower kernel: ? dmu_buf_hold_noread+0xa4/0xfd [zfs] Dec 12 06:26:23 Tower kernel: dmu_buf_hold+0x50/0x76 [zfs] Dec 12 06:26:23 Tower kernel: zap_lockdir+0x4e/0xab [zfs] Dec 12 06:26:23 Tower kernel: zap_cursor_retrieve+0x82/0x24d [zfs] Dec 12 06:26:23 Tower kernel: ? verify_dirent_name+0x22/0x2b Dec 12 06:26:23 Tower kernel: ? filldir64+0x8b/0x1a2 Dec 12 06:26:23 Tower kernel: zfs_readdir+0x274/0x3a0 [zfs] Dec 12 06:26:23 Tower kernel: ? __raw_callee_save___native_queued_spin_unlock+0x11/0x1e Dec 12 06:26:23 Tower kernel: ? do_filp_open+0x8a/0xb0 Dec 12 06:26:23 Tower kernel: ? __raw_spin_unlock+0x5/0x8 [zfs] Dec 12 06:26:23 Tower kernel: ? __down_read_common+0x84/0x2c2 Dec 12 06:26:23 Tower kernel: ? __fget_files+0x57/0x63 Dec 12 06:26:23 Tower kernel: zpl_iterate+0x46/0x64 [zfs] Dec 12 06:26:23 Tower kernel: iterate_dir+0x98/0x136 Dec 12 06:26:23 Tower kernel: __do_sys_getdents64+0x6b/0xd4 Dec 12 06:26:23 Tower kernel: ? filldir+0x1a3/0x1a3 Dec 12 06:26:23 Tower kernel: do_syscall_64+0x83/0xa5 Dec 12 06:26:23 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Dec 12 06:26:23 Tower kernel: RIP: 0033:0x48015b Dec 12 06:26:23 Tower kernel: Code: e8 6a 79 fe ff eb 88 cc cc cc cc cc cc cc cc e8 1b bf fe ff 48 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 Dec 12 06:26:23 Tower kernel: RSP: 002b:000000c0006b79c8 EFLAGS: 00000216 ORIG_RAX: 00000000000000d9 Dec 12 06:26:23 Tower kernel: RAX: ffffffffffffffda RBX: 000000c00005e000 RCX: 000000000048015b Dec 12 06:26:23 Tower kernel: RDX: 0000000000002000 RSI: 000000c0005fe000 RDI: 0000000000000008 Dec 12 06:26:23 Tower kernel: RBP: 000000c0006b7a18 R08: 000000c0009cf801 R09: 0000000000000000 Dec 12 06:26:23 Tower kernel: R10: 00007ffd2eb80080 R11: 0000000000000216 R12: 000000c0006b7908 Dec 12 06:26:23 Tower kernel: R13: 0000000000000000 R14: 000000c001580820 R15: 0000000000000000 Dec 12 06:26:23 Tower kernel: Modules linked in: xt_mark nvidia_modeset(PO) nvidia_uvm(PO) rpcsec_gss_krb5 xt_CHECKSUM ipt_REJECT nf_reject_ipv4 nfsv4 nfs ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap macvlan veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) nvidia(PO) drm backlight efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding edac_mce_amd wmi_bmof mxm_wmi kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd ahci rapl atlantic libahci ccp i2c_piix4 nvme corsair_cpro nvme_core i2c_core k10temp tpm_crb tpm_tis tpm_tis_core tpm wmi button acpi_cpufreq Dec 12 06:26:23 Tower kernel: ---[ end trace 175c948d9f3e665b ]--- Dec 12 06:26:24 Tower kernel: RIP: 0010:kmem_cache_alloc+0x9c/0x176 Dec 12 06:26:24 Tower kernel: Code: 48 89 04 24 74 05 48 85 c0 75 16 4c 89 f1 83 ca ff 89 ee 4c 89 e7 e8 17 ff ff ff 48 89 04 24 eb 26 41 8b 4c 24 28 49 8b 3c 24 <48> 8b 1c 08 48 8d 4a 01 65 48 0f c7 0f 0f 94 c0 84 c0 74 a9 41 8b Dec 12 06:26:24 Tower kernel: RSP: 0018:ffffc90045a83b90 EFLAGS: 00010202 Dec 12 06:26:24 Tower kernel: RAX: 454848a8154e84ad RBX: ffff8881242c1e00 RCX: 0000000000000018 Dec 12 06:26:24 Tower kernel: RDX: 0000000000069ad6 RSI: 0000000000042c00 RDI: 00006040c103eae0 Dec 12 06:26:24 Tower kernel: RBP: 0000000000042c00 R08: ffffe8ffff87eae0 R09: 0000000000000600 Dec 12 06:26:24 Tower kernel: R10: ffff88b498377e50 R11: ffff888121c40000 R12: ffff888186a3c400 Dec 12 06:26:24 Tower kernel: R13: ffff888186a3c400 R14: ffffffffa0060cbc R15: ffff88abae75cb00 Dec 12 06:26:24 Tower kernel: FS: 0000151080106f20(0000) GS:ffff88bf3e840000(0000) knlGS:0000000000000000 Dec 12 06:26:24 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 12 06:26:24 Tower kernel: CR2: 00000078000fdf50 CR3: 00000035541d8000 CR4: 0000000000350ee0
  7. Ok, that approach got me a lot closer. I had to add "no_squash_root" to the exports on the nas so that docker containers can mkdir
  8. i added a script in user scripts to get it to mount on boot. now the issue is that I cant write to the share. server 192.168.1.3: theskaz@nas:/mnt/tank$ ls -l total 59 drwxrwxrwx 4 nobody users 4 Oct 1 18:47 chia drwxrwxrwx 8 nobody users 8 Oct 5 21:02 media drwxrwxrwx 5 nobody users 6 Nov 18 21:22 netshare drwxrwxrwx 2 nobody users 2 Nov 12 19:49 UnfiVideoShareForStorage drwxrwxrwx 3 nobody users 4 Nov 18 23:31 vms theskaz@nas:/mnt/tank$ unraid 192.168.1.39: root@Tower:/tank# ls -l total 17 drwxrwxrwx 2 nobody users 2 Nov 12 12:49 UnfiVideoShareForStorage/ drwxr-xr-x 2 root root 2 Sep 30 12:55 chia/ drwxrwxrwx 8 nobody users 8 Oct 5 15:02 media/ drwxr-xr-x 2 root root 2 Sep 30 12:55 netshare/ drwxr-xr-x 2 root root 2 Sep 30 12:55 vms/ exports: /mnt/tank 192.168.1.39(rw,sync,no_subtree_check) /mnt/datastore 192.168.1.39(rw,sync,no_subtree_check) mount command: mount -o nolock -t nfs 192.168.1.3:/mnt/tank /tank mount -o nolock -t nfs 192.168.1.3:/mnt/datastore /datastore nobody has been mapped to 99 on nas, and users mapped to 100
  9. so, after 1 year or more of messing with Unraid/Zfs and a DAS enc. I decided to move the large storage area to another server (Dell R420) and share it out to Unraid. my question is with NFS, I am trying to figure out if I got everything correct: Server: theskaz@nas:/mnt/datastore$ sudo exportfs -v /mnt/tank 192.168.1.39(rw,wdelay,root_squash,no_subtree_check,sec=sys,rw,secure,root_squash,no_all_squash) /mnt/datastore 192.168.1.39(rw,wdelay,root_squash,no_subtree_check,sec=sys,rw,secure,root_squash,no_all_squash) Unraid: /dev/sdb1 /boot vfat rw,flush,noatime,nodiratime,dmask=77,fmask=177,shortname=mixed /boot/bzmodules /lib/modules squashfs ro,defaults /boot/bzfirmware /lib/firmware squashfs ro,defaults tmpfs /dev/shm tmpfs defaults hugetlbfs /hugetlbfs hugetlbfs defaults 192.168.1.3:/mnt/tank /tank nfs auto,noatime,nolock,tcp,actimeo=1800 0 0 192.168.1.3:/mnt/datastore /datastore nfs auto,noatime,nolock,tcp,actimeo=1800 0 0 I mirrored what the file structure was when the zfs pools were local. Does this look right?: root@Tower:/datastore# ls -latr total 312064341 drwxrwxrwx 5 65534 65534 5 Oct 2 10:18 influxdb/ -rwxrwxrwx 1 65534 65534 805306368000 Oct 12 11:04 sql_data.img* drwxrwxrwx 6 65534 65534 7 Oct 15 07:12 mariadb/ drwxrwxrwx 4 65534 65534 6 Oct 26 13:10 ./ -rwxrwxrwx 1 65534 65534 322122547200 Dec 5 21:35 plotter_temp.img* drwxr-xr-x 23 root root 500 Dec 8 12:03 ../ the 65534 part looks odd to me.
  10. I need to add the kASAN config to the 5.13 kernel. I dont need to make any other changes. How can I accomplish this without effing up everything? this is to debug ZFS on my machine in its natural habitat.
  11. plex does seem to work just fine. I just realized that I have OC settings in the miner. didnt remember that I did that. im going to do some more testing with no OC'ing and see if its still an issue, if so, then Ill reach out. Thank you for your help @ich777!
  12. did you go into plex and set it to hardware transcoding?
  13. after some testing, I think its the Phoenix Miner docker. no matter what config I use, whether its 1, 2, or 3 GPUs they will eventually crash. If I dont run the docker zfs crashes the system, but will not do it near as often.
  14. I did that and was getting kernel panics from ZFS hourly... had to downgrade
  15. I just assigned plex to the 3rd GPU (Titan) and ill give that a shot right now.
  16. they are watercooled and dont go north of 52-4c. I ran plex, no transcode, no nothing. i navigated to a show I wanted to watch, and then it crashed. Plex is tied to the 2080 Ti. the server is still going strong... without any of the nvidia based dockers running. normally it would have crashed by now. if its a memory map issue, could it be due to a memory size difference between the first and 2nd card? the fact that I have 3 cards? the fact that plex is pointing to the smaller one? assuming that the thermals arent an issue, should this be able to run multiple docker containers pointing to the same GPU?
  17. I think Im having an issue with the Nvidia Plugin: Sep 30 07:10:08 Tower kernel: BUG: kernel NULL pointer dereference, address: 00000000000000b1 Sep 30 07:10:08 Tower kernel: #PF: supervisor read access in kernel mode Sep 30 07:10:08 Tower kernel: #PF: error_code(0x0000) - not-present page Sep 30 07:10:08 Tower kernel: PGD 2d5955067 P4D 2d5955067 PUD 2aded0067 PMD 0 Sep 30 07:10:08 Tower kernel: Oops: 0000 [#1] SMP NOPTI Sep 30 07:10:08 Tower kernel: CPU: 72 PID: 106336 Comm: nvidia-smi Tainted: P O 5.10.28-Unraid #1 Sep 30 07:10:08 Tower kernel: Hardware name: ASUS System Product Name/ROG ZENITH II EXTREME ALPHA, BIOS 1402 01/15/2021 Sep 30 07:10:08 Tower kernel: RIP: 0010:_nv031699rm+0x79/0x940 [nvidia] Sep 30 07:10:08 Tower kernel: Code: 07 00 00 41 bf 01 00 00 00 4c 8d 65 48 31 db 44 89 7d 10 66 0f 1f 44 00 00 41 f6 c5 01 0f 84 90 00 00 00 49 8b 86 30 1a 00 00 <80> b8 b1 00 00 00 00 74 12 b8 01 00 00 00 89 d9 d3 e0 41 85 86 94 Sep 30 07:10:08 Tower kernel: RSP: 0018:ffffc9000303b978 EFLAGS: 00010202 Sep 30 07:10:08 Tower kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000002 Sep 30 07:10:08 Tower kernel: RDX: ffff88824b6f0008 RSI: ffff88817b692008 RDI: ffff888198f88008 Sep 30 07:10:08 Tower kernel: RBP: ffff8884806ddd80 R08: 0000000000000002 R09: 0000000000000020 Sep 30 07:10:08 Tower kernel: R10: 0000000000000002 R11: 0000000000000002 R12: ffff8884806dddc8 Sep 30 07:10:08 Tower kernel: R13: 0000000000000003 R14: ffff88817b692008 R15: 0000000000000001 Sep 30 07:10:08 Tower kernel: FS: 0000152f94ef2b80(0000) GS:ffff88bf3e000000(0000) knlGS:0000000000000000 Sep 30 07:10:08 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 30 07:10:08 Tower kernel: CR2: 00000000000000b1 CR3: 000000048e7d4000 CR4: 0000000000350ee0 Sep 30 07:10:08 Tower kernel: Call Trace: Sep 30 07:10:08 Tower kernel: ? _nv031813rm+0x82/0x270 [nvidia] Sep 30 07:10:08 Tower kernel: ? _nv031846rm+0x17/0x30 [nvidia] Sep 30 07:10:08 Tower kernel: ? _nv022821rm+0xc0/0x1b0 [nvidia] Sep 30 07:10:08 Tower kernel: ? _nv022826rm+0x11b/0x230 [nvidia] Sep 30 07:10:08 Tower kernel: ? _nv022826rm+0x211/0x230 [nvidia] Sep 30 07:10:08 Tower kernel: ? _nv022828rm+0x310/0x310 [nvidia] Sep 30 07:10:08 Tower kernel: ? _nv023498rm+0x32d/0x470 [nvidia] Sep 30 07:10:08 Tower kernel: ? _nv023498rm+0x304/0x470 [nvidia] Sep 30 07:10:08 Tower kernel: ? _nv000722rm+0x32a/0x680 [nvidia] Sep 30 07:10:08 Tower kernel: ? _nv000715rm+0x1802/0x23d0 [nvidia] Sep 30 07:10:08 Tower kernel: ? rm_init_adapter+0xc5/0xe0 [nvidia] Sep 30 07:10:08 Tower kernel: ? ttwu_queue_wakelist+0x93/0x9a Sep 30 07:10:08 Tower kernel: ? nv_open_device+0x44b/0x676 [nvidia] Sep 30 07:10:08 Tower kernel: ? nvidia_open+0x266/0x3d1 [nvidia] Sep 30 07:10:08 Tower kernel: ? nvidia_frontend_open+0x62/0x8d [nvidia] Sep 30 07:10:08 Tower kernel: ? chrdev_open+0x150/0x187 Sep 30 07:10:08 Tower kernel: ? cdev_put+0x19/0x19 Sep 30 07:10:08 Tower kernel: ? do_dentry_open+0x184/0x289 Sep 30 07:10:08 Tower kernel: ? path_openat+0x85e/0x937 Sep 30 07:10:08 Tower kernel: ? filename_lookup+0xb8/0xdf Sep 30 07:10:08 Tower kernel: ? do_filp_open+0x4c/0xa9 Sep 30 07:10:08 Tower kernel: ? _cond_resched+0x1b/0x1e Sep 30 07:10:08 Tower kernel: ? getname_flags+0x24/0x146 Sep 30 07:10:08 Tower kernel: ? kmem_cache_alloc+0x108/0x130 Sep 30 07:10:08 Tower kernel: ? do_sys_openat2+0x6f/0xec Sep 30 07:10:08 Tower kernel: ? do_sys_open+0x35/0x4f Sep 30 07:10:08 Tower kernel: ? do_syscall_64+0x5d/0x6a Sep 30 07:10:08 Tower kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Sep 30 07:10:08 Tower kernel: Modules linked in: xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) nvidia_drm(PO) nvidia_modeset(PO) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvidia(PO) drm backlight agpgart ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding edac_mce_amd amd_energy wmi_bmof mxm_wmi kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper mpt3sas atlantic nvme ahci i2c_piix4 raid_class rapl i2c_core scsi_transport_sas input_leds ccp nvme_core libahci led_class k10temp wmi button acpi_cpufreq Sep 30 07:10:08 Tower kernel: CR2: 00000000000000b1 Sep 30 07:10:08 Tower kernel: ---[ end trace d232d3a5b0583cf9 ]--- Sep 30 07:10:08 Tower kernel: RIP: 0010:_nv031699rm+0x79/0x940 [nvidia] Sep 30 07:10:08 Tower kernel: Code: 07 00 00 41 bf 01 00 00 00 4c 8d 65 48 31 db 44 89 7d 10 66 0f 1f 44 00 00 41 f6 c5 01 0f 84 90 00 00 00 49 8b 86 30 1a 00 00 <80> b8 b1 00 00 00 00 74 12 b8 01 00 00 00 89 d9 d3 e0 41 85 86 94 Sep 30 07:10:08 Tower kernel: RSP: 0018:ffffc9000303b978 EFLAGS: 00010202 Sep 30 07:10:08 Tower kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000002 Sep 30 07:10:08 Tower kernel: RDX: ffff88824b6f0008 RSI: ffff88817b692008 RDI: ffff888198f88008 Sep 30 07:10:08 Tower kernel: RBP: ffff8884806ddd80 R08: 0000000000000002 R09: 0000000000000020 Sep 30 07:10:08 Tower kernel: R10: 0000000000000002 R11: 0000000000000002 R12: ffff8884806dddc8 Sep 30 07:10:08 Tower kernel: R13: 0000000000000003 R14: ffff88817b692008 R15: 0000000000000001 Sep 30 07:10:08 Tower kernel: FS: 0000152f94ef2b80(0000) GS:ffff88bf3e000000(0000) knlGS:0000000000000000 Sep 30 07:10:08 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 30 07:10:08 Tower kernel: CR2: 00000000000000b1 CR3: 000000048e7d4000 CR4: 0000000000350ee0 this happens at random times. I have 3 GPUs 2x RTX Titans and 1x 2080Ti: I have 3 Docker Containers that utilize the GPUs. PhoenixMiner (uses all 3), Plex (2080Ti), Deepstack(Dual Titans). I thought maybe they couldnt all run together, so I stopped the others and just ran plex. system still crashed. right now they are all off, and Its still running, but time will tell.. Ill leave an update if it crashes again. syslog.zip tower-diagnostics-20211009-0736.zip
  18. Attached is my updated one, using the 1.8.4 Influx. You were right, my non_negative_derivatives were set at 1s instead of 1ms. ZFS-1.8.json
  19. the Arc Demand is throwing me off. I can get the Data Hit Ratio, I think. but the pivot that you have going on, I have no clue.
  20. from(bucket: v.bucket) |> range(start: v.timeRangeStart, stop: v.timeRangeStop) |> filter(fn: (r) => r[\"_measurement\"] == \"zfs\") |> filter(fn: (r) => r[\"pools\"] == \"hddmain::ssdnvme::ssdsata\") |> filter(fn: (r) => r[\"_field\"] == \"arcstats_size\" or r[\"_field\"] == \"arcstats_data_size\" or r[\"_field\"] == \"arcstats_metadata_size\" or r[\"_field\"] == \"arcstats_mfu_size\" or r[\"_field\"] == \"arcstats_dnode_size\" or r[\"_field\"] == \"arcstats_mru_size\") |> aggregateWindow(every: v.windowPeriod, fn: mean) |> map(fn: (r) => ({ _value: r._value, _time:r._time, _field : r._field}))", Arc Size, converted to this so far: SELECT mean("arcstats_size") as Size, mean("arcstats_data_size") as Data, mean("arcstats_metadata_size") as Metadata, mean("arcstats_mfu_size") as MFU, mean("arcstats_dnode_size") as DNODE, mean("arcstats_mru_size") as MRU FROM "zfs" WHERE $timeFilter GROUP BY time($__interval) fill(none)
  21. took your sample and edited it for the other graphs. currently working on ARC size and demand
  22. thank you. quick question, fr the influxdb queries, mine show "select measurement" on all of them, so I assume that I dont have the corresponding metrics in the db? my telegraf.conf has zfs enabled with pool and dataset metrics set to true.
  23. @Iker would you be able to share the json for your dashboard as a starting point? I have everything else working.