From: Hans Reiser <reiser@namesys.com>
To: Yury Umanets <umka@namesys.com>
Cc: Oleg Drokin <green@namesys.com>, reiserfs-list@namesys.com
Subject: Re: Problems with journal size option on mkfs
Date: Thu, 16 May 2002 14:55:34 +0400 [thread overview]
Message-ID: <3CE39026.2010508@namesys.com> (raw)
In-Reply-To: 3CE39135.9010706@namesys.com
Yury Umanets wrote:
> Hans Reiser wrote:
>
>> Oleg Drokin wrote:
>>
>>> Hello!
>>>
>>> On Wed, May 15, 2002 at 03:12:40PM -0500, Steve Pratt wrote:
>>>
>>>
>>>
>>>> I am in the process of writing a File System Interface Module
>>>> (FSIM) for
>>>> EVMS that will interface with ReiserFS and am having a problem with
>>>> the -s
>>>> (journal size) option on mkfs.reiserfs. The problem is that if I
>>>> specify
>>>> any journal size the mkfs fails. By fails, what I mean is that the
>>>> device
>>>> is not mountable, I don't actually get any error message from
>>>> mkfs. This
>>>> happens even when I give it the default size of 8193 blocks. I
>>>> didn't see
>>>>
>>>
>>>
>>>
>>> This is because non-standard journal support is only included in 2.5
>>> kernel
>>> series.
>>> 2.4 support is available as separate patch for now.
>>>
>>> Bye,
>>> Oleg
>>
>>
>> journal resizing and relocating will go into the next pre1.
>>
> progsreiserfs (libreiserfs for reiser3) could relocate and resize
> journal three versions ago.
>
>
>
>
>
>
>
and the kernel code....
next prev parent reply other threads:[~2002-05-16 10:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 20:12 Problems with journal size option on mkfs Steve Pratt
2002-05-16 5:16 ` Oleg Drokin
2002-05-16 10:47 ` Hans Reiser
2002-05-16 11:00 ` Yury Umanets
2002-05-16 10:55 ` Hans Reiser [this message]
2002-05-16 11:52 ` Chris Mason
2002-05-16 12:00 ` Hans Reiser
2002-05-16 13:02 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2002-05-15 21:49 Steve Pratt
2002-05-15 23:43 ` Chris Mason
2002-05-16 14:59 Steve Pratt
2002-05-16 15:09 ` Oleg Drokin
2002-05-16 15:15 ` Hans Reiser
2002-05-16 16:14 ` Edward Shushkin
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=3CE39026.2010508@namesys.com \
--to=reiser@namesys.com \
--cc=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=umka@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.