pmem Tools version 1.3

The PMDK repository on GitHub is the ultimate source of information on PMDK from release 2.0! For all questions and to submit eventual issues please follow to that repository. The PMDK documentation collected here should be valid up to the 1.13.1 release but is maintained only on a best-effort basis and may not reflect the latest state of the art.
  • LINUX
  • WINDOWS

comment: <> (SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT) comment: <> (LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,) comment: <> (DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY) comment: <> (THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT) comment: <> ((INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE) comment: <> (OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.)

NAME
SYNOPSIS
DESCRIPTION
EXAMPLES
SEE ALSO

NAME

pmempool-transform – Modify internal structure of a pool set.

SYNOPSIS

pmempool transform [options] <poolset_file_src> <poolset_file_dst>

DESCRIPTION

The pmempool transform command modifies internal structure of a pool set defined by the poolset_file_src file, according to a structure described in the poolset_file_dst file.

The following operations are supported:

  • adding replicas - one or more new replicas can be added and synchronized with other replicas in the pool set,

  • removing replicas - one or more replicas can be removed from the pool set,

  • reordering of replicas - the order of existing replicas can be changed.

Currently these operations are allowed only for pmemobj pools (see libpmemobj(3)).

The poolset_file_src argument provides the source pool set to be changed.

The poolset_file_dst argument points to the target pool set.

When adding or deleting replicas, the two pool set files can differ only in the definitions of replicas which are to be added or deleted. One cannot add and remove replicas in the same step. Only one of these operations can be performed at a time. Reordering replicas can be combined with any of them. Also, to add a replica it is necessary for its effective size to match or exceed the pool size. Otherwise the whole operation fails and no changes are applied. Effective size of a replica is the sum of sizes of all its part files decreased by 4096 bytes per each part file. The 4096 bytes of each part file is utilized for storing internal metadata of the pool part files.

Available options:
-d, --dry-run

Enable dry run mode. In this mode no changes are applied, only check for viability of the operation is performed.

-v, --verbose

Increase verbosity level.

-h, --help

Display help message and exit.

EXAMPLES

Example 1.

Let files /path/poolset_file_src and /path/poolset_file_dst have the following contents:

PMEMPOOLSET
20M /0/partfile1
20M /0/partfile2
25M /0/partfile3
REPLICA
40M /1/partfile1
20M /1/partfile2
PMEMPOOLSET
20M /0/partfile1
20M /0/partfile2
25M /0/partfile3
REPLICA
40M /1/partfile1
20M /1/partfile2
REPLICA
50M /2/partfile1
20M /2/partfile2

Then, the command

pmempool transform /path/poolset_file_src /path/poolset_file_dst

adds a replica to the pool set. All other replicas remain unchanged and the size of the pool remains 60M.

Example 2.

Let files /path/poolset_file_src and /path/poolset_file_dst have the following contents:

PMEMPOOLSET
20M /0/partfile1
20M /0/partfile2
25M /0/partfile3
REPLICA
40M /1/partfile1
20M /1/partfile2
PMEMPOOLSET
20M /0/partfile1
20M /0/partfile2
25M /0/partfile3

Then

pmempool_transform /path/poolset_file_src /path/poolset_file_dst

deletes the second replica from the pool set. The first replica remains unchanged and the size of the pool is still 60M.

SEE ALSO

libpmempool(3), libpmemblk(3), libpmemlog(3), pmempool(1)

The contents of this web site and the associated GitHub repositories are BSD-licensed open source.