Instructs 3.6 ReiserFS code to mount
3.5 filesystem, using
3.6 format for newly created objects.
After this you cannot use it through 3.5
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.
Example:
mount -t reiserfs -o conv /dev/sdb1 /mnt/scsi-disk-b
nolog
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 nolog is work in progress.
Example:
mount -t reiserfs -o nolog /dev/sdb1 /mnt/scsi-disk-b
notail
By default, ReiserFS stores small files and `file tails' directly
into the tree. This confuses some utilities like
LILO. This option is used to disable
packing of files into the tree.
Example:
mount -t reiserfs -o notail /dev/sdb1 /mnt/scsi-disk-b
replayonly
Replay transactions in journal, but don't actually mount filesystem.
Used by fsck, mostly.
Example:
mount -t reiserfs -o replayonly /dev/sdb1 /mnt/scsi-disk-b
jdev=journal_device
Example:
mount -t reiserfs -o jdev=/dev/sdb2 /dev/sdb1 /mnt/scsi-disk-b
attrs
Example:
mount -t reiserfs -o attrs /dev/sdb1 /mnt/scsi-disk-b
noattrs
Example:
mount -t reiserfs -o noattrs /dev/sdb1 /mnt/scsi-disk-b
resize=NUMBER
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
ftp://ftp.namesys.com/pub/reiserfsprogs
Example:
mount -t reiserfs -o resize=680000 /dev/sdb1 /mnt/scsi-disk-b
hash=rupasov / tea / r5 / detect
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
ReiserFS mailing list.
(Try this query.)
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.
rupasov
This hash is invented by
Yury Yu. Rupasov <yura@yura.polnet.botik.ru>. 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.
tea
This hash is a Davis-Meyer function
implemented by Jeremy Fitzhardinge <jeremy@zip.com.au>.
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 EHASHCOLLISION with
r5 hash.
r5
This hash is a modified version of
rupasov 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.
detect
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.
Example:
mount -t reiserfs -o hash=r5 /dev/sdb1 /mnt/scsi-disk-b
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).
hashed_relocation
Tunes block allocator.
This may give you performance improvements in some situations.
no_unhashed_relocation
Tunes block allocator.
This may give you performance improvements in some situations.
mount -t reiserfs -o block-allocator=border /dev/sdb1 /mnt/scsi-disk-b
linux kernels 2.6.x
conv
Instructs 3.6 ReiserFS code to mount
3.5 filesystem, using
3.6 format for newly created objects.
After this you cannot use it through 3.5
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.
Example:
mount -t reiserfs -o conv /dev/sdb1 /mnt/scsi-disk-b
nolog
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 nolog is work in progress.
Example:
mount -t reiserfs -o nolog /dev/sdb1 /mnt/scsi-disk-b
notail
By default, ReiserFS stores small files and `file tails' directly
into the tree. This confuses some utilities like
LILO. This option is used to disable
packing of files into the tree.
Example:
mount -t reiserfs -o notail /dev/sdb1 /mnt/scsi-disk-b
replayonly
Replay transactions in journal, but don't actually mount filesystem.
Used by fsck, mostly.
Example:
mount -t reiserfs -o replayonly /dev/sdb1 /mnt/scsi-disk-b
jdev=journal_device
Example:
mount -t reiserfs -o jdev=/dev/sdb2 /dev/sdb1 /mnt/scsi-disk-b
attrs
Example:
mount -t reiserfs -o attrs /dev/sdb1 /mnt/scsi-disk-b
noattrs
Example:
mount -t reiserfs -o noattrs /dev/sdb1 /mnt/scsi-disk-b
resize=NUMBER
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
ftp://ftp.namesys.com/pub/reiserfsprogs
Example:
mount -t reiserfs -o resize=680000 /dev/sdb1 /mnt/scsi-disk-b
data=ordered / journal / writeback
Specifies the journalling mode for file data. Metadata is always journaled.
journal
All data is committed into the journal prior to being written into the main
file system.
ordered
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.
writeback
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.
Example:
mount -t reiserfs -o data=writeback /dev/sdb1 /mnt/scsi-disk-b
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).
hashed_relocation
Tunes block allocator.
This may give you performance improvements in some situations.
no_unhashed_relocation
Tunes block allocator.
This may give you performance improvements in some situations.