Average writes to Disk

mcury

@fireodo said in Average writes to Disk:

@mcury I guess FS is UFS and not ZFS ...

Indeed, UFS here, noatime in fstab

fireodo

@mcury said in Average writes to Disk:

@fireodo said in Average writes to Disk:

@mcury I guess FS is UFS and not ZFS ...

Indeed, UFS here, noatime in fstab

So it seams to cristallise that ZFS is the problem ...

keyser

@mcury said in Average writes to Disk:

SG-3100 - 21.05.1 - pfblockerng dnsbl python mode enabled

iostat -d 5 6

This is really interesting because your box does not suffer from sustained writing from UNBOUND (caused by pfBlockerNG in python mode).
That would suggest it’s a setting or configuration detail that causes the issue.

I wonder what that might be. I think my setup is fairly default, but I have pfBlockerNG creating alias lists instead of it’s own rules.

Maybe we should start a thread with pfBlockerNG configs to see if we can find the root configuration cause for sustained writing to disk in pfBlockerNG?

keyser

@keyser Just as a follow up I think I have now tried EVERY possible setting in my pfBlockerNG setup in terms of making it “quiet” on disk writes.
Nothing sticks - No lists, no logging enabled anywhere, nothing - and still I have a UNBOUND process that writes on average about 380 Kb/s to disk if python mode is enabled.
If I disable Python mode or disable pfBlockerNG in general, UNBOUND no longer does it’s sustained disk writing.

So what could cause that behavior?

fireodo

@keyser said in Average writes to Disk:

Just as a follow up I think I have now tried EVERY possible setting in my pfBlockerNG setup

Good Morning (here it is),

I do not think pfblockerNG (in my case) is the culprit - I just set up a APU2 machine that was yesterday with ZFS and now with UFS and ... voilà: the writings are GONE!

iostat -d 5 6
md0 ada0 pass0
KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s
0.00 0 0.00 22.55 13 0.30 0.38 0 0.00
0.00 0 0.00 0.00 0 0.00 0.00 0 0.00
0.00 0 0.00 0.00 0 0.00 0.00 0 0.00
0.00 0 0.00 4.00 0 0.00 0.00 0 0.00
0.00 0 0.00 4.00 0 0.00 0.00 0 0.00
0.00 0 0.00 0.00 0 0.00 0.00 0 0.00

This seams to prove my suspicion from yesterday that ZFS is causing the heavy writings to disk even if no service is activated on the firewall.

PS. Here the same machine with the same config but ZFS:
iostat -d 5 6
md0 ada0 pass0
KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s
0.00 1 0.00 16.67 41 0.67 0.38 0 0.00
0.00 0 0.00 11.29 26 0.28 0.00 0 0.00
0.00 0 0.00 14.13 19 0.26 0.00 0 0.00
0.00 0 0.00 12.38 21 0.25 0.00 0 0.00
0.00 0 0.00 14.70 19 0.27 0.00 0 0.00
0.00 0 0.00 14.06 21 0.29 0.00 0 0.00

Have a good trip to weekend ...
fireodo

tomashk

I hope I remember correctly, but zfs by default writes every 5 seconds if there is anything to write. Also it depends on type of write operation (synchronous or asynchronous). Because it is easy to revert copy of the pfsense configuration I changed a little zfs configuration on my device (but with it there is a little bit bigger chance of problems in case of not clean shutdown)

So for my device I changed the following:

make all writes asynchronous (probably won't help much here, but software doesn't have to wait for OS to finish writing)

zfs set sync=disabled zroot

System -> Advanced -> System Tunables - set vfs.zfs.txg.timeout to 180 - it will increase time between writes from 5s to 180s; during this time all operations will happen in RAM; but writes could happen earlier if there is too much to write (also OS is able to force writing earlier - I'm not expert so I don't know all conditions); for me write happens once or twice during said 3 minutes
because there is bigger chance of failure with 180s I made zfs to write everything twice (I have 100GB SSD so it is not problem); this won't guaranty data safety, but still (works only for newly written data - old won't be touched)

zfs set copies=2 zroot

That works for me. Please read about it before changing anything. Or at least have configuration backup before you try.

tohil

I use ZFS also but with RAM disks. this will reduce the writes to the ssd massively, right?

  KB/t tps  MB/s   KB/t tps  MB/s   KB/t tps  MB/s   KB/t tps  MB/s
  0.00   1  0.00   0.00   1  0.00  13.97   1  0.01   0.00   0  0.00
  0.00   0  0.00   0.00   0  0.00   0.00   0  0.00   0.00   0  0.00
  0.00   0  0.00   0.00   0  0.00   0.00   0  0.00   0.00   0  0.00
  0.00   0  0.00   0.00  12  0.00   7.86  23  0.18   0.00   0  0.00
  0.00   2  0.00   0.00   2  0.00   0.00   0  0.00   0.00   0  0.00
  0.00   3  0.00   0.00   0  0.00   0.00   0  0.00   0.00   0  0.00

fireodo

@tomashk

I followed your suggestions and it looks good:

