/usr/share/doc/reiserfsprogs/html/mount-options.html is in reiserfsprogs 1:3.6.24-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 | <!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>
|