Since the introduction of required parameters wasn't possible to show
the help message.
In fact the --help flag was checked after all other parameters.

Postpone the creation of the OpenFile object until we are sure that the
file actually exists and we have enough access rigths for it.

Problem:
In the case the path for which the check access is performed doesn't
exists the server will set `out.err` with the correct error number (ENOENT).
On client side the value of out.err is used as return value but the
errno variable is not set.

Assert is put after a more detailed error message is written to the log.

Previously, host rpc addresses have been looked up lazily when a request
was done. This is not necessary as all hosts are looked up anyways
while the file system is running.

Now, all RPC addresses are looked up when the environment is initialized.
After that, the rpc_address map is only accessed read-only and does not
require a mutex anymore.

Since POSIX.1-2001 the S_IFMT (0170000) bitmask of the file mode must
contain the file type.

At the moment we correctly support
 - [S_IFREG] regular file
 - [S_IFDIR] directory

Previously, clients would look for the daemon by name which was not robust.
If the daemon was started with valgrind for example, clients would not find
the daemon.

Similar to other applications a daemon now creates a pid file with
information about its pid and its started mountdir.

Proper errorhandling on server and client side was added.

Multiple daemons per node are explicitly not allowed for now!

Review and fixes that died when rebasing all commits

Nafi3 authored Mar 12, 2018 and Marc Vef committed Mar 23, 2018

This commit gives new options regarding separation of metadir and rootdir location. If only rootdir destination is given both metadata and data is stored at the same path

target was the index of the cycle and target[target] was the actual
identifier of the target. In some part of the code target was considered
as the identifier directly.

Now the index of the cycle is i and target is the actual identifier of
the target.

The calculus (on clients) about the last chunk involved into a
write/read operation was bugged.

A new blocks_calc_util library has been introduced in order to make
easier to perform this kind of calculus.

When rocksdb is build with jemalloc linking with adafs was failing

Instead use margo_iforward. Also only two bulk_handles are now used:
1 for margo_ipc and one for margo_rpc RPC requests.

The LRU map caused multiple issues with memory mappings and caused
severe errors and hanging situations. It has been replaced with a
std::map.

An Argobots mutex was added for rpc address lookups as many threads
might insert and lookup this map in parallel. This caused bulk_transfer
seqfauls as well as other file system crashes.

Cleanup of file system logging.

Before data was pulled first then written or read first and then pushed back

Only use 1 segment now but with multiple transfers

Use cmake in order to properly check and use both the Boost library and
the pthread one.

We need to be explicit about I/O as it cannot be simply repeated. A response
from the daemon will come eventually, either success or failure.

Previously, an ES was created for each destination in each read or write.
Creating and freeing these ES is costly. Also, these ESs had separate pools,
which is bad practice. Multiple ESs work on a single pool. The ABT_sched
decides which ULT or Tasklet is run by which ES at any time.

This change does also reduce CPU load as library IO RPC calls used CPU time
while waiting for the response.

daemon related cmake directives have been pushed into a standalon cmake
file into the src/daemon folder.