That sounds like a title of one of my internal developer-facing tickets related to shadow copies. I didn't add regex support at this time. You can use unix wildcards to restrict which snapshots get presented as previous versions to vss clients though though the auxiliary parameters:According to the release notes:
How do we use regular expressions to filter the snapshot names? It doesn't seem to work in the search box.
shadow:include = aapl-*(only show snapshots beginning with "aapl-"), or
shadow:exclude = aapl-*(exclude snapshots with names beginning with "aapl-"). Multiple filters are supported
shadow:include = aapl-* vss-*presents snapshots beginning with "aapl-" or "vss-".
root@truenas[~]# sysctl -a | grep cpu kern.smp.cpus: 2 kern.smp.maxcpus: 256 kern.ccpu: 0 <cpu count="2" mask="3,0,0,0">0, 1</cpu> kern.sched.cpusetsize: 32 kern.pin_pcpu_swi: 0 kern.racct.pcpu_threshold: 1 kern.hwpmc.nbuffers_pcpu: 32 kern.hwpmc.cpuid: AuthenticAMD-16-06-2 cpu HAMMER device cpufreq device cpuctl kern.vt.splash_cpu_duration: 10 kern.vt.splash_cpu_style: 2 kern.vt.splash_ncpu: 0 kern.vt.splash_cpu: 0 vfs.ncpurgeminvnodes: 16 net.inet.tcp.per_cpu_timers: 0 debug.cpufreq.verbose: 0 debug.cpufreq.lowest: 0 debug.acpi.cpu_unordered: 0 kdb.enter.default=write cn_mute 1; watchdog 38; capture on; bt; show allpcpu; ps; alltrace; write cn_mute 0; textdump dump; reset hw.ncpu: 2 hw.vmm.bhyve_xcpuids: 396 hw.vmm.topology.cpuid_leaf_b: 1 hw.acpi.cpu.cx_lowest: C8 hw.intrs: irq0: attimer0:3 @cpu0(domain0): 0 irq1: atkbd0:1 @cpu0(domain0): 2 irq3::5 @cpu0(domain0): 0 irq4: uart0:7 @cpu0(domain0): 0 irq5::9 @cpu0(domain0): 0 irq6::11 @cpu0(domain0): 0 irq7::13 @cpu0(domain0): 0 irq8: atrtc0:15 @cpu0(domain0): 0 irq9: acpi0:17 @cpu0(domain0): 0 irq10::19 @cpu0(domain0): 0 irq11::21 @cpu0(domain0): 0 irq12::23 @cpu0(domain0): 0 irq13::25 @cpu0(domain0): 0 irq14: ata0:27 @cpu0(domain0): 0 irq15: ata1:29 @cpu0(domain0): 22167 irq16: ohci0 ohci1:31 @cpu0(domain0): 3 irq17: ehci0:33 @cpu0(domain0): 0 irq18: ohci2 ohci3+:35 @cpu0(domain0): 4 irq19: ehci1:37 @cpu0(domain0): 0 irq20::39 @cpu0(domain0): 0 irq21::41 @cpu0(domain0): 0 irq22: ahci0:43 @cpu0(domain0): 11886 irq23::45 @cpu0(domain0): 0 irq256: hpet0:t0:49 @cpu0(domain0): 191170 irq257: hpet0:t1:51 @cpu1(domain0): 164190 irq258: hpet0:t2:53 @cpu0(domain0): 0 irq259: em0:irq0:55 @cpu0(domain0): 0 irq260: em1:irq0:57 @cpu0(domain0): 0 irq261: alc0:59 @cpu0(domain0): 27895 dev.cpufreq.0.%parent: cpu0 dev.cpufreq.0.%pnpinfo: dev.cpufreq.0.%location: dev.cpufreq.0.%driver: cpufreq dev.cpufreq.0.%desc: dev.cpufreq.%parent: dev.hwpstate.0.%parent: cpu0 dev.acpi_perf.1.%parent: cpu1 dev.acpi_perf.0.%parent: cpu0 dev.cpu.1.cx_method: C1/hlt dev.cpu.1.cx_usage_counters: 118071 dev.cpu.1.cx_usage: 100.00% last 11145us dev.cpu.1.cx_lowest: C8 dev.cpu.1.cx_supported: C1/1/0 dev.cpu.1.temperature: 20.0C dev.cpu.1.%parent: acpi0 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%location: handle=\_PR_.P002 dev.cpu.1.%driver: cpu dev.cpu.1.%desc: ACPI CPU dev.cpu.0.cx_method: C1/hlt dev.cpu.0.cx_usage_counters: 139252 dev.cpu.0.cx_usage: 100.00% last 6646us dev.cpu.0.cx_lowest: C8 dev.cpu.0.cx_supported: C1/1/0 dev.cpu.0.freq_levels: 3000/32062 2300/27030 1800/23152 800/8492 dev.cpu.0.freq: 3000 dev.cpu.0.temperature: 20.0C dev.cpu.0.%parent: acpi0
hmm .. .I currently use a 32GB M.2 drive for booting that I got for $10 shipped off of ebay.. before that I picked up 2 x 120GB SSD's that I got for $20 and used one via a USB to SATA cable for a boot drive for quite awhile with zero issues .. I've used 60 and 40GB SSD's in the past as well .. I've never used an HDD for booting though.All that being said though, truenas is great and by far the best in category (IMHO). And I def WILL recommend it to other people.
If they can only give us some additional features for the boot-pool drive isolation, I would be a happy camper.
Let me explain what I mean better:
Lets say you want to build an entirely new TrueNAS server. Now you want a boot drive that's small(byte size), preferably fast(to avoid any bottlenecks) and has good reliability.
Problem is: You can't find something that meets all those criteria now a days. Smallest newly manufactured HDD drives is 1TB (might be 500GB, for some companies). Smallest newly manufactured SSD drives is 240(for most companies as far as I know). And using NVMe is discouraged by most of the community, due to it not increasing performance in any meaningful way (right?). Using a USB Flashdrive(or T-Flash) as a boot device is also strongly discouraged.
So whats left now?
Now you have to either install a 240GB SSD or a 500GB HDD. And all you're allowed to use of those drives is the OS and system dataset, which I supposed can turn into 2xx GiB in about 10 years, along with logs.
But come on....
That's just wasteful and stupid.
Atleast allow me to store some of my VMs on it, the VM will benefit greatly from running off a fast storage media such as SSD. And then it might even be viable to start using a NVMe for a boot disk.
I can still replicate my VMs to a RAID setup for redundancy. This is a no-brainer for me, dunno why IXSystems has insisted on this approach for so long
I frequently recommended these here on the forum - available new:Smallest newly manufactured SSD drives is 240(for most companies as far as I know).