Server : Apache/2.4.41 (Ubuntu) System : Linux absol.cf 5.4.0-198-generic #218-Ubuntu SMP Fri Sep 27 20:18:53 UTC 2024 x86_64 User : www-data ( 33) PHP Version : 7.4.33 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, Directory : /usr/share/doc/reiserfsprogs/html/
Upload File :
Current File : //usr/share/doc/reiserfsprogs/html/reiserfsck.html
<html>
<head>
<meta name="generator" content="groff -Thtml, see www.gnu.org">
<meta name="Content-Style" content="text/css">
<title>REISERFSCK</title>
</head>
<body>
<h1 align=center>REISERFSCK</h1>
<a href="#NAME">NAME</a><br>
<a href="#SYNOPSIS">SYNOPSIS</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#OPTIONS">OPTIONS</a><br>
<a href="#EXPERT OPTIONS">EXPERT OPTIONS</a><br>
<a href="#AN EXAMPLE OF USING reiserfsck">AN EXAMPLE OF USING reiserfsck</a><br>
<a href="#EXIT CODES">EXIT CODES</a><br>
<a href="#AUTHOR">AUTHOR</a><br>
<a href="#BUGS">BUGS</a><br>
<a href="#TODO">TODO</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>
<hr>
<!-- Creator : groff version 1.17.2 -->
<!-- CreationDate: Thu May 13 21:46:08 2004 -->
<a name="NAME"></a>
<h2>NAME</h2>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
reiserfsck - The checking tool for the ReiserFS filesystem.</td></table>
<a name="SYNOPSIS"></a>
<h2>SYNOPSIS</h2>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>reiserfsck</b> [ <b>-afprVy</b> ] [ <b>--rebuild-sb</b> |
<b>--check</b> | <b>--fix-fixable</b> |
<b>--rebuild-tree</b> | <b>--clean-attributes</b> ] [
<b>-j</b> | <b>--journal</b> <i>device</i> ] [ <b>-z</b> |
<b>--adjust-size</b> ] [ <b>-n</b> | <b>--nolog</b> ] [
<b>-B</b> | <b>--badblocks</b> <i>file</i> ] [ <b>-l</b> |
<b>--logfile</b> <i>file</i> ] [ <b>-q</b> | <b>--quiet</b>
] [ <b>-y</b> | <b>--yes</b> ] [ <b>-S</b> |
<b>--scan-whole-partition</b> ] [
<b>--no-journal-available</b> ] <i>device</i></td></table>
<a name="DESCRIPTION"></a>
<h2>DESCRIPTION</h2>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>Reiserfsck</b> searches for a Reiserfs filesystem on a
device, replays any necessary transactions, and either
checks or repairs the file system.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<i>device</i></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
is the special file corresponding to a device or to a
partition (e.g /dev/hdXX for an IDE disk partition or
/dev/sdXX for a SCSI disk partition).</td></table>
<a name="OPTIONS"></a>
<h2>OPTIONS</h2>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>--rebuild-sb</b></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
This option recovers the superblock on a Reiserfs partition.
Normally you only need this option if mount reports
"read_super_block: can't find a reiserfs file
system" and you are sure that a Reiserfs file system is
there. But remember that if you have used some partition
editor program and now you cannot find a filesystem,
probably something has gone wrong while repartitioning and
the start of the partition has been changed. If so, instead
of rebuilding the super block on a wrong place you should
find the correct start of the partition first.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>--check</b></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
This default action checks filesystem consistency and
reports, but does not repair any corruption that it finds.
This option may be used on a read-only file system
mount.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>--fix-fixable</b></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
This option recovers certain kinds of corruption that do not
require rebuilding the entire file system tree
(<b>--rebuild-tree</b>). Normally you only need this option
if the <b>--check</b> option reports "corruption that
can be fixed with <b>--fix-fixable</b>". This includes:
zeroing invalid data-block pointers, correcting st_size and
st_blocks for directories, and deleting invalid directory
entries.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>--rebuild-tree</b></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
This option rebuilds the entire filesystem tree using leaf
nodes found on the device. Normally you only need this
option if the <b>reiserfsck --check</b> reports
"Running with <b>--rebuild-tree</b> is required".
You are strongly encouraged to make a backup copy of the
whole partition before attempting the <b>--rebuild-tree</b>
option. Once <b>reiserfsck --rebuild-tree</b> is started it
must finish its work (and you should not interrupt it),
otherwise the filesystem will be left in the unmountable
state to avoid subsequent data corruptions.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>--clean-attributes</b></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
This option cleans reserved fields of Stat-Data items. There
were days when there were no extended attributes in
reiserfs. When they were implemented old partitions needed
to be cleaned first -- reiserfs code in the kernel did not
care about not used fields in its strutures. Thus if you
have used one of the old (pre-attrbutes) kernels with a
ReiserFS filesystem and you want to use extented attribues
there, you should clean the filesystem first.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>--journal</b> <i>device</i> , <b>-j</b>
<i>device</i></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
This option supplies the device name of the current file
system journal. This option is required when the journal
resides on a separate device from the main data device
(although it can be avoided with the expert option
<b>--no-journal-available</b>).</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>--adjust-size, -z</b></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
This option causes <b>reiserfsck</b> to correct file sizes
that are larger than the offset of the last discovered byte.
This implies that holes at the end of a file will be
removed. File sizes that are smaller than the offset of the
last discovered byte are corrected by
<b>--fix-fixable</b>.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>--badblocks</b> <i>file</i>, <b>-B</b>
<i>file</i></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
This option sets the badblock list to be the list of blocks
specified in the given `file`. The filesystem badblock list
is cleared before the new list is added. It can be used with
<b>--fix-fixable</b> to fix the list of badblocks (see
<b>debugreiserfs -B</b>). If the device has bad blocks,
every time it must be given with the <b>--rebuild-tree</b>
option.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>--logfile</b> <i>file</i>, <b>-l</b>
<i>file</i></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
This option causes <b>reiserfsck</b> to report any
corruption it finds to the specified log file rather than to
stderr.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>--nolog, -n</b></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
This option prevents <b>reiserfsck</b> from reporting any
kinds of corruption.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>--quiet, -q</b></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
This option prevents <b>reiserfsck</b> from reporting its
rate of progress.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>--yes, -y</b></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
This option inhibits <b>reiserfsck</b> from asking you for
confirmation after telling you what it is going to do. It
will assuem you confirm. For safety, it does not work with
the <b>--rebuild-tree</b> option.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>-a</b>, <b>-p</b></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
These options are usually passed by fsck -A during the
automatic checking of those partitions listed in /etc/fstab.
These options cause <b>reiserfsck</b> to print some
information about the specified filesystem, to check if
error flags in the superblock are set and to do some
light-weight checks. If these checks reveal a corruption or
the flag indicating a (possibly fixable) corruption is found
set in the superblock, then <b>reiserfsck</b> switches to
the fix-fixable mode. If the flag indicating a fatal
corruption is found set in the superblock, then
<b>reiserfsck</b> finishes with an error.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>-V</b></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
This option prints the reiserfsprogs version and then
exit.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>-r</b>, <b>-f</b></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
These options are not yet operational and therefore are
ignored.</td></table>
<a name="EXPERT OPTIONS"></a>
<h2>EXPERT OPTIONS</h2>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
DO NOT USE THESE OPTIONS UNLESS YOU KNOW WHAT YOU ARE DOING.
WE ARE NOT RESPONSIBLE IF YOU LOSE DATA AS A RESULT OF THESE
OPTIONS.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>--no-journal-available</b></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
This option allows <b>reiserfsck</b> to proceed when the
journal device is not available. This option has no effect
when the journal is located on the main data device. NOTE:
after this operation you must use <b>reiserfstune</b> to
specify a new journal device.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>--scan-whole-partition, -S</b></td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
This option causes <b>--rebuild-tree</b> to scan the whole
partition but not only the used space on the
partition.</td></table>
<a name="AN EXAMPLE OF USING reiserfsck"></a>
<h2>AN EXAMPLE OF USING reiserfsck</h2>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
1. You think something may be wrong with a reiserfs
partition on /dev/hda1 or you would just like to perform a
periodic disk check.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
2. Run <b>reiserfsck --check --logfile check.log
/dev/hda1</b>. If <b>reiserfsck --check</b> exits with
status 0 it means no errors were discovered.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
3. If <b>reiserfsck --check</b> exits with status 1 (and
reports about fixable corruptions) it means that you should
run <b>reiserfsck --fix-fixable --logfile fixable.log
/dev/hda1</b>.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
4. If <b>reiserfsck --check</b> exits with status 2 (and
reports about fatal corruptions) it means that you need to
run <b>reiserfsck --rebuild-tree</b>. If <b>reiserfsck
--check</b> fails in some way you should also run
<b>reiserfsck --rebuild-tree</b>, but we also encourage you
to submit this as a bug report.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
5. Before running <b>reiserfsck --rebuild-tree</b>, please
make a backup of the whole partition before proceeding. Then
run <b>reiserfsck --rebuild-tree --logfile rebuild.log
/dev/hda1</b>.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
6. If the <b>reiserfsck --rebuild-tree</b> step fails or
does not recover what you expected, please submit this as a
bug report. Try to provide as much information as possible
including your platform and Linux kernel version. We will
try to help solve the problem.</td></table>
<a name="EXIT CODES"></a>
<h2>EXIT CODES</h2>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>reiserfsck</b> uses the following exit codes:<i><br>
0</i> - No errors.<i><br>
1</i> - File system errors corrected.<i><br>
2</i> - Reboot is needed.<i><br>
4</i> - File system fatal errors left uncorrected,<b><br>
reiserfsck --rebuild-tree</b> needs to be launched.<i><br>
6</i> - File system fixable errors left uncorrected,<b><br>
reiserfsck --fix-fixable</b> needs to be launched.<i><br>
8</i> - Operational error.<i><br>
16</i> - Usage or syntax error.</td></table>
<a name="AUTHOR"></a>
<h2>AUTHOR</h2>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
This version of <b>reiserfsck</b> has been written by Vitaly
Fertman <vitaly@namesys.com>.</td></table>
<a name="BUGS"></a>
<h2>BUGS</h2>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
Please report bugs to the ReiserFS developers
<reiserfs-dev@namesys.com>, providing as much
information as possible--your hardware, kernel, patches,
settings, all printed messages, the logfile; check the
syslog file for any related information.</td></table>
<a name="TODO"></a>
<h2>TODO</h2>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
Faster recovering, signal handling.</td></table>
<a name="SEE ALSO"></a>
<h2>SEE ALSO</h2>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
<b>mkreiserfs</b>(8), <b>reiserfstune</b>(8)
<b>resize_reiserfs</b>(8),
<b>debugreiserfs</b>(8),</td></table>
<hr>
</body>
</html>
Server : Apache/2.4.41 (Ubuntu)