ZFS

Moving a zpool to smaller drives #ZFS #FreeBSD – fails

This post is part of a series of storage-related posts. The goal: move the zroot of r730-01 to smaller drives. NOTE: This approach failed. Investigations continue, however this post is not something you should try. Earlier today, as the first step in my proof-of-concept, I moved the zroot of r730-04 from 2x SATADOM device (128G) to 2x SSD devices (1TB). I could have just installed FreeBSD on the 1TB drives, but that wouldn’t […]

Moving a zpool to smaller drives #ZFS #FreeBSD – fails Read More »

gpart backup | gpart restore does not alway give you exact replication

Today I was setting up some drives for testing. I did this manually: root@r730-04:~ # gpart create -s gpt da2 da2 created root@r730-04:~ # gpart add -t efi -s 260M -a 4k da2 da2p1 added root@r730-04:~ # gpart add -t freebsd-swap -s 8G -a 4k da2 da2p2 added root@r730-04:~ # gpart add -t freebsd-zfs -a 4k da2 da2p3 added root@r730-04:~ # gpart show da2 => 40 62533216 da2 GPT (30G) 40 532480 1

gpart backup | gpart restore does not alway give you exact replication Read More »

Using SATADOM drives in a Dell R730

A recent goal is to increase the available storage space in my main development server in the basement. To that end, two recent posts: r730-01: the drive replacement plan r730-01: storage plan The SATADOM devices I purchased are meant to be plugged directly into the M/B of the server. This approach will free up two PCIe slots which were hosting 2x 2.5″ SSDs in a hot-swap adaptor (the post mentions a Dell R720;

Using SATADOM drives in a Dell R730 Read More »

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 »

Creating the new zpools

I have 4 new storage devices to create 2 new zpools, each a two-vdev mirror. Let’s go. In this post: FreeBSD 14.3 These are the drives I have. As an Amazon Associate I earn from qualifying purchases. The 4TB NVMe cards are Samsung 990 EVO Plus SSD 4TB, PCIe Gen 4×4 | Gen 5×2 M.2 The 4TB SSDs are SAMSUNG 870 EVO 4TB 2.5 Inch SATA III Internal SSD (MZ-77E4T0B/AM) The new data02

Creating the new zpools 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 »

Scroll to Top