1. 14 Mar, 2015 3 commits
  2. 13 Mar, 2015 1 commit
    • Mike Hibler's avatar
      MFS fixups. · e12934a2
      Mike Hibler authored
      Make sure we clear out any partial GPTs. On FreeBSD we just use
      "gpart destroy" which will get rid of an MBR or GPT.
      Tee the output of rc.frisbee into a file and upload that back to
      boss in the event of a failure. We will see if this proves useful.
  3. 10 Mar, 2015 1 commit
  4. 06 Mar, 2015 4 commits
  5. 05 Mar, 2015 4 commits
    • Mike Hibler's avatar
      Revamp Xen vnode code to take advantage of "Xen mode" in capture. · 7a59bc05
      Mike Hibler authored
      A per-domain capture process is now started up in vnodeCreate and
      shutdown in vnodeDestroy. It should remain running for the entire time
      in between (across reboots, etc.)
      This should help ensure that you don't ever miss your favorite console
      output, even the thrilling early-stage boot messages!
    • Mike Hibler's avatar
      Add "Xen mode" in capture. · c32c2d42
      Mike Hibler authored
      With "-X <domname>" capture will track what pty is being exposed by
      xenconsoled for a domU console. Capture will doggedly reconnect whenever
      it gets disconnected from the pty (which happens during reboots, etc.)
      Capture can even be started before the domain exists and it will keep
      trying til it does. So betware of typo-ing the domain name, capture won't
      Also added "-R <retry-interval-in-ms>" option to determine capture's
      "doggedness"--how often it will retry to establish a connection in the
      remote/program/xen modes.
    • Leigh B Stoller's avatar
      Checkpoint image backed dataset work. · e94a7950
      Leigh B Stoller authored
    • Leigh B Stoller's avatar
      Minor regex bug fix. · ac167a1e
      Leigh B Stoller authored
  6. 04 Mar, 2015 3 commits
  7. 03 Mar, 2015 5 commits
  8. 25 Feb, 2015 2 commits
  9. 24 Feb, 2015 3 commits
  10. 23 Feb, 2015 1 commit
  11. 20 Feb, 2015 2 commits
  12. 19 Feb, 2015 7 commits
  13. 17 Feb, 2015 1 commit
    • Mike Hibler's avatar
      Major overhaul to support thin snapshot volumes and also fixup locking. · a9e75f33
      Mike Hibler authored
      A "thin volume" is one in which storage allocation is done on demand; i.e.,
      space is not pre-allocated, hence the "thin" part. If thin snapshots and
      the associated base volume are all part of a "thin pool", then all snapshots
      and the base share blocks from that pool. If there are N snapshots of the
      base, and none have written a particular block, then there is only one copy
      of that block in the pool that everyone shares.
      Anyway, we now create a global thin pool in which the thin snapshots can be
      created. We currently allocate up to 75% of the available space in the VG
      to the pool (note: space allocated to the thin pool IS statically allocated).
      The other 25% is for Things That Will Not Be Shared and as fallback in case
      something on the thin volume path fails. That is, we can disable thin
      volume creation and go back to the standard path.
      Images are still downloaded and saved in compressed form in individual
      LVs. These LVs are not allocated from the pool since they are TTWNBS.
      When the first vnode comes along that needs an image, we imageunzip the
      compressed version to create a "golden disk" LV in the pool. That first
      node and all subsequent nodes get thin snapshots of that volume.
      When the last vnode that uses a golden disk goes away we...well,
      do nothing. Unless $REAP_GDS (linux/xen/libvnode_xen.pm) is set non-zero,
      in which case we reap the golden disk. We always leave the compressed
      image LV around. Leigh says he is going to write a daemon to GC all these
      things when we start to run short of VG space...
      This speed up for creation of vnodes that shared an image turned up some
      more rack conditions, particularly around iptables. I close a couple more
      holes (in particular, ensuring that we lock iptables when setting up
      enet interfaces as we do for the cnet interface) and added some optional
      lock debug logging (turned off right now).
      Timestamped those messages and a variety of other important messages
      so that we could merge (important parts of) the assorted logfiles and
      get a sequential picture of what happened:
          grep TIMESTAMP *.log | sort +2
      (Think of it as Weir lite!)
  14. 10 Feb, 2015 1 commit
  15. 03 Feb, 2015 1 commit
  16. 02 Feb, 2015 1 commit