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/self/root/usr/share/doc/reiserfsprogs/html/
Upload File :
Current File : //proc/self/root/usr/share/doc/reiserfsprogs/html/mount-options.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta name="Author" content="Danilov Nikita">
<meta name="GENERATOR" content="Hand crafted in XEMACS">
<meta name="Description" content="ReiserFS mount options">
<meta name="KeyWords" content="reiserfs, ReiserFS, namesys, file-system, file system, filesystem, mount, mount options, conversion, nolog, notail, reiserfs-raw, GC, garbage collector">
<link href="style_whitepaper.css" rel="stylesheet">
<title>ReiserFS mount options</title>
</head>
<body>
<h1>ReiserFS Mount Options</h1>
<h2>linux kernels 2.4.x</h2>
<dl>
<!-- 2.6 -->
<dt><span class="code">conv</span></dt>
<dd>
<p>
Instructs <span class="ver">3.6</span> ReiserFS code to mount
<span class="ver">3.5</span> filesystem, using
<span class="ver">3.6</span> format for newly created objects.
After this you cannot use it through <span class="ver">3.5</span>
ReiserFS tools anymore. This option causes conversion of old
format super block to the new format. If not specified - old
partition will be dealt with in a manner of 3.5.
</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o conv /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!--
<dt><span class="code">dontpanic</span></dt>
<dd>
<p>
Ignore IO errors during journal committing. Without this option ReiserFS
will panic on IO errors.<br>
<em>Only available when reiserfs-raw is used.</em> Not in the stock kernels.
</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o dontpanic /dev/sdb1 /cache/squid-cache-1
</pre>
</dd>
-->
<!-- 2.6 -->
<dt><span class="code">nolog</span></dt>
<dd>
<p>
Disable journalling. This will get you slight performance improvement in
some situations at the cost of losing fast recovery from crashes.
Actually even with this option turned on, ReiserFS still performs all
journalling paraphernalia, save for actual writes into journalling area.
Implementation of real <span class="code">nolog</span> is work in progress. </p>
<p>Example:</p>
<pre>
mount -t reiserfs -o nolog /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!-- 2.6 -->
<dt><span class="code">notail</span></dt>
<dd>
<p>
By default, ReiserFS stores small files and `file tails' directly
into the tree. This confuses some utilities like
<span class="fileName">LILO</span>. This option is used to disable
packing of files into the tree.</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o notail /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!--
<dt><span class="code">pgc=LOW,HIGH</span></dt>
<dd>
<p>
Activate Passive Garbage Collector.<br>
<em>Only available when reiserfs-raw is used.</em> Not in the stock kernels.</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o pgc=50,75 /dev/sdb1 /cache/squid-cache-1
</pre>
</dd>
</dd>
<dt><span class="code">raw</span></dt>
<dd>
<p>
Mount filesystem in `<em>raw</em>' access mode. <br>
<em>Only available when reiserfs-raw is used.</em> Not in the stock kernels.</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o raw /dev/sdb1 /cache/squid-cache-1
</pre>
</dd>
-->
<!-- 2.6 not checked -->
<dt><span class="code">replayonly</span></dt>
<dd>
<p>
Replay transactions in journal, but don't actually mount filesystem.
Used by fsck, mostly.</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o replayonly /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!-- 2.6 -->
<dt><span class="code">jdev=journal_device</span></dt>
<dd>
<p>
</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o jdev=/dev/sdb2 /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!-- 2.6 -->
<dt><span class="code">attrs</span></dt>
<dd>
<p>
</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o attrs /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!-- 2.6 -->
<dt><span class="code">noattrs</span></dt>
<dd>
<p>
</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o noattrs /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!-- 2.6. not cheked -->
<dt><span class="code">resize=NUMBER</span></dt>
<dd>
<p>
Remount option allowing to expand ReiserFS partition on-line.
Make ReiserFS think that device has NUMBER blocks.
Useful with LVM devices.
There is a special resizer utility
which can be obtained from
<a
href="ftp://ftp.namesys.com/pub/reiserfsprogs">ftp://ftp.namesys.com/pub/reiserfsprogs</a></p>
<p>Example:</p>
<pre>
mount -t reiserfs -o resize=680000 /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!-- 2.6 does not work -->
<dt><span class="code">hash=rupasov / tea / r5 / detect</span></dt>
<dd>
<p>
Choose hash function ReiserFS will use to find files within
directories.
Long time ago ReiserFS had only one hash,
so hash code was not marked in filesystem superblock. Then additional hashes
became available so we had to put hash code into super block. Also, old hash was
made notdefault. At that time there were already a number of filesystems with not
set hash code in super block. So, mount option was created to make it possible to
write proper hash value into super block.
Relative merits of hash functions were subjected to discussions of great
length on the
<a href="http://marc.theaimsgroup.com/?l=reiserfs&r=1&w=2">ReiserFS mailing list</a>.
(Try this <a href="http://marc.theaimsgroup.com/?l=reiserfs&w=2&r=1&s=hash+tea+rupasov&q=b">query</a>.)
Roughly speaking: 99% of the time, this option
is not required. If the normal autodection code can't determine which
hash to use (because both hases had the same value for a file)
use this option to force a specific hash. It won't allow you to override
the existing hash on the FS, so if you have a tea hash disk, and mount
with -o hash=rupasov, the mount will fail.
</p>
<p>
<dl>
<dt><span class="code">rupasov</span></dt>
<dd>
<p>
This hash is invented by
<a href="mailto:yura@yura.polnet.botik.ru">Yury Yu. Rupasov <yura@yura.polnet.botik.ru></a>. It is fast and preserves locality, mapping lexicographically
close file names to the close hash values. Never use it, as it has high probability of hash collisions.
</p>
</dd>
<dt><span class="code">tea</span></dt>
<dd>
<p>
This hash is a Davis-Meyer function
implemented by <a href="mailto:jeremy@zip.com.au">Jeremy Fitzhardinge <jeremy@zip.com.au></a>.
It is hash permuting bits in the name thoroughly. It gets high randomness
and, therefore, low probability of hash collision, but this costs
performance. Use this if you got <span class="code">EHASHCOLLISION</span> with
<span class="code">r5</span> hash.
</p>
</dd>
<dt><span class="code">r5</span></dt>
<dd>
<p>
This hash is a modified version of
<span class="code">rupasov</span> hash. It is used by default and it is
better to stick here until you have to support huge directories and unusual
file-name patterns.
</p>
</dd>
<dt><span class="code">detect</span></dt>
<dd>
<p>
This is the instructs mount to detect hash function
in use by instance of filesystem being mounted and write this information
into superblock. This is only useful on the first mount of old filesystem.
</p>
</dd>
</dl>
<p>Example:</p>
<pre>
mount -t reiserfs -o hash=r5 /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!-- 2.6 -->
<dt><span class="code">block-allocator=hashed_relocation /
no_unhashed_relocation / noborder / border </span></dt>
<dd>
<p>
Tunes block allocator.
This option is used for testing experimental features, makes benchmarking new
features with and without more convenient, should never be used by
users in any code shipped to users (ideally).
</p>
<p>
<dl>
<!-- 2.6 -->
<dt><span class="code">hashed_relocation</span></dt>
<dd>
<p>
Tunes block allocator.
This may give you performance improvements in some situations.
</p>
</dd>
<!-- 2.6 -->
<dt><span class="code">no_unhashed_relocation</span></dt>
<dd>
<p>
Tunes block allocator.
This may give you performance improvements in some situations.
</p>
</dd>
<!-- 2.6 -->
<dt><span class="code">noborder</span></dt>
<dd>
<p>
Disable `<em>border allocator algorithm</em>' invented by
<a href="mailto:yura@yura.polnet.botik.ru">Yury Yu. Rupasov <yura@yura.polnet.botik.ru></a>.
This may give you performance improvements in some situations.
<!-- (This option was also known as <span class="code">test1</span>.) -->
</p>
</dd>
<!-- 2.6 -->
<dt><span class="code">block-allocator=border</span></dt>
<dd>
<p>
Enable `<em>border allocator algorithm</em>' invented by
<a href="mailto:yura@yura.polnet.botik.ru">Yury Yu. Rupasov
<yura@yura.polnet.botik.ru></a>.
This may give you performance improvements in some situations.
</dd>
</dl>
</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o block-allocator=border /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!--
<dt><span class="code">test4</span></dt>
<dd>
<p>
This doesn't seem to be of any use now.</p>
</dd>
-->
</dl>
<hr>
<h2>linux kernels 2.6.x</h2>
<dl>
<!-- 2.6 -->
<dt><span class="code">conv</span></dt>
<dd>
<p>
Instructs <span class="ver">3.6</span> ReiserFS code to mount
<span class="ver">3.5</span> filesystem, using
<span class="ver">3.6</span> format for newly created objects.
After this you cannot use it through <span class="ver">3.5</span>
ReiserFS tools anymore. This option causes conversion of old
format super block to the new format. If not specified - old
partition will be dealt with in a manner of 3.5.
</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o conv /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!-- 2.6 -->
<dt><span class="code">nolog</span></dt>
<dd>
<p>
Disable journalling. This will get you slight performance improvement in
some situations at the cost of losing fast recovery from crashes.
Actually even with this option turned on, ReiserFS still performs all
journalling paraphernalia, save for actual writes into journalling area.
Implementation of real <span class="code">nolog</span> is work in progress. </p>
<p>Example:</p>
<pre>
mount -t reiserfs -o nolog /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!-- 2.6 -->
<dt><span class="code">notail</span></dt>
<dd>
<p>
By default, ReiserFS stores small files and `file tails' directly
into the tree. This confuses some utilities like
<span class="fileName">LILO</span>. This option is used to disable
packing of files into the tree.</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o notail /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!-- 2.6 not checked whether this works or not -->
<dt><span class="code">replayonly</span></dt>
<dd>
<p>
Replay transactions in journal, but don't actually mount filesystem.
Used by fsck, mostly.</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o replayonly /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!-- 2.6 -->
<dt><span class="code">jdev=journal_device</span></dt>
<dd>
<p>
</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o jdev=/dev/sdb2 /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!-- 2.6 -->
<dt><span class="code">attrs</span></dt>
<dd>
<p>
</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o attrs /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!-- 2.6 -->
<dt><span class="code">noattrs</span></dt>
<dd>
<p>
</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o noattrs /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!-- 2.6. did not cheked -->
<dt><span class="code">resize=NUMBER</span></dt>
<dd>
<p>
Remount option allowing to expand ReiserFS partition on-line.
Make ReiserFS think that device has NUMBER blocks.
Useful with LVM devices.
There is a special resizer utility
which can be obtained from
<a
href="ftp://ftp.namesys.com/pub/reiserfsprogs">ftp://ftp.namesys.com/pub/reiserfsprogs</a></p>
<p>Example:</p>
<pre>
mount -t reiserfs -o resize=680000 /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!-- 2.6 -->
<dt><span class="code">data=ordered / journal / writeback </span></dt>
<dd>
<p>
Specifies the journalling mode for file data. Metadata is always journaled.
<dl>
<dt><span class="code">journal</span></dt>
<dd>
<p>
All data is committed into the journal prior to being written into the main
file system.
</p>
</dd>
<dt><span class="code">ordered</span></dt>
<dd>
<p>
This is the default mode. All data is forced directly out to the main
file system prior to its metadata being committed to the journal.
</p>
</dd>
<dt><span class="code">writeback</span></dt>
<dd>
<p>
Data ordering is not preserved - data may be written into the main
file system after its metadata has been committed to the journal.
This is rumoured to be the highest-throughput option. It guarantees
internal file system integrity, however it can allow old data to appear in
files after a crash and journal recovery.
</p>
</dd>
</dl>
</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o data=writeback /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
<!-- 2.6 -->
<dt><span class="code">block-allocator=hashed_relocation /
no_unhashed_relocation / noborder / border </span></dt>
<dd>
<p>
Tunes block allocator.
This option is used for testing experimental features, makes benchmarking new
features with and without more convenient, should never be used by
users in any code shipped to users (ideally).
</p>
<p>
<dl>
<!-- 2.6 -->
<dt><span class="code">hashed_relocation</span></dt>
<dd>
<p>
Tunes block allocator.
This may give you performance improvements in some situations.
</p>
</dd>
<!-- 2.6 -->
<dt><span class="code">no_unhashed_relocation</span></dt>
<dd>
<p>
Tunes block allocator.
This may give you performance improvements in some situations.
</p>
</dd>
<!-- 2.6 -->
<dt><span class="code">noborder</span></dt>
<dd>
<p>
Disable `<em>border allocator algorithm</em>' invented by
<a href="mailto:yura@yura.polnet.botik.ru">Yury Yu. Rupasov <yura@yura.polnet.botik.ru></a>.
This may give you performance improvements in some situations.
<!-- (This option was also known as <span class="code">test1</span>.) -->
</p>
</dd>
<!-- 2.6 -->
<dt><span class="code">block-allocator=border</span></dt>
<dd>
<p>
Enable `<em>border allocator algorithm</em>' invented by
<a href="mailto:yura@yura.polnet.botik.ru">Yury Yu. Rupasov
<yura@yura.polnet.botik.ru></a>.
This may give you performance improvements in some situations.
</dd>
</dl>
</p>
<p>Example:</p>
<pre>
mount -t reiserfs -o block-allocator=border /dev/sdb1 /mnt/scsi-disk-b
</pre>
</dd>
</dl>
<hr>
<p class="fine-print">
Maintainer: <a href="mailto:grev@namesys.com">grev@namesys.com</a>
<!-- Created: Wed Jan 24 16:13:00 MSK 2001 -->
<!-- hhmts start -->
<!-- hhmts end -->
</p>
</body>
</html>
Server : Apache/2.4.41 (Ubuntu)