From: "E.Gryaznova" <grev@namesys.com>
To: "Martin MOKREJŠ" <mmokrejs@ribosome.natur.cuni.cz>
Cc: reiserfs-list@namesys.com
Subject: Re: Unsupported mkreiserfs and mount options
Date: Tue, 19 Oct 2004 20:47:33 +0400 [thread overview]
Message-ID: <41754525.3070305@namesys.com> (raw)
In-Reply-To: <41750674.3060505@ribosome.natur.cuni.cz>
Martin MOKREJ© wrote:
> Hi,
> I'm doing some benchmarking of reiserfs on 2.4.28-pre3 system.
> I have crafted some non-standard options to mkreiserfs and mount,
> but they sometimes fail. I've attached only those which have failed.
> ;)
>
> Am I right they don't work but should according to manpages?
> Thanks for help
> Martin
> P.S.: Yes, some messages about unsupported bla bla got logged by syslog.
> Why cannot user see the on STDERR? I simply don't know what has
> generated what in syslog. :(
>
>------------------------------------------------------------------------
>
>mkreiserfs -f -s 8192 -b 2048 /dev/sdb2
>Guessing about desired format.. Kernel 2.4.28-pre3 is running.
>Format 3.6 with non-standard journal
>Count of blocks on the device: 638137920
>Number of blocks consumed by mkreiserfs formatting process: 47175
>Blocksize: 2048
>Hash function used to sort names: "r5"
>Journal Size 8192 blocks (first block 34)
>Journal Max transaction length 512
>inode generation number: 0
>UUID: f9c76801-44d4-4020-a5cf-b9e5aa76a707
>Initializing journal - 0%....20%....40%....60%....80%....100%
>Syncing..ok
>mount -t reiserfs /dev/sdb2 /scratch
>mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
> or too many mounted file systems
> (aren't you trying to mount an extended partition,
> instead of some logical partition inside?)
>
>
>
block size = 2048 is supported in 2.6.x kernel.
>
>mkreiserfs -f -s 8192 -b 8192 /dev/sdb2
>Guessing about desired format.. Kernel 2.4.28-pre3 is running.
>Format 3.6 with non-standard journal
>Count of blocks on the device: 159534480
>Number of blocks consumed by mkreiserfs formatting process: 10637
>Blocksize: 8192
>Hash function used to sort names: "r5"
>Journal Size 8192 blocks (first block 10)
>Journal Max transaction length 1024
>inode generation number: 0
>UUID: fcfa840c-4170-421a-9383-cebaf2d78b58
>Initializing journal - 0%....20%....40%....60%....80%....100%
>Syncing..ok
>mount -t reiserfs /dev/sdb2 /scratch
>mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
> or too many mounted file systems
> (aren't you trying to mount an extended partition,
> instead of some logical partition inside?)
>
>
>
>mkreiserfs -f -h r5 /dev/sdb2
>Guessing about desired format.. Kernel 2.4.28-pre3 is running.
>Format 3.6 with standard journal
>Count of blocks on the device: 319068960
>Number of blocks consumed by mkreiserfs formatting process: 17949
>Blocksize: 4096
>Hash function used to sort names: "r5"
>Journal Size 8193 blocks (first block 18)
>Journal Max transaction length 1024
>inode generation number: 0
>UUID: 2fa671ed-eb3e-4e4f-b59c-040502c6d7b4
>Initializing journal - 0%....20%....40%....60%....80%....100%
>Syncing..ok
>mount -t reiserfs -o r5 /dev/sdb2 /scratch
>mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
> or too many mounted file systems
> (aren't you trying to mount an extended partition,
> instead of some logical partition inside?)
>
>
>
>
You use incorrect mount option. In according to
www.namesys.com/mount-options.html the correct option is :
-o hash=r5
>mkreiserfs -f -h yura /dev/sdb2
>mkreiserfs: wrong hash type specified. Using default
>mkreiserfs 3.6.17 (2003 www.namesys.com)
>
>
I am confused, why do you use "yura" hash?
# mkeriserfs --help
mkreiserfs 3.6.17 (2003 www.namesys.com)
Options:
-h | --hash rupasov|tea|r5 hash function to use by default
>
>mkreiserfs -f -t 16384 /dev/sdb2
>mkreiserfs 3.6.17 (2003 www.namesys.com)
>WARNING: wrong transaction max size (16384). Changed to 1024
>
>
>mkreiserfs -f -t 65535 /dev/sdb2
>mkreiserfs 3.6.17 (2003 www.namesys.com)
>WARNING: wrong transaction max size (65535). Changed to 1024
>
>
>mkreiserfs -f -t 131072 /dev/sdb2
>mkreiserfs 3.6.17 (2003 www.namesys.com)
>WARNING: wrong transaction max size (131072). Changed to 1024
>
>
mkreiserfs man page says that :
-t | --transaction-max-size N
N is the maximum transaction size parameter for the
journal. The default, and max possible, value is
1024 blocks. It should be less than half the size
of the journal. If specified incorrectly, it will
automatically be adjusted.
>
>mkreiserfs -f -h r5 /dev/sdb2
>Guessing about desired format.. Kernel 2.4.28-pre3 is running.
>Format 3.6 with standard journal
>Count of blocks on the device: 319068960
>Number of blocks consumed by mkreiserfs formatting process: 17949
>Blocksize: 4096
>Hash function used to sort names: "r5"
>Journal Size 8193 blocks (first block 18)
>Journal Max transaction length 1024
>inode generation number: 0
>UUID: 2b54ffa7-068a-428b-bc7b-a8b3ba80400b
>Initializing journal - 0%....20%....40%....60%....80%....100%
>Syncing..ok
>mount -t reiserfs -o hashed_relocation /dev/sdb2 /scratch
>mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
> or too many mounted file systems
> (aren't you trying to mount an extended partition,
> instead of some logical partition inside?)
>
>
In according to www.namesys.com/mount-options.html the correct option is
-o block-allocator=hashed_relocation
>
>
>mkreiserfs -f -h r5 /dev/sdb2
>Guessing about desired format.. Kernel 2.4.28-pre3 is running.
>Format 3.6 with standard journal
>Count of blocks on the device: 319068960
>Number of blocks consumed by mkreiserfs formatting process: 17949
>Blocksize: 4096
>Hash function used to sort names: "r5"
>Journal Size 8193 blocks (first block 18)
>Journal Max transaction length 1024
>inode generation number: 0
>UUID: e2d5da73-0359-4bc1-bfcb-6dad0a80efe6
>Initializing journal - 0%....20%....40%....60%....80%....100%
>Syncing..ok
>mount -t reiserfs -o no_unhashed_relocation /dev/sdb2 /scratch
>mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
> or too many mounted file systems
> (aren't you trying to mount an extended partition,
> instead of some logical partition inside?)
>
>
>
-o block-allocator=no_unhashed_relocation
>
>mkreiserfs -f -h r5 /dev/sdb2
>Guessing about desired format.. Kernel 2.4.28-pre3 is running.
>Format 3.6 with standard journal
>Count of blocks on the device: 319068960
>Number of blocks consumed by mkreiserfs formatting process: 17949
>Blocksize: 4096
>Hash function used to sort names: "r5"
>Journal Size 8193 blocks (first block 18)
>Journal Max transaction length 1024
>inode generation number: 0
>UUID: 10caff17-0e91-4517-814b-fc407a996985
>Initializing journal - 0%....20%....40%....60%....80%....100%
>Syncing..ok
>mount -t reiserfs -o noborder /dev/sdb2 /scratch
>mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
> or too many mounted file systems
> (aren't you trying to mount an extended partition,
> instead of some logical partition inside?)
>
>
>
-o block-allocator=noborder
>
>mkreiserfs -f -h r5 /dev/sdb2
>Guessing about desired format.. Kernel 2.4.28-pre3 is running.
>Format 3.6 with standard journal
>Count of blocks on the device: 319068960
>Number of blocks consumed by mkreiserfs formatting process: 17949
>Blocksize: 4096
>Hash function used to sort names: "r5"
>Journal Size 8193 blocks (first block 18)
>Journal Max transaction length 1024
>inode generation number: 0
>UUID: c2edaab9-1b24-459b-ba62-722798e0745d
>Initializing journal - 0%....20%....40%....60%....80%....100%
>Syncing..ok
>mount -t reiserfs -o r5 /dev/sdb2 /scratch
>mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
> or too many mounted file systems
> (aren't you trying to mount an extended partition,
> instead of some logical partition inside?)
>
>
>
the correct option is
-o hash=r5 (as it is docummented in www.namesys.com/mount-options.html)
would you please check is this work for you? I did not check 2.4.28, but
this works fine in 2.4.23.
Thanks,
Lena
next prev parent reply other threads:[~2004-10-19 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 12:20 Unsupported mkreiserfs and mount options Martin MOKREJŠ
2004-10-19 14:28 ` Edward Shishkin
2004-10-19 15:02 ` Martin MOKREJŠ
2004-10-19 15:47 ` Edward Shishkin
2004-10-19 16:47 ` E.Gryaznova [this message]
2004-10-22 8:38 ` Martin MOKREJŠ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41754525.3070305@namesys.com \
--to=grev@namesys.com \
--cc=mmokrejs@ribosome.natur.cuni.cz \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.