Skip to content
Commits on Mar 8, 2015
  1. Avoid truncating image files

    committed
    Thanks to inejge for reporting, and the patch.
Commits on Feb 24, 2015
  1. Fix gemspec for Ruby 2.x

    committed
  2. Now with debugging!

    committed
    In addition to refactoring the output formatting in general, there's now a
    separate --debug option that will provide you with even *more* obsessive
    detail about what's going on.
  3. @sjbronner
Commits on Oct 14, 2014
  1. Merge pull request #38 from nickjwebb/patch-1

    committed
    Update README.md
  2. @nickjwebb

    Update README.md

    nickjwebb committed
    Minor changes to improve readability and understanding.
  3. Merge remote-tracking branch 'deriamis/sshkey'

    committed
    Conflicts:
    	bin/lvmsync
  4. Add a new option, --data-source [Fixes GH#10, GH#17]

    committed
    Specify a different block device to read from.  Not something I'd be
    inclined to use myself, but when two people take the time to submit PRs for
    the same issue, clearly there's demand for it.
  5. Add a --quiet option

    committed
    For when you really would prefer not to know much of anything.
  6. Improve the handling of stdout/stderr from the remote

    committed
    This should help with OpenSSH ControlMaster (a la GH#37), but it'll be of
    benefit to everyone, I think, as the control code is cleaner now.
Commits on Oct 12, 2014
Commits on Oct 11, 2014
  1. Be more verbose

    committed
    Pass -v to the receiving lvmsync, and immediately print any output
    from the receiver, too.
  2. Accurately report when the lvmsync receiver fails

    committed
    This work was most cleanly achieved by refactoring out a lot of "behind the
    scenes" logic that should be buried inside a "LogicalVolume" class, so I
    made one, and used that.  Overall, I think it's a definite net win.
Commits on Oct 10, 2014
  1. Quiet tests right the hell down

    committed
    I want to see the tests passed, not that an LV was created.
Commits on Oct 6, 2014
  1. Correct byte-order on LVM metadata reads [Fixes GH#31]

    committed
    Somehow I managed to completely confuse myself as to the LVM metadata
    format, and it was only the bug in htonq/ntohq (GH#6) that I fixed recently
    that had made it work all this time.  Once I fixed that bug, this one
    appeared.
    
    Thanks to UnwashedMeme for the detective work, and pointing me in the right
    direction.
Commits on Oct 3, 2014
Commits on Sep 12, 2014
  1. @deriamis
  2. @deriamis
Commits on Sep 3, 2014
  1. Fix the block maps for data ranges

    Steven McDonald committed with
    The existing code uses the underlying data blocks as keys, and the
    origin blocks as values, which is backwards. This is done correctly
    above for the single mapping case, so this bug only affects range
    mappings.
  2. Fix up test suite

    committed
Commits on Sep 1, 2014
Commits on Aug 31, 2014
  1. Stylistic fix

    committed
  2. Merge pull request #26 from Informatic/master

    committed
    Fix missing handshake in snapback files
  3. Merge branch 'popen3-ruby1.9-fix' of git://github.com/AnchorCat/lvmsync

    committed
    Conflicts:
    	lib/lvm/vg_config.rb
    
    (MP: A much better fix for the 1.8 incompatibilities I hacked around in
    bf42ee8)
    #
    # It looks like you may be committing a merge.
    # If this is not correct, please remove the file
    #	.git/MERGE_HEAD
    # and try again.
    
    # Please enter the commit message for your changes. Lines starting
    # with '#' will be ignored, and an empty message aborts the commit.
    # On branch master
    # Your branch is up-to-date with 'github/master'.
    #
    # All conflicts fixed but you are still merging.
    #
    # Changes to be committed:
    #	modified:   lib/lvm/vg_config.rb
    #
  4. Merge pull request #14 from AnchorCat/bump-lvmsync-protocol

    committed
    Bump lvmsync protocol version and update receiver
  5. Merge pull request #28 from deriamis/vgcfgbackup

    committed
    Variables vary even more than you might think...
Something went wrong with that request. Please try again.