.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "JOURNAL_ABORT" "" "06 October 2005" "" ""

.SH NAME
journal_abort \- Shutdown the journal immediately.
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void journal_abort  (journal_t * \fIjournal\fB, int \fIerrno\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIjournal\fB\fR
the journal to shutdown.
.TP
\fB\fIerrno\fB\fR
an error number to record in the journal indicating
the reason for the shutdown.
.SH "DESCRIPTION"
.PP
Perform a complete, immediate shutdown of the ENTIRE
journal (not of a single transaction).  This operation cannot be
undone without closing and reopening the journal.
.PP
The journal_abort function is intended to support higher level error
recovery mechanisms such as the ext2/ext3 remount-readonly error
mode.
.PP
Journal abort has very specific semantics.  Any existing dirty,
unjournaled buffers in the main filesystem will still be written to
disk by bdflush, but the journaling mechanism will be suspended
immediately and no further transaction commits will be honoured.
.PP
Any dirty, journaled buffers will be written back to disk without
hitting the journal.  Atomicity cannot be guaranteed on an aborted
filesystem, but we _do_ attempt to leave as much data as possible
behind for fsck to use for cleanup.
.PP
Any attempt to get a new transaction handle on a journal which is in
ABORT state will just result in an -EROFS error return.  A
journal_stop on an existing handle will return -EIO if we have
entered abort state during the update.
.PP
Recursive transactions are not disturbed by journal abort until the
final journal_stop, which will receive the -EIO error.
.PP
Finally, the journal_abort call allows the caller to supply an errno
which will be recorded (if possible) in the journal superblock.  This
allows a client to record failure conditions in the middle of a
transaction without having to complete the transaction to record the
failure to disk.  ext3_error, for example, now uses this
functionality.
.PP
Errors which originate from within the journaling layer will NOT
supply an errno; a null errno implies that absolutely no further
writes are done to the journal (unless there are any already in
progress).