Sophie

Sophie

distrib > CentOS > 6 > i386 > by-pkgid > 2c51d8eb79f8810ada971ee8c30ce1e5 > files > 1222

kernel-doc-2.6.32-71.14.1.el6.noarch.rpm

<?xml version="1.0" encoding="ANSI_X3.4-1968" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968" /><title>journal_abort</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /><link rel="home" href="index.html" title="Linux Filesystems API" /><link rel="up" href="ch05s03.html#journal_level" title="Journal Level" /><link rel="prev" href="re186.html" title="journal_wipe" /><link rel="next" href="re188.html" title="journal_errno" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"><span>journal_abort</span></th></tr><tr><td width="20%" align="left"><a accesskey="p" href="re186.html">Prev</a>&#160;</td><th width="60%" align="center">Journal Level</th><td width="20%" align="right">&#160;<a accesskey="n" href="re188.html">Next</a></td></tr></table><hr /></div><div class="refentry" title="journal_abort"><a id="API-journal-abort"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>journal_abort &#8212; 
     Shutdown the journal immediately.
 </p></div><div class="refsynopsisdiv" title="Synopsis"><h2>Synopsis</h2><div class="funcsynopsis"><table border="0" summary="Function synopsis" cellspacing="0" cellpadding="0" class="funcprototype-table"><tr><td><code class="funcdef">void <b class="fsfunc">journal_abort </b>(</code></td><td>journal_t * <var class="pdparam">journal</var>, </td></tr><tr><td>&#160;</td><td>int <var class="pdparam">errno</var><code>)</code>;</td></tr></table><div class="funcprototype-spacer">&#160;</div></div></div><div class="refsect1" title="Arguments"><a id="id3127462"></a><h2>Arguments</h2><div class="variablelist"><dl><dt><span class="term"><em class="parameter"><code>journal</code></em></span></dt><dd><p>
     the journal to shutdown.
    </p></dd><dt><span class="term"><em class="parameter"><code>errno</code></em></span></dt><dd><p>
     an error number to record in the journal indicating
     the reason for the shutdown.
    </p></dd></dl></div></div><div class="refsect1" title="Description"><a id="id3127507"></a><h2>Description</h2><p>
   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.
   </p><p>

   The journal_abort function is intended to support higher level error
   recovery mechanisms such as the ext2/ext3 remount-readonly error
   mode.
   </p><p>

   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.
   </p><p>

   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.
   </p><p>

   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.
   </p><p>

   Recursive transactions are not disturbed by journal abort until the
   final journal_stop, which will receive the -EIO error.
   </p><p>

   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.
   </p><p>

   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).
</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="re186.html">Prev</a>&#160;</td><td width="20%" align="center"><a accesskey="u" href="ch05s03.html#journal_level">Up</a></td><td width="40%" align="right">&#160;<a accesskey="n" href="re188.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"><span>journal_wipe</span>&#160;</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">&#160;<span>journal_errno</span></td></tr></table></div></body></html>