From: Oleg Drokin <green@namesys.com>
To: Steve Pratt <slpratt@us.ibm.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Problems with journal size option on mkfs
Date: Thu, 16 May 2002 19:09:11 +0400 [thread overview]
Message-ID: <20020516190911.A2877@namesys.com> (raw)
In-Reply-To: <OF61DE11CE.F7B7B7AE-ON85256BBB.0051CE0D@pok.ibm.com>
Hello!
On Thu, May 16, 2002 at 09:59:46AM -0500, Steve Pratt wrote:
> >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.
> So just to be sure I understand this:the current 2.4 kernel code (2.4.18)
> does not include support for ANY non-standard journal options, including
> non default size of an inline log??
Yes, this is correct.
> If this is true, wouldn't it have made sense to put some checking in the
> utilities to detect the level of support in the kernel and either put out a
> meaningful error message or simply ignore the option? As it stands now,
> from the command line mkfs doesn't even indicate that there was an error.
There were no error at mkfs time. May be user is doing mkfs from some bootable
floppy with old kernel and then plans to boot into more modern kernel, for
example.
> Even if the ReiserFS utilities don't check, is there some way I can query
> the ReiserFS kernel code to detect the presence of these features?
Well, the simplest way is to have (or make) small file with reiserfs image
with non-standard journal and try to mount it ;)
Or you can try to mount valid reiserfs fs with jdev= mount option, which
is only present on code with nonstandard journaling support.
In short, there is no easy way. But if you can think of any,
we might implement it if it non-intrusive and easy enough.
Actually this is not very reliable in the sence that you cannot say
which kernel user plans to use later on.
Bye,
Oleg
next prev parent reply other threads:[~2002-05-16 15:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 14:59 Problems with journal size option on mkfs Steve Pratt
2002-05-16 15:09 ` Oleg Drokin [this message]
2002-05-16 15:15 ` Hans Reiser
2002-05-16 16:14 ` Edward Shushkin
-- 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-15 20:12 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
2002-05-16 11:52 ` Chris Mason
2002-05-16 12:00 ` Hans Reiser
2002-05-16 13:02 ` Chris Mason
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=20020516190911.A2877@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=slpratt@us.ibm.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.