1. 24 Mar, 2005 1 commit
  2. 23 Mar, 2005 5 commits
  3. 22 Mar, 2005 10 commits
  4. 21 Mar, 2005 7 commits
  5. 20 Mar, 2005 2 commits
  6. 19 Mar, 2005 2 commits
  7. 18 Mar, 2005 8 commits
  8. 17 Mar, 2005 3 commits
    • Mike Hibler's avatar
      Quicky attempt to get NTFS support working under Linux. · beb269a5
      Mike Hibler authored
      Untested, but compiles!
      beb269a5
    • Mike Hibler's avatar
      Yeah, I'm a dork. · 9de8411a
      Mike Hibler authored
      Put back the changes I removed in my last commit.
      You would think I would know how to read diff output by now...
      9de8411a
    • Mike Hibler's avatar
      Partial support for disk-zeroing on experiment termination. · 60e7adb8
      Mike Hibler authored
      I did the "back half" support.  If the 'mustwipe' field is non-zero
      in the reserved table entry for a node then its disk must be zeroed.
      How the zeroing is done, depends on the value of the mustwipe field.
      Right now, '1' means pass the '-z' option to frisbee to have it zero
      all non-allocated blocks.  The value '2' is reserved for enabling a
      "full wipe" pass of the disk before running frisbee, which Keith Sklower
      (DETER) wanted to be able to do.  Note that 1 and 2 are effectively the
      same, if we are loading a full-disk image; i.e. all non-allocated blocks
      from the new image are zeroed.  But if the disk were being loaded with
      a single-partition image, then "frisbee -z" would only wipe unused
      blocks in that partition.
      
      The reload_daemon has been modified to extract the mustwipe info and
      invoke os_load accordingly.   os_load now takes a "-z <type>" option
      to enable the zeroing by setting a value in the current_reloads table.
      tmcd will read and return that info to its caller in the "loadinfo" command.
      Finally, the rc.frisbee script that runs in the frisbee MFS extracts the
      loadinfo info and crafts the frisbee startup command.
      
      What still needs to be done is the "front end," how the user specifies
      the value and how it winds up in the DB reserved table.  This will probably
      involve addition of state to the experiments table as this will likely be
      a per-experiment setting.
      60e7adb8
  9. 16 Mar, 2005 2 commits
    • Timothy Stack's avatar
      ea6e552a
    • Mike Hibler's avatar
      Really important stuff: · a8ef625f
      Mike Hibler authored
      Unified the 'dot' handling (status printing) of frisbee and imagezip.
      They now both report the number of chunks remaining along with the dots.
      Also put out a periodic splat for every GB of uncompressed data we write.
      This is useful when you are zero-filling, since otherwise it appears that
      frisbee has hung when it is really just zeroing the last unused 100GB of
      your disk.
      a8ef625f