1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>gfjournaladmin</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" title="gfjournaladmin">
<a name="gfjournaladmin.1"></a><div class="titlepage"></div>
<div class="refnamediv">
<a name="name"></a><h2>Name</h2>
<p>gfjournaladmin — erase a particular record in a journal file</p>
</div>
<div class="refsynopsisdiv" title="Synopsis">
<a name="synopsis"></a><h2>Synopsis</h2>
<div class="cmdsynopsis"><p><code class="command">gfjournaladmin</code> [<em class="replaceable"><code>options</code></em>] <em class="replaceable"><code>journal-file</code></em> <em class="replaceable"><code>sequence-number</code></em> </p></div>
</div>
<div class="refsect1" title="DESCRIPTION">
<a name="description"></a><h2>DESCRIPTION</h2>
<p>
<span class="command"><strong>gfjournaladmin</strong></span> erases a record with
<em class="replaceable"><code>sequence-number</code></em> in a journal file.
Since the record is replaced by A NOP (no operation) record with the
same length, other records in the journal file are not moved or modified.
</p>
<p>
When gfmd detects a conflict of metadata, it reports a log message like
as the following and aborts immediately.
</p>
<div class="literallayout"><p><br>
db_journal_store_thread : seqnum=938 ope=FILECOPY_ADD : \<br>
already exists<br>
</p></div>
<p>
Such a conflict should not happen, but once it has been caused by a bug
of gfmd, restarting gfmd never succeeds.
Since gfmd applies journal data at boot time, it finds the conflict
and aborts again.
<span class="command"><strong>gfjournaladmin</strong></span> command is used for getting out from
the situation. The log message shown above suggests a record with the
sequence number 938 causes a conflict.
You can delete the record by executing:
</p>
<div class="literallayout"><p><br>
gfjournaladmin /var/gfarm-metadata/journal/0000000000.gmj 938<br>
</p></div>
<p>
Note that <span class="command"><strong>gfjournaladmin</strong></span> cannot erase a journal
record of BEGIN (operation ID 1) or END (operation ID 2).
</p>
</div>
<div class="refsect1" title="OPTIONS">
<a name="options"></a><h2>OPTIONS</h2>
<div class="variablelist"><dl>
<dt><span class="term"><code class="option">-h</code></span></dt>
<dd><p>Displays a list of command options.</p></dd>
<dt><span class="term"><code class="option">-?</code></span></dt>
<dd><p>Equivalent to <code class="option">-h</code>.</p></dd>
<dt><span class="term"><code class="option">-n</code></span></dt>
<dd><p>
Read a journal file, but do not write actually.
</p></dd>
<dt><span class="term"><code class="option">-v</code></span></dt>
<dd><p>
Prints verbose messages.
</p></dd>
</dl></div>
</div>
</div></body>
</html>
|
