> Neglecting to do it or meaning to do it then getting pulled in to some meeting (or other important distraction) and then imagining you did it.

If your job is to make sure your file system and your database—SQLite, Pg, My/MariDB, etc—are tuned together, and you don't tune it, then you should be called into a meeting. Or at least the no-fault RCA should bring up remediation methods to make sure it's part of the SOP so that it won't happen again.

The alternative the GP suggests is using Btrfs, which I find even more irresponsible than your non-tuning situation. (Heck, if someone on my sysadmin team suggested we start using Btrfs for anything I would think they were going senile.)

> Defense is starting to get a blank check with fairly bipartisan support for the first time in at least 30-40 years and it's centered on semiconductor supply chains.

Really? Because:

> During Donald Trump's 2025 speech to a joint session of Congress, the president asked House Speaker Mike Johnson to “get rid” of the subject act.[190]

* https://en.wikipedia.org/wiki/CHIPS_and_Science_Act#Subseque...

> ZFS isn’t viable for SQLite unless you turn off fsync’s in ZFS

Which you can do on a per dataset ('directory') basis very easily:

    zfs set sync=disabled mydata/mydb001

Meanwhile all the rest of your pools / datasets can keep the default POSIX behaviour.

> SQLite on ZFS needs the Fsync behaviour to be off […]

    zfs set sync=disabled mydata/mydb001

> Not sure why you'd need more than 10/8

Large organizations have moved to IPv6 because they, and everyone else, are using 10/8, and so when mergers and acquisitions happen trying to connect the networks together becomes a nightmare.

See this talk from Wells Fargo as an example:

* https://www.youtube.com/watch?v=EzTWjNUb4H4