Mon Apr  9 09:33:25 EDT 2018

Slept from ten to seven. Woke briefly around three, but otherwise slept well.

High of forty today. Chance of rain/snow in the afternoon.

Thought I was almost over this cold, but it's hanging on tenaciously.

Work:
- Order replacement 16:9 LCD for Sherwood
  Done.
- What is up with IO on Postoffice (and possibly all the Windows VM's on Mizzen)?
  Investigated, but I still don't know the cause of the slowness.

```
--- mizzen ~ $  sudo parted -l | grep -A 6 -e 'vg0-postoffice--data' -e 'vg0-florida--mail'
Disk /dev/mapper/vg0-florida--mail: 537GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End    Size   File system  Name                          Flags
 1      17.4kB  134MB  134MB               Microsoft reserved partition  msftres
 2      135MB   537GB  537GB  ntfs         Basic data partition
--
Disk /dev/mapper/vg0-postoffice--data: 193GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End    Size   File system  Name                          Flags
 1      17.4kB  134MB  134MB               Microsoft reserved partition  msftres
 2      135MB   193GB  193GB  ntfs         Basic data partition
--- mizzen ~ $  sudo parted /dev/mapper/vg0-postoffice--data 'align-check optimal 1'
1 not aligned
--- mizzen ~ $  sudo parted /dev/mapper/vg0-postoffice--data 'align-check optimal 2'
2 aligned
--- mizzen ~ $  sudo parted /dev/mapper/vg0-florida--mail 'align-check optimal 1'
1 not aligned
--- mizzen ~ $  sudo parted /dev/mapper/vg0-florida--mail 'align-check optimal 2'
2 aligned
```

I guess it doesn't matter that the MRP isn't aligned.
This probably isn't a misalignment problem, then.

This is a simple two-disk mirror, so RAID chunk size doesn't figure into it.

https://www.safaribooksonline.com/library/view/managing-raid-on/9780596802035/ch01.html
> Stripe-size versus chunk-size
> The stripe-size of an array defines the amount of data written to a group of parallel disk blocks. Assume you have an array of four disks with a stripe size of 64 KB (a common default). In this case, 16 KB worth of data is written to each disk (see Figure 1-4), for a total of 64 KB per stripe. An array's chunk-size defines the smallest amount of data per write operation that should be written to each individual disk. That means a striping array made up of four disks, with a chunk-size of 64 KB, has a stripe-size of 256 KB, because a minimum of 64 KB is written to each component disk. Depending on the specific RAID implementation, users may be asked to set a stripe-size or a chunk-size. For example, most hardware RAID controllers use a stripe-size, while the Linux kernel uses a chunk-size.

Home:
- Quit messing around with the Ansible playbook, and just set up a new server
  Done.
- Go to bed not late

Mostly up and running on the Vultr VM.
Not too traumatic.

Breakfast: bagel, coffee
Lunch: Thai noodles, coffee
Dinner: