From: Edward Shishkin <edward@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 19:47:35 +0400 [thread overview]
Message-ID: <41753717.8050108@namesys.com> (raw)
In-Reply-To: <41752C7B.5080107@ribosome.natur.cuni.cz>
Martin MOKREJ© wrote:
> Edward Shishkin wrote:
>
>> Martin MOKREJ© wrote:
>
>
> sd(8,18):Using r5 hash to sort names
> reiserfs_getopt: head of option "hash" is only correct
Ahh, you specify the mount options a bit incorrect, first
use the "type" of the option:
mount -t reiserfs -o hash=r5 /dev/sdb2 /scratch
> reiserfs_getopt: unknown option "no_unhashed_relocation"
use 'block-allocator' here, etc..
See http://www.namesys.com/mount-options.html
for details.
Edward
> reiserfs_getopt: unknown option "noborder"
> reiserfs: found format "3.6" with standard journal
> reiserfs: checking transaction log (device sd(8,18)) ...
> for (sd(8,18))
> sd(8,18):Using r5 hash to sort names
> reiserfs: found format "3.6" with standard journal
> reiserfs: checking transaction log (device sd(8,18)) ...
> for (sd(8,18))
> sd(8,18):Using r5 hash to sort names
> reiserfs_getopt: unknown option "r5"
>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> 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?)
>>
next prev parent reply other threads:[~2004-10-19 15: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 [this message]
2004-10-19 16:47 ` E.Gryaznova
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=41753717.8050108@namesys.com \
--to=edward@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.