Isn't that RAM usage normal? ZFS will use all available memory. My Intel machine uses all 16GB.
So, the devs are still investigating, but have no leads right now. So l will continue to search for symptoms and potential causes.
1) I have strong reason to believe that is it is memory (ram) related. ( My system seems to die when I use all my ram)(memory leak bug is not helping, should be patched in the next update)
2) Power management or motherboard power saving could also be related. ( Cool'n'Quiet and power optimiztions)
I have three primary questions?
1) Is everyone running ECC ram in a compatible motherboard?
2) Is anyone getting crashes running non-ECC ram?
3 What motherboard are you using? -- (mine- ASRock AB350 PRO4)
Have a great week!-- Cheers
I read through the mailing list linked in the blog post and saw a mention of disabling SMT in the BIOS. I tried that today and what consistently would lock my machine (replication to an external) succeeded. I am going to see how long it can stay up, but this may be a temporary solution!Seems Ryzen still has issues with FreeBSD https://www.phoronix.com/scan.php?page=news_item&px=Ryzen-BSD-Lock-Ups-2018
May want to start sending issues upstream to the FreeBSD forums if you are still having issues as they will be the ones to implement the fixes.
iozone -M -e -+u -T -t 12 -r 128k -s 50G -i 0 -i 1 -i 2 -i 8 -+p 70 -C
I am currently in another testing phase ( only 2 days), but currently treating it as a HW/power management or Memory related issue. I have disabled C6 state, DIMM power down, cool and quiet, and another power saving feature. I have also disabled DF error freeze ( I have no idea about this one).
Ezra I think your issue is something completely different, most AMD systems running freenas are stable for days not hours.
I think I might be suffering from your same situation but have yet to solve the issue. However I do not think it was a RAM issue in the end. Here is my current status in trying to solve the consistent crashing:
[HW]
Mobo: asrock x370 taichi
RAM: corsair ECC 2x16GB
CPU: tried both 1500 and 1500X
[BIOS]
* Everything except SMT has been disabled (cool nquiet, c6, kvm)
[OS]
0) Crashed consistently within 24hours on Freenas11.1
https://forums.freenas.org/index.php?threads/freenas-11-crash-during-write.59578/#post-424111
1) Ran prime95 for ~12 hours from a USB stick, no stability problems
2) Changed to freebsd - would run a long iozone read/write test: would crash each time on freebsd: the following iozone command was used
Code:iozone -M -e -+u -T -t 12 -r 128k -s 50G -i 0 -i 1 -i 2 -i 8 -+p 70 -C
3) Changed to debian kernel 9.4 and 9.13 - Would no longer crash on when running iozone, but would still crash within a day after installing zfs-on-linux, docker, plex, handbrake (I have no idea if any of these caused the crash but I remember when I first booted up OS it was OK for the first 24 hours before I installed docker/plex although I doubt that would be an issue.
This would still crash even though memory usage was very very low
4) currently trying debian 9.14 without anything loaded to see how long it stays alive
I am strongly considering scraping this and returning the MOBO/CPU and starting fresh. Have a few more days to decide.
Disabling SMT is no longer crashing, even with cool 'n quiet, c6 enabled (which would crash right away in 11.1-U1 for me)
Disabling SMT also seems to have fixed the immediate crashing (within 24hours) on the debian version. In that instance it was a combination of docker being installed and SMT. In other words, if I installed docker then I had to disable SMT.
Do you think this is specific to the X370 taichi boards or something where need to be patient and wait for a fix on the OS side?
It's not the motherboards, it is happening on a wide variety of motherboards, as well as threadripper, non& ecc boards. Disabling SMT just increases the time between crashes, the same as with disabling cool and quiet. We need more debug info, but it is pretty hard to come by with the computer's freezing. I am currently testing a new setup. Back on 11.0u4 I was able to go 20 days without crashing so, I will only report once I get to 25. We should have a new patch 11.1 U2 in 30ish days. --
It could be months before the problem is found. -- Unless you can monitor it and be a guinea pig go for a stable build. AMD thread/cpu count is very nice, but FreeBSD is not liking Zen right now.Thanks for your response. Do you think its worth keep these mobo/cpu builds under the assumption that eventually it will be stable??? or is that unlikely and I should strongly consider returning them.
Its interesting to me that running docker specifically was causing crashing on a Debian build; I have no idea if that helps diagnose these problems although that is a completely different OS.