1. 17 Nov, 2016 1 commit
  2. 15 Nov, 2016 3 commits
  3. 14 Nov, 2016 7 commits
    • Mike Hibler's avatar
      Allow building of zapdisk without the disk erase feature. · 8e66ee84
      Mike Hibler authored
      Needed this for building zapdisk for a really old FreeBSD (6.3).
      8e66ee84
    • Mike Hibler's avatar
      Ignore state transitions from NORMALv2/ISUP -> BOOTING. · 990fcc0b
      Mike Hibler authored
      In the !BOOTINFO_EVENTS world, someone making a random DHCP request would
      cause a state transition to BOOTING which would start a timeout ticking and
      most likely would timeout in a couple of minutes and reboot the node.
      990fcc0b
    • Mike Hibler's avatar
      Fix obscure error with (not) invalidating disks during reload. · 4925a276
      Mike Hibler authored
      Our MBR/superblock/LVM/ZFS smashing code in rc.frisbee relied on dmesg
      output to determine the local disks to call zapdisk on. However, the RE we
      used assumed well ordered output like:
      
        da0 at mpt0 bus 0 scbus0 target 0 lun 0
        da0: <ATA WDC WD5003ABYZ-0 1S03> Fixed Direct Access SPC-3 SCSI device
        da0: Serial Number      WD-WMAYP0DPNFLM
        da0: 300.000MB/s transfers
        da0: Command Queueing enabled
        da0: 476940MB (976773168 512 byte sectors)
      
      where we matched that last line. But due to the asynchronous nature of disk
      initialization, probably due to some soon-to-be-failing disks on the d710s,
      the last line was delayed and came out mashed-up with the da1 output:
      
        da1: <ATA WDC WD5003ABYX-1 1S02> Fixed Direct Access SPC-3 SCSI device
        da1: Serial Number      WD-WMAYP4939538
        da1: 300.000MB/s transfersda0: 476940MB (976773168 512 byte sectors)
      
      so we didn't see da0 and didn't call zapdisk on it. This led to some LVM
      metadata on /dev/sda4 leaking through to a new experiment and if that experiment
      tried to setup LVM (e.g., a vnode host), it would blow up.
      
      Now we use a sysctl call (kern.disks) to get the disk names.
      4925a276
    • David Johnson's avatar
    • Jonathon Duerig's avatar
    • Jonathon Duerig's avatar
      All portals hosted from the main site should use the 'emulab.net' domain when... · 3d66b3f4
      Jonathon Duerig authored
      All portals hosted from the main site should use the 'emulab.net' domain when displaying URNs for images.
      3d66b3f4
    • Mike Hibler's avatar
      Tweaks to the agreement between mkextrafs and the blockstore system. · 939b0ae7
      Mike Hibler authored
      For the case in which mkextrafs is used to create local homedirs/projdirs:
      
      Look for the desired mount point (/local) in /etc/fstab and use that if
      it exists (i.e., that FS was already setup by the blockstore system or a
      previous mkextrafs).
      
      Otherwise, look for /var/emulab/boot/extrafs which should contain info
      left behind by the local blockstore setup code indicating a FS or unused
      device to use. For an unused device, rc.storage will identify the largest
      available device that is at least 10MB.
      939b0ae7
  4. 13 Nov, 2016 1 commit
  5. 12 Nov, 2016 5 commits
  6. 11 Nov, 2016 6 commits
  7. 10 Nov, 2016 4 commits
  8. 09 Nov, 2016 3 commits
  9. 08 Nov, 2016 4 commits
  10. 07 Nov, 2016 6 commits