diff options
author | Adam T. Carpenter <atc@53hor.net> | 2021-01-15 14:48:59 -0500 |
---|---|---|
committer | Adam T. Carpenter <atc@53hor.net> | 2021-01-15 14:48:59 -0500 |
commit | 0c3a3e015b66eeac415580cb9f0391184e54853f (patch) | |
tree | c5301a7f310ada2298160f8f3b47c61692d4373c | |
parent | 57b70c5a30fba783dcbb290b08821d7d3c1e96c1 (diff) | |
download | 53hor-0c3a3e015b66eeac415580cb9f0391184e54853f.tar.xz 53hor-0c3a3e015b66eeac415580cb9f0391184e54853f.zip |
added/finished Zroot mirror vdevs
-rw-r--r-- | cv.html | 2 | ||||
-rw-r--r-- | drafts/2020 reading list.html | 27 | ||||
-rw-r--r-- | drafts/dell-dock.html | 82 | ||||
-rw-r--r-- | drafts/expanding-zroot-mirrored-vdevs.html | 299 | ||||
-rw-r--r-- | drafts/make-your-web-site-look-boring.html | 3 | ||||
-rw-r--r-- | drafts/mpv is literally a flawless video player.html | 1 | ||||
-rw-r--r-- | drafts/my web site looks like this | 0 |
7 files changed, 395 insertions, 19 deletions
@@ -12,7 +12,7 @@ <label for="email">Email</label> <a id="email" href="mailto:atc@53hor.net">atc@53hor.net</a> <label for="www">WWW</label> - <a id="www" href="https://www.53hor.net/profile/">www.53hor.net/profile</a> + <a id="www" href="https://www.53hor.net/info.html">www.53hor.net/profile</a> <label for="git">Git</label> <a id="git" href="https://git.53hor.net">git.53hor.net</a> diff --git a/drafts/2020 reading list.html b/drafts/2020 reading list.html new file mode 100644 index 0000000..9e8cbf1 --- /dev/null +++ b/drafts/2020 reading list.html @@ -0,0 +1,27 @@ +<h1>Adam's <del>2020</del> <ins>Quarantine</ins> Reading List</h1> + +<ul> + <li>The Maltese Falcon</li> + <li>The Big Sleep</li> + <li>The Giver</li> + <li>Harry Potter 1</li> + <li>Harry Potter 1</li> + <li>Harry Potter 1</li> + <li>Harry Potter 1</li> + <li>Harry Potter 1</li> + <li>Harry Potter 1</li> + <li>Harry Potter 7 (finished 2021)</li> + <li>Myst</li> + <li>Myst</li> + <li>Myst</li> + <li>Hatchet</li> + <li>2 detective books?</li> + <li>Theodore Boone</li> + <li>Lighter than Air</li> + <li>Brief Histor of Flight</li> + <li>The Time Machine</li> + <li>The Island of Dr. Moreau</li> + <li>The Invisible Man</li> + <li>Treasure Island</li> + <li>Graf Zeppelin and Hindenburg</li> +</ul> diff --git a/drafts/dell-dock.html b/drafts/dell-dock.html index 4be6691..4a9dd9a 100644 --- a/drafts/dell-dock.html +++ b/drafts/dell-dock.html @@ -1,18 +1,17 @@ -<h1>Make Your Docking Station Work for You on FreeBSD</h1> +<h1>Make Your Docking Station Work for You (on FreeBSD)</h1> <p class="description"> - Here's the problem. I have a Dell Latitude E-series laptop running FreeBSD - 12.1-RELEASE. I also have a Dell E-Port II docking station on my desk. I - wanted to be able to take my shut, sleeping laptop and plop it down on the - docking station, hit the dock power button, and have the laptop wake up and - switch over to all of the docking station peripherals. All of the USB devices - did this without any additional work. However, the ethernet hookup, external - monitor, and speakers all required some additional tinkering. This assumes - that you're already familiar with wired and wireless network interfaces on - FreeBSD! + I have a Dell Latitude E-series laptop running FreeBSD 12.2-RELEASE. I also + have a Dell E-Port II docking station on my desk. I wanted to be able to take + my shut, sleeping laptop and plop it down on the docking station, hit the dock + power button, and have the laptop wake up and switch over to all of the + docking station peripherals. So I did it! And now I'm going to write about it + so I don't forget how. You need to know a little bit about FreeBSD + <code>sysctl</code> knobs, display outputs in X, sound devices, and + <code>ifconfig</code> networking. </p> -<h2>Link Aggregation (Failover)</h2> +<h2>Switching from Ethernet to WiFi and Back Again, Seamlessly</h2> <p> FreeBSD doesn't magically swap from wireless to wired connections by default, @@ -20,21 +19,21 @@ <a href="https://www.freebsd.org/doc/handbook/network-aggregation.html" >FreeBSD handbook page on network aggregation</a > - as it's where I found out how to do what I'm about to show you. Basically, + as it's where I found out about link aggregation and failover. Basically, aggregation lets you bind two of your network interfaces together into a single virtual interface. Failover lets your traffic continue moving as long - as one of the aggregated interfaces has is connected. The steps I had to - follow are as follows: + as one of the aggregated interfaces has is connected. + Here's what I had to do: </p> -<ul> +<ol> <li> - Bind the wireless network interface to the MAC address of the wired - interface + Bind the wireless network interface (wlan0) to the MAC address of the wired + interface (em0) </li> <li>Create a lagg interface using the two network interfaces</li> <li>Bind the lagg interface to an IP address, preferably with DHCP</li> -</ul> +</ol> <p>All of this is configured in my <code>rc.conf</code>:</p> @@ -54,3 +53,50 @@ ifconfig_lagg0="up laggproto failover laggport em0 laggport wlan0 DHCP" # <- con will take over. This transition happens instantly, and without interrupting traffic; active transactions aren't cut short for example. </p> + +<h2>Sleeping on Lid Close Except When Docked</h2> + +<p> + This is an easy one. You can use <code>sysctl</code> to configure what happens + when a laptop lid is closed. I wanted the lid closing while undocked to + suspend (put the laptop to sleep). When it's docked however, I don't use the + internal display and wanted to be able to shut the lid and leave it shut. If you read <code>ACPI(4)</code> in the manual, you'll find this little passage: +</p> + +<pre> +<blockquote> +hw.acpi.lid_switch_state + Suspend state (S1-S5) to enter when the lid switch (i.e., a + notebook screen) is closed. Default is "NONE" (do nothing). +</blockquote> +<pre> + +<p>I changed this value a long time ago so closing the lid suspends the laptop. You can check with <code>sysctl</code>:</p> + +<pre> +<code> +$ sysctl hw.acpi.lid_switch_state +hw.acpi.lid_switch_state: S3 +</code> +</pre> + +<p>Now, if I wanted to disable this functionality, I would just change this parameter as root:</p> + +<pre> +<code> +$ doas sysctl hw.acpi.lid_switch_state=NONE +hw.acpi.lid_switch_state: NONE -> NONE +</code> +</pre> + +This change takes effect immediately. I can open and close the lid and nothing happens but turning off the screen. Awesome. + +<h2>Swapping Primary Display Outputs (Also Nvidia Screen-Tearing)</h2> + +<h2>Switching Default Sound Device</h2> + +<h2>Putting It All Together (Scripts Are Glue)</h2> + +<h2>What I Didn't Have to Do</h2> + +usb devices, battery/charging diff --git a/drafts/expanding-zroot-mirrored-vdevs.html b/drafts/expanding-zroot-mirrored-vdevs.html new file mode 100644 index 0000000..e15f262 --- /dev/null +++ b/drafts/expanding-zroot-mirrored-vdevs.html @@ -0,0 +1,299 @@ +<h1>Root on ZFS: A ZPool of Mirror VDEVs</h1> + +<p class="description"> + I wanted/needed to make a root on ZFS pool out of multiple mirror VDEVs, and + since I'm not a ZFS expert, I took a little shortcut. +</p> + +<p> + I recently got a new-to-me server (yay!) and I wanted to do a root-on-ZFS + setup on it. I've really enjoyed using ZFS for my data storage pools for a + long time. I've also enjoyed the extra functionality that comes with having a + bootable system installed on ZFS on my laptop and decided with this upgrade + it's time to do the same on my server. Historically I've used RAIDZ for my + storage pools. RAIDZ functions almost like a RAID10 but at the ZFS level. It + gives you parity so that a certain number of disks can die from your pool and + you won't lose any data. It does have a few tradeoffs however*, and for + personal preferences I've decided that for the future I would like to have a + single ZPool over top of multiple mirror VDEVs. In other words, my main + root+storage pool will be made up of two-disk mirrors and can be expanded to + include any number of new mirrors I can fit into the machine. +</p> + +<p> + This did present some complications. First of all, + <code>bsdinstall</code> won't set this up for you automatically (and sure + enough, + <a href="https://www.freebsd.org/doc/handbook/bsdinstall-partitioning.html" + >in the handbook</a + > + it mentions the guided root on ZFS tool will only create a single, top-level + VDEV unless it's a stripe). It will happily let you use RAIDZ for your ZROOT + but not the more custom approach I'm taking. I did however use + <code>bsdinstall</code> as a shortcut so I wouldn't have to do all of the + partitioning and pool setup manually, and that's what I'm going to document + below. Because I'm totally going to forget how this works the next time I have + to do it. +</p> + +<p> + In my scenario I have an eight-slot, hot-swappable PERC H310 controller that's + configured for AHCI passthrough. In other words, all FreeBSD sees is as many + disks as I have plugged into the backplane. I'm going to fill it with 6x2TB + hard disks which, as I said before, I want to act as three mirrors (two disks + each) in a single, bootable, growable ZPool. For starters, I shoved the + FreeBSD installer on a flash drive and booted from it. I followed all of the + regular steps (setting hostname, getting online, etc.) until I got to the + guided root on ZFS disk partitioning setup. +</p> + +<p> + Now here's where I'm going to take the first step on my shortcut. Since there + is no option to create the pool of arbitrary mirrors I'm just going to create + a pool from a single mirror VDEV of two disks. Later I will expand the pool to + include the other two mirrors I had intended for. My selections were as + follows: +</p> + +<ul> + <li>Pool Type/Disks: mirror mfisyspd0 mfisyspd1</li> + <li>Pool Name: zroot</li> + <li>Partition Scheme: GPT (EFI)</li> + <li>Swap Size: 4g</li> +</ul> + +<p> + Everything else was left as a default. Then I followed the installer to + completion. At the end, when it asked if I wanted to drop into a shell to do + more to the installation, I did. +</p> + +<p> + The installer created the following disk layout for the two disks that I + selected. +</p> + +<pre> +<code> +atc@macon:~ % gpart show +=> 40 3907029088 mfisyspd0 GPT (1.8T) + 40 409600 1 efi (200M) + 409640 2008 - free - (1.0M) + 411648 8388608 2 freebsd-swap (4.0G) + 8800256 3898228736 3 freebsd-zfs (1.8T) + 3907028992 136 - free - (68K) + +=> 40 3907029088 mfisyspd1 GPT (1.8T) + 40 409600 1 efi (200M) + 409640 2008 - free - (1.0M) + 411648 8388608 2 freebsd-swap (4.0G) + 8800256 3898228736 3 freebsd-zfs (1.8T) + 3907028992 136 - free - (68K) +</code> +</pre> + +<p> + The installer also created the following ZPool from my single mirror VDEV. +</p> + +<pre> +<code> +atc@macon:~ % zpool status + pool: zroot + state: ONLINE + scan: none requested +config: + + NAME STATE READ WRITE CKSUM + zroot ONLINE 0 0 0 + mirror-0 ONLINE 0 0 0 + mfisyspd0p3 ONLINE 0 0 0 + mfisyspd1p3 ONLINE 0 0 0 + +errors: No known data errors +</code> +</pre> + +<p> + There are a couple of things to take note of here. First of all, + <em>both</em> disks in the bootable ZPool have an EFI boot partition. That + means they're both a part of (or capable of?) booting the pool. Second, they + both have some swap space. Finally, they both have a third partition which is + dedicated to ZFS data, and that partition is what got added to my VDEV. +</p> + +<p> + So where do I go from here? I was tempted to just + <code>zpool add mirror ... ...</code> and just add my other disks to the pool + (actually, I <em>did</em> do this but it rendered the volume unbootable for a + very important reason), but then I wouldn't have those all-important boot + partitions (using whole-disk mirror VDEVS). Instead, I need to manually go + back and re-partition four disks exactly like the first two. Or, since all I + want is two more of what's already been done, I can just clone the partitions + using <code>gpart backup</code> and <code>restore</code>! Easy! Here's what I + did for all four remaining disks: +</p> + +<pre> +<code> +root@macon:~ # gpart backup mfisyspd0 | gpart restore -F mfisyspd2` +</code> +</pre> + +<p> + Full disclosure, I didn't even think of this as a possibility + <a + href="ihttps://unix.stackexchange.com/questions/472147/replacing-disk-when-using-freebsd-zfs-zroot-zfs-on-partition#472175" + >until I read this Stack Exchange post</a + >. This gave me a disk layout like this: +</p> + +<pre> +<code> +atc@macon:~ % gpart show +=> 40 3907029088 mfisyspd0 GPT (1.8T) + 40 409600 1 efi (200M) + 409640 2008 - free - (1.0M) + 411648 8388608 2 freebsd-swap (4.0G) + 8800256 3898228736 3 freebsd-zfs (1.8T) + 3907028992 136 - free - (68K) + +=> 40 3907029088 mfisyspd1 GPT (1.8T) + 40 409600 1 efi (200M) + 409640 2008 - free - (1.0M) + 411648 8388608 2 freebsd-swap (4.0G) + 8800256 3898228736 3 freebsd-zfs (1.8T) + 3907028992 136 - free - (68K) + +=> 40 3907029088 mfisyspd2 GPT (1.8T) + 40 409600 1 efi (200M) + 409640 2008 - free - (1.0M) + 411648 8388608 2 freebsd-swap (4.0G) + 8800256 3898228736 3 freebsd-zfs (1.8T) + 3907028992 136 - free - (68K) + +=> 40 3907029088 mfisyspd3 GPT (1.8T) + 40 409600 1 efi (200M) + 409640 2008 - free - (1.0M) + 411648 8388608 2 freebsd-swap (4.0G) + 8800256 3898228736 3 freebsd-zfs (1.8T) + 3907028992 136 - free - (68K) + +=> 40 3907029088 mfisyspd4 GPT (1.8T) + 40 409600 1 efi (200M) + 409640 2008 - free - (1.0M) + 411648 8388608 2 freebsd-swap (4.0G) + 8800256 3898228736 3 freebsd-zfs (1.8T) + 3907028992 136 - free - (68K) + +=> 40 3907029088 mfisyspd5 GPT (1.8T) + 40 409600 1 efi (200M) + 409640 2008 - free - (1.0M) + 411648 8388608 2 freebsd-swap (4.0G) + 8800256 3898228736 3 freebsd-zfs (1.8T) + 3907028992 136 - free - (68K) +</code> +</pre> + +<p> + And to be fair, this makes a lot of logical sense. You don't want a six-disk + pool to only be bootable by two of the disks or you're defeating some of the + purposes of redundancy. So now I can extend my ZPool to include those last + four disks. +</p> + +<p> + This next step may or may not be a requirement. I wanted to overwrite where I + assumed any old ZFS/ZPool metadata might be on my four new disks. This could + just be for nothing and I admit that, but I've run into trouble in the past + where a ZPool wasn't properly exported/destroyed before the drives were + removed for another purpose and when you use those drives in future + <code>zpool import</code>s, you can see both the new and the old, failed + pools. And, in the previous step I cloned an old ZFS partition many times! So + I did a small <code>dd</code> on the remaining disks to help me sleep at + night: +</p> + +<pre> +<code> +root@macon:~ # dd if=/dev/zero of=/dev/mfisyspd2 bs=1M count=100 +</code> +</pre> + +<p> + One final, precautionary step is to write the EFI boot loader to the new + disks. In + <a href="https://www.freebsd.org/doc/handbook/zfs-zpool.html" + >zpool admin handbook</a + > + it mentions you should do this any time you <em>replace</em> a zroot device, + so I'll do it just for safe measure on all four additional disks: +</p> + +<pre> +<code> +root@macon:~ # gpart bootcode -p /boot/boot1.efifat -i 1 mfisyspd2 +</code> +</pre> + +<p> + Don't forget that the command is different for UEFI and a traditional BIOS. + And finally, I can add my new VDEVs: +</p> + +<pre> +<code> +root@macon:~ # zpool zroot add mirror mfisyspd2p3 mfisyspd3p3 +root@macon:~ # zpool zroot add mirror mfisyspd4p3 mfisyspd5p3 +</code> +</pre> + +<p>And now my pool looks like this:</p> + +<pre> +<code> +atc@macon:~ % zpool status + pool: zroot + state: ONLINE + scan: none requested +config: + + NAME STATE READ WRITE CKSUM + zroot ONLINE 0 0 0 + mirror-0 ONLINE 0 0 0 + mfisyspd0p3 ONLINE 0 0 0 + mfisyspd1p3 ONLINE 0 0 0 + mirror-1 ONLINE 0 0 0 + mfisyspd2p3 ONLINE 0 0 0 + mfisyspd3p3 ONLINE 0 0 0 + mirror-2 ONLINE 0 0 0 + mfisyspd4p3 ONLINE 0 0 0 + mfisyspd5p3 ONLINE 0 0 0 + +errors: No known data errors +</code> +</pre> + +<p> + Boom. A growable, bootable zroot ZPool. Is it easier than just configuring the + partitions and root on ZFS by hand? Probably not for a BSD veteran. But since + I'm a BSD layman, this is something I can live with pretty easily. At least + until this becomes an option in <code>bsdintall</code> maybe? At least now I + can add as many more mirrors as I can fit into my system. And it's just as + easy to replace them. This is better for me than my previous RAIDZ, where I + would have to destroy and re-create the pool in order to add more disks to the + VDEV. Now I just create another little mirror and grow the pool and all of my + filesystems just see more storage. And of course, having ZFS for all of my + data makes it super easy to create filesystems on the fly, compress or quota + them, and take snapshots (including the live ZROOT!) and send those snapshots + over the network. Pretty awesome. +</p> + +<p> + * I'm not going to explain why here, but + <a href="http://www.openoid.net/zfs-you-should-use-mirror-vdevs-not-raidz/" + >this is a pretty well thought out article</a + > + that should give you an idea about the pros and cons of RAIDZ versus mirror + VDEVs so you can draw your own conclusions. +</p> diff --git a/drafts/make-your-web-site-look-boring.html b/drafts/make-your-web-site-look-boring.html new file mode 100644 index 0000000..c43b218 --- /dev/null +++ b/drafts/make-your-web-site-look-boring.html @@ -0,0 +1,3 @@ +<h1>Make Your Web Site Boring!</h1> + +- functional - not disctracting - tasteful - readable diff --git a/drafts/mpv is literally a flawless video player.html b/drafts/mpv is literally a flawless video player.html new file mode 100644 index 0000000..75c09a0 --- /dev/null +++ b/drafts/mpv is literally a flawless video player.html @@ -0,0 +1 @@ +talk about playlist auto-chapters from description timesttamps diff --git a/drafts/my web site looks like this b/drafts/my web site looks like this deleted file mode 100644 index e69de29..0000000 --- a/drafts/my web site looks like this +++ /dev/null |