Let’s tally up. For reference, this is one of a series of posts regarding compression testing on zpools: Experimenting with compression off Experimenting with compression=lz4 Experimenting with compression=zstd Compression results – you are here Samsung-SSD-870 4TB SSD For the Samsung-SSD-870 4TB SSD no compression we had: 2:34 = 154s 2:32 = 152s 2:30 = 150s 3:52 = 238s 4:46 = 286s 4:16 = 256s 4:15 = 255s 4:15 = 255s 4:49 = 289s […]
Compression results Read More »
When I destroyed the zpools when I was done with zstd compression testing, these errors appeared in /var/log/messages: You’d be shocked to learn these messages appear when creating a zpool with those devices: [12:21 r730-01 dvl ~/tmp] % sudo zpool create Samsung-SSD-980-PRO-geom-issues mirror /dev/nda1 /dev/nda2 re: Background: these two devices were part of a zpool before I started playing with them. They had partitions on them. Recovery and destroy There may be a
GEOM: nda1: the primary GPT table is corrupt or invalid Read More »
Following on from my previous post where I tested lz4, let’s try compression=zstd. Experimenting with compression off Experimenting with compression=lz4 Experimenting with compression=zstd – you are here Compression results First, we delete the old: [21:19 r730-01 dvl ~/tmp] % sudo zpool destroy Samsung-SSD-870-compression-lz4 [21:19 r730-01 dvl ~/tmp] % sudo zpool destroy Samsung-SSD-980-PRO-compression-lz4 [21:19 r730-01 dvl ~/tmp] % sudo zpool destroy Samsung-SSD-990-EVO-compression-lz4 Then create the new: [21:19 r730-01 dvl ~/tmp] % sudo zpool create
Experimenting with compression=zstd Read More »
Following on from my previous post where I tested with compress off, let’s try compression=lz4. Experimenting with compression off Experimenting with compression=lz4 – you are here Experimenting with compression=zstd Compression results First, we delete the old: [19:45 r730-01 dvl ~] % sudo zpool destroy Samsung-SSD-870-no-compression [19:45 r730-01 dvl ~] % sudo zpool destroy Samsung-SSD-980-PRO-no-compression [19:46 r730-01 dvl ~] % sudo zpool destroy Samsung-SSD-990-EVO-no-compression [19:46 r730-01 dvl ~] % Then create the new: [19:47
Experimenting with compression=lz4 Read More »
Now that the new storage is in place, I thought to test with compression on and off. Perhaps also use both lz4 and zstd. For reference, this is one of a series of posts regarding compression testing on zpools: Experimenting with compression off – you are here Experimenting with compression=lz4 Experimenting with compression=zstd Compression results My plan: create three zpools of two mirrored devices and test. There will be three posts: compression off,
Experimenting with compression off Read More »
I notice I also worked with some SSDs at the end of this post – I have since amended the title of this post. In this post: FreeBSD 14.3 Today I removed two existing NVMe cards, each with a 1TB stick on it. Those sticks were added to these cards: If you want the same hardware, you can use these links. As an Amazon Associate I earn from qualifying purchases. These are all
Adding in new NVMe cards and sticks – and replacing two SSDs Read More »
This post is mostly for my benefit, so I can keep track of my plan for adjusting space. It doesn’t contain much of educational value. One recent day, I powered off r730-01 and took inventory of the 16 drive bays. A short overview: [17:36 r730-01 dvl ~] % zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT data01 5.81T 2.84T 2.97T – – 1% 48% 1.00x ONLINE – data02
r730-01: the drive replacement plan Read More »
FreeBSD has a great concept of establishing default values and letting the user override them. That approach does not apply to newsyslog, and specifically, newsyslog.conf This idea came up on IRC after I said I was looking forward to a new FreeBSD 15 which allows the compression specified in newsyslog.conf to be overridden. Using /etc/newsyslog.conf.d Getting a clean copy First, I grabbed a pristine copy of /etc/newsyslog.conf from the repo: [12:34 r730-01 dvl
Cannot override /etc/newsyslog.conf with /etc/newsyslog.conf.d/newsyslog.conf Read More »
Recently I’ve been playing with NVMe to find out more about monitoring for wear. Tried nvme-cli: [17:49 r730-01 dvl ~] % nvme list Failed to scan topology: No such file or directory Seems it is a known problem. Went with this instead: [17:52 r730-01 dvl ~] % sudo nvmecontrol devlist nvme0: Samsung SSD 980 PRO with Heatsink 1TB nvme0ns1 (953869MB) nvme1: Samsung SSD 980 PRO with Heatsink 1TB nvme1ns1 (953869MB) With more information
Finding out more about nvme on FreeBSD Read More »
I have a jail on r730-01 called dvl-ingress01. Here are some filesystems related to that jail: [11:50 r730-01 dvl ~] % zfs list | grep dvl-ingress01 | grep repos NAME USED AVAIL REFER MOUNTPOINT data02/freshports/dvl-ingress01/ingress/repos 8.65G 1011G 112K /jails/dvl-ingress01/var/db/ingress/repos data02/freshports/dvl-ingress01/ingress/repos/doc 706M 1011G 678M /jails/dvl-ingress01/var/db/ingress/repos/doc data02/freshports/dvl-ingress01/ingress/repos/ports 3.53G 1011G 2.30G /jails/dvl-ingress01/var/db/ingress/repos/ports data02/freshports/dvl-ingress01/ingress/repos/src 4.44G 1011G 2.73G /jails/dvl-ingress01/var/db/ingress/repos/src data02/freshports/dvl-ingress01/repos 120K 1011G 120K /jails/dvl-ingress01/var/db/ingress/repos That is not a complete list, but it illustrates the filesystems I’m working with
Mounting and unmounting zfs filesystems within a #FreeBSD jail Read More »