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 : /proc/thread-self/root/usr/share/doc/reiserfsprogs/html/
Upload File :
Current File : //proc/thread-self/root/usr/share/doc/reiserfsprogs/html/reiserfstune.html
<html>
<head>
<meta name="generator" content="groff -Thtml, see www.gnu.org">
<meta name="Content-Style" content="text/css">
<title>REISERFSTUNE</title>
</head>
<body>
<h1 align=center>REISERFSTUNE</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="#POSSIBLE SCENARIOS OF USING REISERFSTUNE:">POSSIBLE SCENARIOS OF USING REISERFSTUNE:</a><br>
<a href="#AUTHOR">AUTHOR</a><br>
<a href="#BUGS">BUGS</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>
<hr>
<!-- Creator : groff version 1.17.2 -->
<!-- CreationDate: Thu May 13 21:46:09 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%">
reiserfstune - The tuning 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>reiserfstune</b> [ <b>-f</b> ] [ <b>-j</b> |
<b>--journal-device</b> <i>FILE</i> ] [
<b>--no-journal-available</b> ] [
<b>--journal-new-device</b> <i>FILE</i> ] [
<b>--make-journal-standard</b> ] [ <b>-s</b> |
<b>--journal-new-size</b> <i>N</i> ] [ <b>-o</b> |
<b>--journal-new-offset</b> <i>N</i> ] [ <b>-t</b> |
<b>--trans-max-size</b> <i>N</i> ] [ <b>-b</b> |
<b>--add-badblocks</b> <i>file</i> ] [ <b>-B</b> |
<b>--badblocks</b> <i>file</i> ] [ <b>-u</b> | <b>--uuid</b>
<i>UUID</i> ] [ <b>-l</b> | <b>--label</b> <i>LABEL</i> ]
<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>reiserfstune</b> is used for tuning the ReiserFS. It can
change two journal parameters (the journal size and the
maximum transaction size), and it can move the journal's
location to a new specified block device. (The old
ReiserFS's journal may be kept unused, or discarded at the
user's option.) Besides that <b>reiserfstune</b> can store
the bad block list to the ReiserFS and set UUID and LABEL.
Note: At the time of writing the relocated journal was
implemented for a special release of ReiserFS, and was not
expected to be put into the mainstream kernel until
approximately Linux 2.5. This means that if you have the
stock kernel you must apply a special patch. Without this
patch the kernel will refuse to mount the newly modified
file system. We will charge $25 to explain this to you if
you ask us why it doesn't work.</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%">
Perhaps the most interesting application of this code is to
put the journal on a solid state disk.</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 the newly specified
block device (e.g /dev/hdXX for IDE disk partition or
/dev/sdXX for the 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>-j</b> | <b>--journal-device</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%">
<i>FILE</i> is the file name of the block device the file
system has the current journal (the one prior to running
reiserfstune) on. This option is required when the journal
is already on a separate device from the main data device
(although it can be avoided with
<b>--no-journal-available</b>). If you don't specify journal
device by this option, reiserfstune suppose that journal is
on main 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>--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%">
allows <b>reiserfstune</b> to continue when the current
journal's block device is no longer available. This might
happen if a disk goes bad and you remove it (and run
fsck).</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-new-device</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%">
<i>FILE</i> is the file name of the block device which will
contain the new journal for the file system. If you don't
specify this, reiserfstune supposes that journal device
remains the same.</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>-s</b> | <b>--journal-new-size</b> <i>N</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%">
<i>N</i> is the size parameter for the new journal. When
journal is to be on a separate device - its size defaults to
number of blocks that device has. When journal is to be on
the same device as the filesytem - its size defaults to
amount of blocks allocated for journal by <i>mkreiserfs</i>
when it created the filesystem. Minimum is 513 for both
cases.</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>-o</b> | <b>--journal-new-offset</b>
<i>N</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%">
<i>N</i> is an offset in blocks where journal will starts
from when journal is to be on a separate device. Default is
0. Has no effect when journal is to be on the same device as
the filesystem. Most users have no need to use this feature.
It can be used when you want the journals from multiple
filesystems to reside on the same device, and you don't want
to or cannot partition that 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>-t</b> | <b>--trans-max-size</b>
<i>N</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%">
<i>N</i> is the maximum transaction size parameter for the
new journal. The default, and max possible, value is 1024
blocks. It should be less than half the size of the journal.
If specifed incorrectly, it will be adjusted.</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>-b</b> | <b>--add-badblocks</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%">
<i>File</i> is the file name of the file that contains the
list of blocks to be marked as bad on the fs. The list is
added to the fs list of bad blocks.</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>-B</b> | <b>--badblocks</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%">
<i>File</i> is the file name of the file that contains the
list of blocks to be marked as bad on the fs. The bad block
list on the fs is cleared before the list specified in the
<i>File</i> is added to the fs.</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>-f</b> | <b>--force</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%">
Normally <b>reiserfstune</b> will refuse to change a journal
of a file system that was created before this journal
relocation code. This is because if you change the journal,
you cannot go back (without special option
<b>--make-journal-standard</b>) to an old kernel that lacks
this feature and be able to use your filesytem. This option
forces it to do that. Specified more than once it allows to
avoid asking for confirmation.</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>--make-journal-standard</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%">
As it was mentioned above, if your file system has
non-standard journal, it can not be mounted on the kernel
without journal relocation code. The thing can be changed,
the only condition is that there is reserved area on main
device of the standard journal size 8193 blocks (it will be
so for instance if you convert standard journal to
non-standard). Just specify this option when you relocate
journal back, or without relocation if you already have it
on main 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>-u</b> | <b>--uuid</b> <i>UUID</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%">
Set the universally unique identifier ( <b>UUID</b> ) of the
filesystem to <i>UUID</i> (see also <b>uuidgen(8)</b>). The
format of the UUID is a series of hex digits separated by
hypthens, like this:
"c1b9d5a2-f162-11cf-9ece-0020afc76f16".</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>-l</b> | <b>--label</b> <i>LABEL</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%">
Set the volume label of the filesystem. <i>LABEL</i> can be
at most 16 characters long; if it is longer than 16
characters, reiserfstune will truncate it.</td></table>
<a name="POSSIBLE SCENARIOS OF USING REISERFSTUNE:"></a>
<h2>POSSIBLE SCENARIOS OF USING REISERFSTUNE:</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 have ReiserFS on /dev/hda1, and you wish to have it
working with its journal on the device
/dev/journal</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%">
<pre>
boot kernel patched with special "relocatable journal support" patch
reiserfstune /dev/hda1 --journal-new-device /dev/journal -f
mount /dev/hda1 and use.
You would like to change max transaction size to 512 blocks
reiserfstune -t 512 /dev/hda1
You would like to use your file system on another kernel that doesn't
contain relocatable journal support.
umount /dev/hda1
reiserfstune /dev/hda1 -j /dev/journal --journal-new-device /dev/hda1 --make-journal-standard
mount /dev/hda1 and use.
2. You would like to have ReiserFS on /dev/hda1 and to be able to
switch between different journals including journal located on the
device containing the filesystem.
boot kernel patched with special "relocatable journal support" patch
mkreiserfs /dev/hda1
you got solid state disk (perhaps /dev/sda, they typically look like scsi disks)
reiserfstune --journal-new-device /dev/sda1 -f /dev/hda1
Your scsi device dies, it is three in the morning, you have an extra IDE device
lying around
reiserfsck --no-journal-available /dev/hda1
or
reiserfsck --rebuild-tree --no-journal-available /dev/hda1
reiserfstune --no-journal-available --journal-new-device /dev/hda1 /dev/hda1
using /dev/hda1 under patched kernel
</pre></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>reiserfstune</b> has been written by
Vladimir Demidov <vova@namesys.com> and Edward
Shishkin <edward@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; check the syslog file for
any related information.</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>reiserfsck</b>(8), <b>debugreiserfs</b>(8),
<b>mkreiserfs</b>(8)</td></table>
<hr>
</body>
</html>
Server : Apache/2.4.41 (Ubuntu)