'\" t
.\"     Title: gfjournaladmin
.\"    Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
.\"      Date: 21 Jun 2012
.\"    Manual: Gfarm
.\"    Source: Gfarm
.\"  Language: English
.\"
.TH "GFJOURNALADMIN" "1" "21 Jun 2012" "Gfarm" "Gfarm"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
gfjournaladmin \- erase a particular record in a journal file
.SH "SYNOPSIS"
.HP \w'\fBgfjournaladmin\fR\ 'u
\fBgfjournaladmin\fR [\fIoptions\fR] \fIjournal\-file\fR \fIsequence\-number\fR
.SH "DESCRIPTION"
.PP
\fBgfjournaladmin\fR
erases a record with
\fIsequence\-number\fR
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\&.
.PP
When gfmd detects a conflict of metadata, it reports a log message like as the following and aborts immediately\&.
.sp
.if n \{\
.RS 4
.\}
.nf
	db_journal_store_thread : seqnum=938 ope=FILECOPY_ADD : \e
	    already exists
.fi
.if n \{\
.RE
.\}
.PP
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\&.
\fBgfjournaladmin\fR
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:
.sp
.if n \{\
.RS 4
.\}
.nf
	gfjournaladmin /var/gfarm\-metadata/journal/0000000000\&.gmj 938
.fi
.if n \{\
.RE
.\}
.PP
Note that
\fBgfjournaladmin\fR
cannot erase a journal record of BEGIN (operation ID 1) or END (operation ID 2)\&.
.SH "OPTIONS"
.PP
\fB\-h\fR
.RS 4
Displays a list of command options\&.
.RE
.PP
\fB\-?\fR
.RS 4
Equivalent to
\fB\-h\fR\&.
.RE
.PP
\fB\-n\fR
.RS 4
Read a journal file, but do not write actually\&.
.RE
.PP
\fB\-v\fR
.RS 4
Prints verbose messages\&.
.RE