From: mjt@nysv.org
To: reiserfs-list@namesys.com
Subject: mount throws a nikita-3228 on me
Date: Tue, 25 May 2004 11:00:01 +0300 [thread overview]
Message-ID: <20040525080001.GF4990@nysv.org> (raw)
Hi
I took a snapshot from the Namesys BK some days ago, compiled the
2.6.6-mm2 with high hopes of the future, but it doesn't mount.
It says only small keys are supported. I think it was a Nikita-3228.[1]
Looking at the code, it seems like it checks which size of keys are
supported. AFAIK this is not an mkfs-time option, but a kernel option only?
What does it mean, is the BK kernel broken or must I work some magick
to get it working?
What does it mean when the kernel help says it will make my system
binary-incompatible? Just that it doesn't mount or will actual ELF
files break?
Why support two key sizes at all? Small keys save disk space but aren't
as cool? Is there some practical situation where one would not want
large keys?
I'm not the only one who has experienced this, but I haven't heard
anyone getting it to work, so any help would be much appreciated.
[1]
Whoever came up with this bug naming scheme deserves an award for
innovation, practice and cleanliness. If I ever get a project where
this may be applied, I will borrow the idea :)
--
mjt
next reply other threads:[~2004-05-25 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 8:00 mjt [this message]
2004-05-25 8:30 ` mount throws a nikita-3228 on me Vladimir Saveliev
2004-05-25 8:55 ` Alex Zarochentsev
2004-05-25 9:07 ` Alex Zarochentsev
2004-05-25 21:11 ` mjt
2004-05-26 5:20 ` Alex Zarochentsev
2004-05-26 20:40 ` mjt
2004-05-27 7:02 ` Vladimir Saveliev
2004-05-27 9:21 ` mjt
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=20040525080001.GF4990@nysv.org \
--to=mjt@nysv.org \
--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.