GitLab

Otherwise it will fail and we will think we don't have a GPT when we
really do. Some unnamed 56-year-old screwed that up!

There seem to be some issues when booting lots of Moonshots.

ntp tries to create a temporary file in the same dir when updating,
and that doesn't work with /etc.

We tried this 14 or so years ago and it didn't work on FreeBSD 4.7.
But this does work on Linux at least.

add for VMs, but we were never deleting them and after a while
sshd refuses to start.

Do not remove iscsi startup files in the guest on XEN44.

We pass through a flag in the tmcd loadinfo call to tell whether to attempt
to do a TRIM when loading the disk (or after loading the disk). If TRIM=1
then we do so.

Since it is not clear from what I have read whether repeated TRIMming is
a detriment to SSD life, we throttle it as follows:

1. We don't TRIM at all unless the sitevariable general/bootdisk_trim_interval
   is non zero. If it is set, we will wait at least that many seconds after
   the previous TRIM before we do it again.

2. We keep track of the last trim via the node_attribute "bootdisk_lasttrim"
   which is a unix timestamp of the last time that tmcd responded to a
   loadinfo request in which it returned TRIM=1.

2. We track, on a per-node basis, whether the boot disk should be TRIMmed
   or not. If the node or node-type attribute "bootdisk_trim" is non-zero,
   we will attempt a trim if the interval has passed since the last trim.

So, we never trim if the sitevariable is 0 (the default value). If it is
non-zero, we only trim the boot disk of those nodes that have the node or
node_type attribute set and only after a sufficient interval has passed.

This does not address non-boot disks, but currently frisbee won't mess
with any other disk anyway. Eventually, we will have to have per-disk or
per-disktype attributes if we want to do this better.

Also add utility function to allow the node to get the exact details of
the image it is running ('imageinfo').

Some of the taint checks are rather heavy-handed presently.  Pretty much
any vector that could be used by the user to do something as root has
been severed right at the top of the relevant tmcd calls.

Calls affected:

manifest ('blackbox' and 'useronly' taintstates)
rpms ('blackbox' and 'useronly' taintstates)
tarballs ('blackbox' and 'useronly' taintstates)
blobs ('blackbox' and 'useronly' taintstates)
startupcmd ('blackbox' taintstate)
mounts ('blackbox' taintstate)
programs ('blackbox' taintstate)

Taint handling for the 'accounts' call was dealt with in a prior commit.

Just in case the default route is via a VLAN device.

I was attempting to read back any last words the program might have
uttered, but if it said nothing, we would hang. I would not have
expected this behavior from a pipe (actually, socketpair) when the
other end has gone away! But, make it non blocking before we read
to be safe.

When locating the root device, if a BSD disk partition fills the entire
DOS partition, then Linux will not create a separate /dev entry for it.
In that case, we use the DOS partition device.

Also, a couple of changes to resync with BSD slicefix.

If an available partition device (aka, the 4th partition on the system disk)
represents less than 5% of the spare space we have found, ignore it.

This will allow us to continue to use the 4th partition on the system
disk of the d710s (450GB or so) and the second disk (250GB), but not use
the 2nd partition (3GB), which would make us thrash about on the system
disk even more than usual.

Mostly this is for the new HP server boxes, so it doesn't pick up the 10GB
left over on the (virtual) system disk when we have 21TB available on the
second (virtual) disk.

Another hack til blockstores rule the world...

Also loads a couple of Infiniband modules so that Infiniband tools work
properly.

pretty up the output when not in reporting mode

check for corner case where there are no HD SNs to be found

clean up output
From testing on boss.emulab: set bsidx_bass=1000 to fill gaps in database
  found and handle case where "ERROR DISK OUT OF ORDER" when SN=UNKNOWN