Andrea3000

I’m on 6.10.3 and * * * * * only works after I disable and then re-enable the schedules. I don’t remember having had this issue when I was on 6.9.x

My array is already set to autostart and it does. After some more digging I found out that: - All the custom schedules weren't working, not just the one that was supposed to run every minute - The issue was due to the syntax of the cron string and I managed to fix it and it is now working. I had to replace: - * * * * * with */1 * * * * - 0 * * * * with 0 */1 * * * - 0 0 1 * * with 0 0 1 */1 * I don't know why the old strings did't work as they should be equally valid..

Hi @Squid I think I have encountered a bug with User Scripts. I use the scheduling/Cron feature on 3 of my scripts. - One is set to execute "At first array start only" (and works correctly) - One is set to execute every hour using a custom Cron string "0 * * * *" (and works correctly) - One si set to execute every minute using a custom Cron string "* * * * *" (THIS DOESN'T WORK) The script that is set to execute every minute works the first time I set it up but after a reboot it doesn't get executed. In order for it to work I have to temporarily disable the scheduling, put it back to custom and apply the changes. This works until the following reboot. Would you be able to help me with this? Thanks Andrea

Actually, I was checking the in-tree Intel drivers that are included in the Linux kernel 5.15.46 and the logic to export the die temperature via hwmon is already there: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/net/ethernet/intel/ixgbe/ixgbe_sysfs.c?h=v5.15.46 I can see that it is enabled at compile time via the CONFIG_IXGBE_HWMON parameter (whose default value is TRUE) #ifdef CONFIG_IXGBE_HWMON if (ixgbe_sysfs_init(adapter)) e_err(probe, "failed to allocate sysfs resources\n"); #endif /* CONFIG_IXGBE_HWMON */ Is it kept at its default value when the unraid kernel is compiled or it is disabled? @limetech do you have any suggestion on how to debug the fact that I can't access the temperature sensor of my Intel X550 card? Thanks Andrea

Sorry, I'm back with another ZFS related question. I'm trying to access the ZFS snapshots via Samba on MacOS. I know that for Windows I can use the shadow_copy2 vfs object to make the snapshots appears as shadow copies. But what about MacOS? I found online that this can be done in TrueNAS via the zfsacl vfs object: https://www.truenas.com/community/threads/how-to-access-zfs-snapshots-over-smb.69449/ but this doesn't appear to be available in unRAID. Is there a workaround?

Thanks @jortan. Most of my use cases involve only asynchronous writes. In addition, I have an Intel Optane P1600x that I’m using as slog device to handle synchronous writes (It has power loss protection). Therefore, I’m more inclined to still allow synchronous write, my priority is not to lose any data.

Thank you. I experimented a bit with a NVME special vdev and while the performance have increased slightly, it isn't worth the effort (and risk) for me. I got the SATA cables that I was expecting and I put all 8 disks online in a raidz2 pool. With 1M recordsize I can saturate the 10gbe bandwidth with sequential reads or writes. For random read/writes I'm around 180-200MB/s with 1M recordsize. I'm pretty happy with that and I'll probably stick with raidz2 for extra peace of mind. Thank you all for all the valuable advices, much appreciated.

Sorry @gyto6 for the very late reply, it took me much longer than expected to source the components to build the server. I've now created a zfs dataset, and created few snapshots using: zfs snapshot -r myPool/myDataset@now I can see the snapshot being created with "zfs list -t snapshot" NAME USED AVAIL REFER MOUNTPOINT myPool/myDataset@now 1.28M - 1.32M - I've also created an SMB share that points to myDataset and I can access it via MacOS without issues. I went through both of the guides that you linked in the posts above but I can't find a way to make the snapshots accessible to MacOS via SMB. Am I missing something? To be more specific, if on the server I browse to: /myPool/myDataset/.zfs/snapshot I can see the snapshot named "now" that I have created: /myPool/myDataset/.zfs/snapshot# ls -a ./ ../ now/ From MacOS, if I browse to the share "myDataset" and then to the snapshot directory, I don't see any snapshot: ****@192 snapshot % pwd /Volumes/myDataset/.zfs/snapshot ****@192 snapshot % ls -a . ..

Thanks @jortan. While you replied, I was about to edit my original post to add the output of "zpool iostat" for the two zpool layouts. 3-wide striped array (no parity): capacity operations bandwidth pool alloc free read write read write ---------- ----- ----- ----- ----- ----- ----- zfs 21.9G 10.9T 0 727 0 728M zfs 21.9G 10.9T 0 722 0 722M zfs 21.9G 10.9T 0 733 0 648M zfs 24.6G 10.9T 0 1.05K 0 693M zfs 24.6G 10.9T 0 715 0 716M zfs 24.6G 10.9T 0 753 0 738M zfs 27.2G 10.8T 0 1.03K 0 647M zfs 27.2G 10.8T 0 734 0 734M zfs 27.2G 10.8T 0 722 0 723M zfs 27.2G 10.8T 0 735 0 719M zfs 29.9G 10.8T 0 1.05K 0 630M zfs 29.9G 10.8T 0 724 0 725M zfs 29.9G 10.8T 0 728 0 728M zfs 29.9G 10.8T 0 736 0 737M zfs 32.5G 10.8T 0 1.06K 0 655M zfs 32.5G 10.8T 0 742 0 743M zfs 32.5G 10.8T 0 739 0 740M zfs 32.5G 10.8T 0 734 0 735M zfs 35.1G 10.8T 0 1014 0 612M zfs 35.1G 10.8T 0 727 0 727M zfs 35.1G 10.8T 0 727 0 728M zfs 35.1G 10.8T 0 743 0 728M zfs 37.8G 10.8T 0 925 0 588M zfs 37.8G 10.8T 0 705 0 706M zfs 37.8G 10.8T 0 709 0 709M zfs 37.8G 10.8T 0 713 0 714M zfs 40.5G 10.8T 0 1.04K 0 657M zfs 40.5G 10.8T 0 742 0 743M zfs 40.5G 10.8T 0 730 0 716M zfs 40.5G 10.8T 0 724 0 643M zfs 43.1G 10.8T 0 978 0 685M zfs 43.1G 10.8T 0 719 0 720M zfs 43.1G 10.8T 0 721 0 722M 4-wide raidz1 array: capacity operations bandwidth pool alloc free read write read write ---------- ----- ----- ----- ----- ----- ----- zfs 96.3G 14.5T 8 6.36K 120K 544M zfs 96.3G 14.5T 9 4.95K 124K 421M zfs 96.2G 14.5T 8 5.44K 120K 546M zfs 96.2G 14.5T 8 6.34K 120K 516M zfs 96.2G 14.5T 8 6.53K 120K 568M zfs 96.2G 14.5T 8 5.46K 120K 566M zfs 96.2G 14.5T 8 5.94K 120K 583M zfs 96.2G 14.5T 10 5.94K 148K 539M zfs 96.2G 14.5T 9 5.44K 132K 528M zfs 96.3G 14.5T 8 4.34K 120K 375M zfs 96.3G 14.5T 5 6.08K 79.9K 525M zfs 96.3G 14.5T 8 6.33K 120K 598M zfs 96.3G 14.5T 8 5.98K 120K 565M zfs 96.3G 14.5T 8 5.82K 120K 578M zfs 96.3G 14.5T 11 5.75K 160K 550M zfs 96.3G 14.5T 8 5.97K 120K 557M zfs 96.3G 14.5T 8 6.00K 120K 566M zfs 96.3G 14.5T 10 3.98K 128K 285M zfs 96.3G 14.5T 5 4.55K 79.9K 561M zfs 96.3G 14.5T 8 5.79K 120K 506M zfs 96.3G 14.5T 8 6.23K 120K 495M zfs 96.3G 14.5T 8 6.21K 120K 522M zfs 96.3G 14.5T 5 5.96K 79.9K 577M Before reading your reply I thought that the reason for the lower performance were the reads that are interleaved in between the writes. I know very little about zfs but I wasn't expecting a write operation to require reads. Does this have something to do with the ZIL?

I've done some more benchmarking and, if anything, I'm more puzzled than before.. I created 4 zpools (one at a time), each with just a single drive. I run a sequential write test with fio and I get 250MB/s from each drive, as expected from the manufacturer specifications. I then created a striped zpool with no parity (equivalent of RAID0) using 3 drives, re-run the sequential write test and I obtained this: fio --direct=1 --name=test --bs=128k --filename=/zfs/test/whatever.tmp --size=64G --iodepth=64 --readwrite=write test: (g=0): rw=write, bs=(R) 128KiB-128KiB, (W) 128KiB-128KiB, (T) 128KiB-128KiB, ioengine=psync, iodepth=64 fio-3.23 Starting 1 process test: Laying out IO file (1 file / 65536MiB) Jobs: 1 (f=1): [W(1)][100.0%][w=709MiB/s][w=5670 IOPS][eta 00m:00s] test: (groupid=0, jobs=1): err= 0: pid=28574: Thu Jun 2 09:48:20 2022 write: IOPS=5745, BW=718MiB/s (753MB/s)(64.0GiB/91257msec); 0 zone resets clat (usec): min=10, max=25115, avg=168.47, stdev=97.66 lat (usec): min=11, max=25118, avg=171.59, stdev=98.28 clat percentiles (usec): | 1.00th=[ 13], 5.00th=[ 60], 10.00th=[ 111], 20.00th=[ 141], | 30.00th=[ 157], 40.00th=[ 165], 50.00th=[ 169], 60.00th=[ 174], | 70.00th=[ 178], 80.00th=[ 188], 90.00th=[ 206], 95.00th=[ 245], | 99.00th=[ 453], 99.50th=[ 562], 99.90th=[ 799], 99.95th=[ 963], | 99.99th=[ 2008] bw ( KiB/s): min=564736, max=5577216, per=100.00%, avg=736542.42, stdev=364660.92, samples=182 iops : min= 4412, max=43572, avg=5754.23, stdev=2848.91, samples=182 lat (usec) : 20=3.44%, 50=0.57%, 100=5.08%, 250=86.32%, 500=3.88% lat (usec) : 750=0.58%, 1000=0.09% lat (msec) : 2=0.03%, 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01% cpu : usr=4.56%, sys=30.31%, ctx=506955, majf=0, minf=10 IO depths : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0% submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% issued rwts: total=0,524288,0,0 short=0,0,0,0 dropped=0,0,0,0 latency : target=0, window=0, percentile=100.00%, depth=64 Run status group 0 (all jobs): WRITE: bw=718MiB/s (753MB/s), 718MiB/s-718MiB/s (753MB/s-753MB/s), io=64.0GiB (68.7GB), run=91257-91257msec Up until this point, everything makes sense. I get 750MB/s which is the sum of the 3 drives. I then decided to create a 4 disks wide raidz1 pool. This should give me the same sequential write performance of the 3-wide striped pool. Instead, this is what I get: fio --direct=1 --name=test --bs=128k --filename=/zfs/test/whatever.tmp --size=64G --iodepth=64 --readwrite=write --idle-prof=percpu test: (g=0): rw=write, bs=(R) 128KiB-128KiB, (W) 128KiB-128KiB, (T) 128KiB-128KiB, ioengine=psync, iodepth=64 fio-3.23 Starting 1 process Jobs: 1 (f=1): [W(1)][100.0%][w=378MiB/s][w=3027 IOPS][eta 00m:00s] test: (groupid=0, jobs=1): err= 0: pid=12882: Thu Jun 2 10:19:12 2022 write: IOPS=3322, BW=415MiB/s (436MB/s)(64.0GiB/157791msec); 0 zone resets clat (usec): min=11, max=101426, avg=299.37, stdev=168.44 lat (usec): min=12, max=101426, avg=300.34, stdev=168.46 clat percentiles (usec): | 1.00th=[ 13], 5.00th=[ 174], 10.00th=[ 258], 20.00th=[ 285], | 30.00th=[ 297], 40.00th=[ 302], 50.00th=[ 310], 60.00th=[ 314], | 70.00th=[ 318], 80.00th=[ 330], 90.00th=[ 355], 95.00th=[ 371], | 99.00th=[ 420], 99.50th=[ 537], 99.90th=[ 922], 99.95th=[ 1123], | 99.99th=[ 1893] bw ( KiB/s): min=266752, max=5665536, per=100.00%, avg=425720.69, stdev=299525.60, samples=315 iops : min= 2084, max=44262, avg=3325.94, stdev=2340.04, samples=315 lat (usec) : 20=3.80%, 50=0.17%, 100=0.08%, 250=5.44%, 500=89.95% lat (usec) : 750=0.38%, 1000=0.11% lat (msec) : 2=0.07%, 4=0.01%, 10=0.01%, 20=0.01%, 250=0.01% cpu : usr=0.77%, sys=5.58%, ctx=505109, majf=0, minf=11 IO depths : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0% submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% issued rwts: total=0,524288,0,0 short=0,0,0,0 dropped=0,0,0,0 latency : target=0, window=0, percentile=100.00%, depth=64 Run status group 0 (all jobs): WRITE: bw=415MiB/s (436MB/s), 415MiB/s-415MiB/s (436MB/s-436MB/s), io=64.0GiB (68.7GB), run=157791-157791msec CPU idleness: system: 95.21% percpu: 92.62%, 96.21%, 95.96%, 96.08% unit work: mean=26.64us, stddev=0.53 Instead, I only get 436MB/s. As you can see, I added the "--idle-prof=percpu" option to report the CPU idleness which shows values well above 90%. From this I concluded that I'm not bottlenecked by the CPU for the parity calculation. But if this is true, why are the performance so much worse considering that the number of "data" drives are the same between the 4-wide raidz1 and 3-wide striped pool? How can I determine what the bottleneck is?

I’m going for a 10GB SLOG based on the fact that I will connect to the server via 10gbe, which means that in 5 seconds I can send up to 5GB. I’m doubling that to have some additional margin. The P1600X has power loss protection, therefore I should be able to recover everything that wasn’t yet committed to disk in case of power failure.

Thank you very much @Marshalleq for all the informations. Is there a particular reason why you chose zstd compression instead of lz4? Is it because you have a powerful enough CPU that compensates the slower compression/decompression? As part of the “performance” tuning I’m expecting today the delivery of an Intel Optane P1600X 118GB NVMe that I plan to partition with a 10GB partition to use as SLOG and a 108GB partition to use as L2ARC. But I will wait before installing it to make sure that first I’m happy with the performance of the zpool as it is and to find optimal settings for my use case. Thanks Andrea

Ok, I have benchmarked the drives individually using the DiskSpeed docker and each drive performs more or less the same with roughly 250MB/s read at the outer diameter and 140-150MB/s at the inner diameter. Maybe my expectations were too high for a random read/write benchmark, I set my expectations based on this post/guide from the Level1Techs forum: https://forum.level1techs.com/t/zfs-on-unraid-lets-do-it-bonus-shadowcopy-setup-guide-project/148764 that shows results of 150-160MB/s for randrw with 4x 5400RPM drives in raidz1, with average IOPS just short of 700...which is huge compared to what I get. Based on what @Iker said, and the disk review posted, the results obtained in the Levels1Techs forum are unrealistically too high for 4x HDD?!? The other day, before I posted my benchmark, I tried also a sequential read and write and the performance was still very poor, less than 100MB/s, which is what made me conclude that something wasn't right. I have repeated the benchmark yesterday and I now get performance between 280-320MB/s for sequential read/write in raidz2. I was hoping to be more in the 400-500MB/s range but it still respectable. @BVD I've done a bit of research and I'm pretty much sold on zfs. The features that attract me the most are: snapshots, data integrity, bit rot protection and decent performance. For what concerns the tuning, I think I need to study a bit because I wouldn't know where to start. I know what kind of data I will be storing therefore I can at least choose the blocksize, but I wouldn't know what else can be tuned. Are there some guidelines/tutorials on how to tune the zfs pool to maximise performance? Or at least to know what I should expect from a zpool of 8x WD Red Pro Nas drives in raidz2?

Thank you @Marshalleq and @BVD for your replies. The only reason why I choose raidz2 with only 4 drives is because I know that I will be running raidz2 with 8 drives and I wanted to test a similar parity layout, while waiting for the sata cables to arrive. I agree that it doesn’t make any sense. The RAM is mostly free, there were around 60GB free when I run the fio test. As for the CPU, I assumed that an i3 with turbo would have been sufficient to compute parity (with compression off for this test). I can see one core at 100% during the test, the others around 20%. Could the CPU be the bottleneck? Last night I started testing the drives individually using the DiskSpeed docker. I tested the first which gave me 250MB/s at the outer diameter and 150MB/s at the inner diameter. I will test the others and report back. Thanks Andrea

Hi, I have an Intel X550-T2 PCIE card and I'm trying to acces the onboard temperature sensor. I can see from the ixgbe driver that this is supported: https://github.com/majek/ixgbe/blob/master/src/ixgbe_sysfs.c /** * ixgbe_add_hwmon_attr - Create hwmon attr table for a hwmon sysfs file. * @adapter: pointer to the adapter structure * @offset: offset in the eeprom sensor data table * @type: type of sensor data to display * * For each file we want in hwmon's sysfs interface we need a device_attribute * This is included in our hwmon_attr struct that contains the references to * the data structures we need to get the data to display. */ static int ixgbe_add_hwmon_attr(struct ixgbe_adapter *adapter, unsigned int offset, int type) { ... ... However, I've read in this post that the ixgbe drivers aren't included in 6.10 because they were causing problems. Instead, only the in-tree driver is included. @limetech what are the chances that I can access the temperature sensors with the in-tree driver? If I run sensors-detect I don't find any hwmon that is related to the network card. Is there a way for me to test the ixgbe driver on unraid 6.10? Thanks Andrea

Hi, I just set up an unraid server with zfs and I run some benchmarks. The performance of the array are significantly lower than what I was expecting. Eventually the array will be of 8 drives in raidz2 but at the moment I'm waiting for 4 more SATA cables to be delivered, therefore at the moment my system is as follows: Gigabyte C246M-WU4 Intel Core i3-9100 Kingston 64GB 2666Mhz ECC RAM 4x WD Red Pro NAS 4TB 7200RPM The ZFS array is of 4 drives in raidz2. I just run some benchmarks with fio and this is what I get: fio --direct=1 --name=test --bs=256k --filename=/zfs/zfs/test/whatever.tmp --thread --size=64G --iodepth=64 --readwrite=randrw test: (g=0): rw=randrw, bs=(R) 256KiB-256KiB, (W) 256KiB-256KiB, (T) 256KiB-256KiB, ioengine=psync, iodepth=64 fio-3.23 Starting 1 thread test: Laying out IO file (1 file / 65536MiB) Jobs: 1 (f=1): [m(1)][100.0%][r=44.5MiB/s,w=47.5MiB/s][r=177,w=189 IOPS][eta 00m:00s] test: (groupid=0, jobs=1): err= 0: pid=2196: Sun May 29 11:44:57 2022 read: IOPS=225, BW=56.4MiB/s (59.1MB/s)(31.0GiB/580821msec) clat (usec): min=25, max=765897, avg=4299.50, stdev=18500.73 lat (usec): min=25, max=765897, avg=4299.87, stdev=18500.73 clat percentiles (usec): | 1.00th=[ 41], 5.00th=[ 71], 10.00th=[ 126], 20.00th=[ 129], | 30.00th=[ 133], 40.00th=[ 139], 50.00th=[ 147], 60.00th=[ 159], | 70.00th=[ 6390], 80.00th=[ 9503], 90.00th=[ 11207], 95.00th=[ 12649], | 99.00th=[ 26084], 99.50th=[ 39584], 99.90th=[299893], 99.95th=[530580], | 99.99th=[658506] bw ( KiB/s): min= 512, max=130048, per=100.00%, avg=58788.18, stdev=27067.79, samples=1141 iops : min= 2, max= 508, avg=229.63, stdev=105.74, samples=1141 write: IOPS=225, BW=56.4MiB/s (59.2MB/s)(32.0GiB/580821msec); 0 zone resets clat (usec): min=23, max=23560, avg=115.99, stdev=251.13 lat (usec): min=25, max=23570, avg=125.35, stdev=251.63 clat percentiles (usec): | 1.00th=[ 28], 5.00th=[ 41], 10.00th=[ 98], 20.00th=[ 101], | 30.00th=[ 103], 40.00th=[ 105], 50.00th=[ 108], 60.00th=[ 111], | 70.00th=[ 117], 80.00th=[ 130], 90.00th=[ 143], 95.00th=[ 149], | 99.00th=[ 174], 99.50th=[ 212], 99.90th=[ 799], 99.95th=[ 5342], | 99.99th=[12649] bw ( KiB/s): min= 512, max=125952, per=100.00%, avg=59016.54, stdev=28070.89, samples=1137 iops : min= 2, max= 492, avg=230.52, stdev=109.65, samples=1137 lat (usec) : 50=4.79%, 100=5.49%, 250=73.76%, 500=0.26%, 750=0.04% lat (usec) : 1000=0.06% lat (msec) : 2=0.02%, 4=0.03%, 10=7.27%, 20=7.41%, 50=0.71% lat (msec) : 100=0.05%, 250=0.05%, 500=0.03%, 750=0.03%, 1000=0.01% cpu : usr=0.51%, sys=6.56%, ctx=44312, majf=0, minf=0 IO depths : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0% submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% issued rwts: total=131040,131104,0,0 short=0,0,0,0 dropped=0,0,0,0 latency : target=0, window=0, percentile=100.00%, depth=64 Run status group 0 (all jobs): READ: bw=56.4MiB/s (59.1MB/s), 56.4MiB/s-56.4MiB/s (59.1MB/s-59.1MB/s), io=31.0GiB (34.4GB), run=580821-580821msec WRITE: bw=56.4MiB/s (59.2MB/s), 56.4MiB/s-56.4MiB/s (59.2MB/s-59.2MB/s), io=32.0GiB (34.4GB), run=580821-580821msec The dataset used to run the benchmark was created with those parameters: zfs create zfs/test -o casesensitivity=insensitive -o compression=off -o atime=off -o sync=standard Both the read/write speeds and the IOPS are much lower than what those drives should be capable of. @ich777 are there some settings I'm missing or am I doing something wrong? Thanks Andrea

Hi, I'm trying to create a script that gets executed every 5 seconds, to control PWM fan speed. Because Cron doesn't give enough granularity, I had to resort to the watch command. I have created a "parent" script that invokes the watch command with the main script as argument, like this: #!/bin/bash INTERVAL=5 watch --interval $INTERVAL bash /boot/config/plugins/user.scripts/scripts/hdd_fans_control/script If I execute the parent script manually from the command line, like this: bash /boot/config/plugins/user.scripts/scripts/parent/script everything works as expected. While if I execute the parent script via the "Run Script" or "Run in background" buttons from the User Scripts page, the script doesn't work. With "Run Script" I just get an empty output and nothing happens, while if I use "Run in background" (which is how I intend to run the script eventually) I get this output: Script Starting May 29, 2022 11:09.54 Full logs for this script are available at /tmp/user.scripts/tmpScripts/parent/log.txt Error opening terminal: unknown. Script Finished May 29, 2022 11:09.54 Full logs for this script are available at /tmp/user.scripts/tmpScripts/parent/log.txt @Squid do you know how to fix it? What am I doing wrong? Thanks Andrea

Thank you for the reply. Maybe I misunderstood that article, but what I would like to do is to let Unraid and ZFS handle the snapshots of the data on the server, even when the Mac is off. I would then like to use the Time Machine interface on the Mac to browse through the snapshots and restore files and folders if I need. Is that possible?

Hi, I’m putting together a storage server and I’m planning to install Unraid and use the ZFS plugin to have a native ZFS pool as my main storage. The client that will use the storage server the most, runs MacOS. Currently I backup my data via USB using Time Machine. Once the server will be up and running I plan to use ZFS snapshots to create periodic snapshots of all my datasets. Is there a way to access the ZFS snapshots via Time Machine, in a similar way to what can be done in Windows with shadow copies? In other words, is there a plug-in that allows to present the ZFS snapshot to MacOS as it were a Time Machine backup?

Hi, I’m putting together a low power, small form factor storage server running unraid. It will have 8 HDDs with two fans cooling them. The server will be idle for most of the day, with the hard drives spinned down. And during this time I’m aiming for the CPU to reach a low power state, at least C7. I’m trying to find a way to control the two hard drive fans based on the HDD temperatures (with PWM). The BIOS has a series of temperature sensors that can be used to control the fans, but the HDD temperature isn’t on that list. I’ve seen few plug-in and scripts here on the forum to periodically read HDD temp and set fan speed accordingly, say every 5 seconds. Do you know if running a script like that every 5 second “wakes” the CPU up from C7 (or higher) into a higher power state? Are there hardware alternatives (fan controllers?) that can read the hdd temp and control the fans accordingly? Thanks Andrea