iostat -d 5 6
             md0             ada0            pass0
  KB/t tps  MB/s   KB/t tps  MB/s   KB/t tps  MB/s
  0.00   0  0.00  15.55  14  0.21   0.38   0  0.00
  0.00   0  0.00   0.00   0  0.00   0.00   0  0.00
  0.00   0  0.00   0.00   0  0.00   0.00   0  0.00
  0.00   0  0.00   0.00   0  0.00   0.00   0  0.00
  0.00   0  0.00   0.00   0  0.00   0.00   0  0.00
  0.00   0  0.00   0.00   0  0.00   0.00   0  0.00

This is the production machine where initially I found that heavy writing. I give it 24 hours and keep an eye also on the LBA_written.

Thanks anyway!
fireodo

fireodo

@tomashk said in Average writes to Disk:

zfs set sync=disabled zroot

Is this command permanent or has it to be made on each reboot? Thanks

tohil

This is the SMART Test output from one of my boxes, APU2 Board with 16GB SSD...
241 Lifetime_Writes_GiB shows GB count written.... -> 4176.278 TB???? no way....

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000a   100   100   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       8694
 12 Power_Cycle_Count       0x0012   100   100   000    Old_age   Always       -       42
168 SATA_Phy_Error_Count    0x0012   100   100   000    Old_age   Always       -       0
170 Bad_Blk_Ct_Erl/Lat      0x0013   100   100   010    Pre-fail  Always       -       0/20
173 MaxAvgErase_Ct          0x0000   100   100   000    Old_age   Offline      -       385 (Average 775)
192 Unsafe_Shutdown_Count   0x0012   100   100   000    Old_age   Always       -       4
194 Temperature_Celsius     0x0023   070   070   000    Pre-fail  Always       -       30
196 Not_In_Use              0x0000   100   100   000    Old_age   Offline      -       0
218 CRC_Error_Count         0x0000   100   100   000    Old_age   Offline      -       0
241 Lifetime_Writes_GiB     0x0012   100   100   000    Old_age   Always       -       4176278

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended captive    Completed without error       00%      8694         -
# 2  Short captive       Completed without error       00%      8694         -
# 3  Short offline       Completed without error       00%      2557         -

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

fireodo

@tohil said in Average writes to Disk:

241 Lifetime_Writes_GiB shows GB count written.... -> 4176.278 TB???? no way....

Smart is always Device specific - you have to dig for the correct interpretation of those values ... 4 PB is heavy and I don't believe it even its theoretically possible ...

tomashk

@fireodo said in Average writes to Disk:

@tomashk said in Average writes to Disk:

zfs set sync=disabled zroot

Is this command permanent or has it to be made on each reboot? Thanks

It is permanent. You can check if it is set with this command:

zfs get -r sync zroot

(it will show information for whole zfs file system)

and you can revert it with this command if I remember correctly:

zfs set sync=enabled zroot

fireodo

@tomashk

Thank you! Those settings do the trick! Maybe @jimp can take a look on this thread and maybe its something for the next version ...?

Regards,
fireodo

johnpoz

Yeah I would hope that the default settings used for zfs install wouldn't be a determinant to life of SSD or eMMC would have issues with total writes as well..

I don't know of a way to check what eMMC reports for total life write, etc.

fireodo

@johnpoz said in Average writes to Disk:

I don't know of a way to check what eMMC reports for total life write, etc.

As I don't have any device here with eMMC (OK, except my Phone but that's out of my research-reach :-D ) I cannot say anything about it. Is it smart capable? Documentation says its a kind of predecesor of SD-Card ...

johnpoz

If for whatever reason the onboard eMMC died, I know you can add a msata to it.. So that would always be an option.

But would be curious if there is a way to get info from it on total data written, etc.

stephenw10

There's no way to get write data from eMMC AFAIK.

tomashk

@fireodo said in Average writes to Disk:

Thank you! Those settings do the trick! Maybe @jimp can take a look on this thread and maybe its something for the next version ...?

I changed it a few years ago because I was annoyed by constant blinking of the LED when SSD was working :). But I used those options having very basic knowledge of zfs. Now I know it a little bit better so I understand what are downsides of this configuration. And I guess it is far from being optimal. Also I'm not sure if setting it by default on zfs for next version would be good. There are too many variables for different devices to be sure if this is completely safe. But fortunately it easy to restore configuration if something is broken and I don't store important information on pfsense's drive.

fireodo

@tomashk said in Average writes to Disk:

Also I'm not sure if setting it by default on zfs for next version would be good.

Thats why I thought it would be good if some of the developer with far more knowledge about that ZFS take a look at this situation and maybe find a more robust solution...

johnpoz

@stephenw10 if zfs does, at least in its default config cause more writes to the eMMC or SSD.. You mentioned something about

There was a bug at one time that was not mounting root as noatime

That increased drive writes in normal use, is there some change to the zfs config that might be prudent to change.. As being mentioned in this thread for example

System -> Advanced -> System Tunables - set vfs.zfs.txg.timeout to 180

I mean writing 20GB a day for not really doing anything does seem like a lot, its possible there is some error in the math, or interpretation of the info that leads to an exaggerated understanding off the amount written.. The amount of life time writes to eMMC is a concern if zfs is in fact drastically increasing the amount of data written..