All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Saveliev <vs@namesys.com>
To: Pierre Fafet <pierre.fafet@ladservices.fr>
Cc: 'Reiserfs List' <reiserfs-list@namesys.com>
Subject: Re: newbie question about mounting options
Date: Fri, 09 Apr 2004 14:41:33 +0400	[thread overview]
Message-ID: <1081507293.2354.6.camel@tribesman.namesys.com> (raw)
In-Reply-To: <000a01c41d82$7e69bf70$3acac9d2@pierre2>

Hello

On Thu, 2004-04-08 at 19:59, Pierre Fafet wrote:
> Hi,
> 
> Sorry if this question was already seen, I'm newbie on this list.
> 
> I tried creating a reiserfs file system with external journal device
> mkreiserfs work fine but I can't mount the FS as you can see on the
> following screen copy :
> 
>     [root@CORTON root]# mkreiserfs -s 8193 -j /dev/sdf1 /dev/sdg2
> 
>     <-------------mkreiserfs, 2002------------->
>     reiserfsprogs 3.6.4
> 
>     mkreiserfs: Guessing about desired format..
>     mkreiserfs: Kernel 2.4.20-30.9smp is running.

This kernel is too old. External journal support was included in 2.4.22

>     Format 3.6 with non-standard journal
>     Count of blocks on the device: 8865871
>     Number of blocks consumed by mkreiserfs formatting process: 289
>     Blocksize: 4096
>     Hash function used to sort names: "r5"
>     Journal Device [0x851]
>     Journal Size 8193 blocks (first block 0)
>     Journal Max transaction length 1024
>     Space on this device reserved by journal: 0
>     inode generation number: 0
>     UUID: 874b3d7c-48b8-48ca-90e1-80bc98c74193
>     ATTENTION: YOU SHOULD REBOOT AFTER FDISK!
>             ALL DATA WILL BE LOST ON '/dev/sdg2' AND ON JOURNAL DEVICE
> '/dev/sdf1'!
>     Continue (y/n):y
>     Initializing journal - 0%....20%....40%....60%....80%....100%
>     Syncing..ok
> 
>     The [...]
>     Have fun.
> 
>     [root@CORTON root]# mount -t reiserfs /dev/sdg2 /mnt
>     mount: wrong fs type, bad option, bad superblock on /dev/sdg2,
>            or too many mounted file systems
>     [root@CORTON root]#
> 
> Why is it not working ?
> 
> My distrib is Red Hat Linux 9
> 
> 
> P.F.
> 
> 


      parent reply	other threads:[~2004-04-09 10:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 15:59 newbie question about mounting options Pierre Fafet
2004-04-08 16:26 ` Valdis.Kletnieks
2004-04-09 10:41 ` Vladimir Saveliev [this message]

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=1081507293.2354.6.camel@tribesman.namesys.com \
    --to=vs@namesys.com \
    --cc=pierre.fafet@ladservices.fr \
    --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.