Zfs nvme log and cache - Revision history

Busk at 15:42, 22 May 2026

2026-05-22T15:42:26Z

Busk at 15:42, 22 May 2026

2026-05-22T15:42:11Z

Busk: Created page with "``` sudo nvme list Node Generic SN Model Namespace Usage Format..."

2026-05-22T15:36:45Z

Created page with "``` sudo nvme list Node Generic SN Model Namespace Usage Format..."

New page

```
sudo nvme list
Node Generic SN Model Namespace Usage Format FW Rev
--------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- --------
/dev/nvme0n1 /dev/ng0n1 CVFT439300062P0EGN INTEL SSDPEDMD020T4 0x1 2.00 TB / 2.00 TB 512 B + 0 B 8DV101H0

# 1. Create a new GPT partition table
sudo parted /dev/nvme0n1 mklabel gpt

# 2. Create the first 1TB partition (for SLOG)
sudo parted -a optimal /dev/nvme0n1 mkpart primary 0% 1TB

# 3. Create the second 1TB partition (for L2ARC)
sudo parted -a optimal /dev/nvme0n1 mkpart primary 1TB 100%

lsblk /dev/nvme0n1

# Add to log
sudo zpool add <pool_name> log /dev/nvme0n1p1

# Add to cache
sudo zpool add <pool_name> cache /dev/nvme0n1p2

```

← Older revision		Revision as of 15:42, 22 May 2026
Line 87:		Line 87:
	Important Warning: If you go the LVM route, ensure you are not creating a circular dependency where your root filesystem (and thus LVM) depends on a ZFS pool that is trying to access an LVM volume. Given your expertise, this is likely a non-issue, but it is a common pitfall.		Important Warning: If you go the LVM route, ensure you are not creating a circular dependency where your root filesystem (and thus LVM) depends on a ZFS pool that is trying to access an LVM volume. Given your expertise, this is likely a non-issue, but it is a common pitfall.

−	~~Are you planning to stick with static partitioning, or does the LVM approach fit your current infrastructure design better?~~

	```		```

@@ Line 23: / Line 23: @@
 # Add to cache
 sudo zpool add <pool_name> cache /dev/nvme0n1p2
 ```