Disks

zfs: setting compression and adding new vdevs

If you read my recent posts, I’m replacing an existing zpool with new devices. At first, I went to copy the old zpool to a new zpool. I then decided instead of copying, to replace. I’m also going to see about compression. I’m sure it won’t take effect, because replace is a block-by-block copy, or so I think. We’ll confirm. Before Here is the zpool, really, just the top-level filesystem. Notice how compression […]

zfs: setting compression and adding new vdevs Read More »

Moving a zpool to new devices – after the syncoid copy – oh wait, zfs replace

This morning, as I was typing the subject of this blog post, I realized I don’t have to do this copying. The new devices are staying in this host. It is better for me to add the new devices to the zpool and remove the old devices. That is so much easier. The existing zpool can stay in use and there is no interruption in service. NOTE: after publishing this entry, I realized

Moving a zpool to new devices – after the syncoid copy – oh wait, zfs replace Read More »

Compression results

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 »

GEOM: nda1: the primary GPT table is corrupt or invalid

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 »

Experimenting with compression=zstd

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 »

Experimenting with compression=lz4

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 »

Experimenting with compression off

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 »

Adding in new NVMe cards and sticks – and replacing two SSDs

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 »

Clear the existing good drive and add it to the new zpool

In recent posts: Doing a bit of stress work on a new HDD x8dtu: adding in the smaller drive Swapping zpools – moving from using main_tank to using data If you have a look over those posts, you’ll see why you never want to downsize a zpool. In this post: FreeBSD 14.2 removing the zfs labels from an drive which was part of a zpool which is no longer in use destroying the

Clear the existing good drive and add it to the new zpool Read More »

Swapping zpools – moving from using main_tank to using data

As mentioned in Doing a bit of stress work on a new HDD, I have a failing 5TB drive which is going to be replace by a 4TB drive. Only about 1.45TB are used, so there’s plenty of space to grow. If you get one thing from this post, don’t be downsizing zpools like this. I would have had much less work and opportunity for error, if I had returned that 4TB drive

Swapping zpools – moving from using main_tank to using data Read More »

Scroll to Top