1. 16 Dec, 2014 1 commit
  2. 02 Dec, 2014 3 commits
  3. 14 Nov, 2014 1 commit
  4. 10 Nov, 2014 1 commit
    • Mike Hibler's avatar
      Fix Linux MFS issue. · 254d0d6d
      Mike Hibler authored
      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.
      254d0d6d
  5. 07 Nov, 2014 2 commits
    • Mike Hibler's avatar
      The latest in logic to have findSpareDisks not use the system disk. · 2eab9b24
      Mike Hibler authored
      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...
      2eab9b24
    • Mike Hibler's avatar
      Fix for CentOS. Liberalize an RE. · 2472e72a
      Mike Hibler authored
      2472e72a
  6. 09 Oct, 2014 1 commit
    • Mike Hibler's avatar
      Rework client-side storage scripts to semi-coexist with mkextrafs uses. · 9cf8f9c6
      Mike Hibler authored
      Broke rc.storage into two phases, local blockstores and remote blockstores.
      Setup of the former will also pick a best candidate for an old-school
      "extrafs" and put the info in /var/emulab/boot/extrafs. This will be a
      single line with one of DISK=foo, PART=foo, or FS=foo depending on whether
      it found an available full disk, disk partition, or mounted filesystem
      that we can use for mkextrafs (in the first two cases) or where we can
      mooch off of (the last). This is only used in os_mountextrafs() right now;
      i.e., I have NOT changed the mkextrafs script. So explicit invocations
      by the user could still screw things up.
      
      I have tested this with local blockstores and a non-nfs experiment
      on both Linux and FreeBSD to make sure the most common sharing of space
      works. I have not made any new images and I have not yet tested to make
      sure I did not break non-blockstore, non-nfs experiments (i.e., where
      we really should run mkextrafs).
      
      So maybe don't make any new images til I get back, or else be prepared
      to clean up after me.
      9cf8f9c6
  7. 02 Oct, 2014 1 commit
  8. 29 Sep, 2014 1 commit
    • Mike Hibler's avatar
      Improve findSpareDisks a bit: · dc93ff42
      Mike Hibler authored
       * handle devices like /dev/cciss/c0d0 and /dev/cciss/c0d0p1,
       * ignore srN and dm-N files,
       * ignore partitions/drives that are in an LVM PV.
      dc93ff42
  9. 22 Sep, 2014 1 commit
  10. 14 Aug, 2014 1 commit
  11. 06 Aug, 2014 1 commit
  12. 31 Jul, 2014 1 commit
  13. 28 Jul, 2014 2 commits
  14. 25 Jul, 2014 5 commits
  15. 20 Jun, 2014 1 commit
  16. 12 Jun, 2014 1 commit
  17. 30 May, 2014 3 commits
  18. 26 May, 2014 1 commit
  19. 21 May, 2014 2 commits
  20. 19 May, 2014 2 commits
  21. 16 May, 2014 1 commit
    • Mike Hibler's avatar
      Add a variable to control what space is included in the xen_vg VG. · 2fbfc5dd
      Mike Hibler authored
      Setting LVM_FULLDISKONLY will effectively tell it to not use extra
      space on the system disk when constructing the VG used for vnode disk
      creation. This can affect performace for everybody, especially if it
      uses multiple little partitions on the system disk. However, this is
      turned off by default since, on our d710 nodes, most of the extra
      space is on the system disk. Setting this should be plumbed through
      to the user somehow so they can choose.
      2fbfc5dd
  22. 09 May, 2014 4 commits
  23. 08 May, 2014 1 commit
    • Mike Hibler's avatar
      Support for MBR v3 images in Xen VMs. · ef69e78a
      Mike Hibler authored
      If the Xen dom0 base image is properly (1M) aligned and the VM images
      are properly aligned as well, we should avoid or at least minimize any
      anomolous effects due to mismatches along the path involving the guest OS,
      guest disk layout, LVM LVs, LVM PVs, and the underlying physical disks.
      
      Also, random change to add a min size parameter to the findSpareDisks
      function. I was going to use this to avoid sucking up the little 3GB
      unused partition in MBR 3, but then decided against it.
      ef69e78a
  24. 07 May, 2014 1 commit
    • Mike Hibler's avatar
      Prepare for the coming of MBR version 3. · b4fdf8e0
      Mike Hibler authored
      Ironic. After all that hoo-haw about dynamically-created MBRs in the
      previous commit, we introduce a new hardcoded static MBR...
      
      Goals:
       * Single OS partition, in the fast area of rotating disks
       * Proper alignment for 4k sector drives and SSDs (1MB alignment)
       * Still works on 40GB disk (aka, pc850s)
       * P1 16 GiB: goldilocks FS: not too small (> 10GB), but not too big (< 30GB)
       * P2  3 GiB: can hold a co-loaded MBR 1 image (e.g., FBSD410 delay node OS)
       * P3  3 GiB: at least as much swap at currently (>= 1GB)
      
      The partition table:
        P1:     2048	33554432	FS, 16GiB
        P2: 33556480	 6291456	possible delay-node OS or additional swap, 3GiB
        P3: 39847936	 6291456	swap, 3GiB
        P4: 46139392	34278848+	extrafs, 16+GB
      
      The larger size and partition alignment are why I pushed this through despite
      my noble intentions.
      b4fdf8e0
  25. 01 May, 2014 1 commit