Added 'dry-run' mode in eblob_merge
examples: merge: add -d to getopt
examples: merge: do not truncate output files on dry run
examples: merge: fixed spelling, improved wording
blob: improved log message on lockf() failure
Merge pull request #43 from SaveTheRbtz/master

Merge and logging improvements
v0.21.15
codespell: committed->commited
examples: merge: allow missed -o if -d is specified
Merge pull request #44 from SaveTheRbtz/master

merge dry-run fixes
blob: skip size check on possibly zero-filled records

While investigating elliptics startup failure due to corrupted index
we've found following index entry:

0000000: 0000 0000 0000 0000 0000 0000 0000 0000  ................
0000010: 0000 0000 0000 0000 0000 0000 0000 0000  ................
0000020: 0000 0000 0000 0000 0000 0000 0000 0000  ................
0000030: 0000 0000 0000 0000 0000 0000 0000 0000  ................
0000040: 0000 0000 0000 0000 0000 0000 0000 0000  ................
0000050: 0000 0000 0000 0000 0000 0000 0000 0000  ................

It happens that some versions of eblob (possibly even current one) are
leaving zero-filled index entries. Those index entries are likely to be
produced by `kill -9`.

Let's just ignore them for now (logging advise to run eblob_merge on given
base) thus allowing iterator and index initialization to proceed.

Reported by: izhidkov@
blob: we shouldn't ignore index corruption on iteration

This will fix self-healing of eblob in presence of broken unsorted
index.
Merge pull request #45 from SaveTheRbtz/master

Corrupted blob handling bugfixes.
v0.21.16
data-sort: add time-scheduled data-sort

This will explicitly defines 3 data-sort modes:
* EBLOB_AUTO_DATASORT
Sort bases on start + as they are closed.
* EBLOB_TIMED_DATASORT
Sort bases each defrag_timeout seconds.
* EBLOB_SCHEDULED_DATASORT
Sort bases in random interval defrag_time +- defrag_splay.
Merge pull request #46 from SaveTheRbtz/devel

data-sort: add time-scheduled data-sort
v0.21.17
Simplify eblob_regex_iter
defrag: mark bctls for defrag based on number of records and size

In case when all bases are closed on blob_size limit and records_in_blob
is set way too high then blob may will try to defragment bases on each
defragmentation run.

As workaround one would probably want to lower records_in_blob to some
appropriate value.

Bug first appeared in v0.21.6
Merge pull request #47 from SaveTheRbtz/master

defrag: mark bctls for defrag based on number of records and size