All of lore.kernel.org
 help / color / mirror / Atom feed
From: mjt@nysv.org
To: Vladimir Saveliev <vs@namesys.com>
Cc: Alex Zarochentsev <zam@namesys.com>, reiserfs-list@namesys.com
Subject: Re: mount throws a nikita-3228 on me
Date: Thu, 27 May 2004 12:21:04 +0300	[thread overview]
Message-ID: <20040527092104.GL4990@nysv.org> (raw)
In-Reply-To: <1085641367.1915.197.camel@tribesman.namesys.com>

On Thu, May 27, 2004 at 11:02:47AM +0400, Vladimir Saveliev wrote:

>> OK. I tried it with what was suggested on the list.
>> It did not, however work. I added the lines to reiser4.h; 
>did you remove lines from debug.h?

Yes.

>> But I understood from IRC that this problem should really be fixed?
>> So am I doing something wrong here?
>certainly

It's seldom comforting to hear you're wrong; this is an exception :)

>Please try the following: add something incompilable in reiser4.h right
>after 
>#define REISER4_LARGE_KEY (1)
>
>on compiling you should get some files not compilable - as expected
>and some files which compile fine. The last ones have wrong #include
>section. The mentioned change in reiser4.h and debug.h should fix that
>though

I actually got the bugger to mount now. I just can't remember what
I did, because it was past midnight...
I switched to large keys, that must be one thing. So small keys are
probably broken? Should it even mount in that situation?

I got an oops and the bird and some stack trace, though. So it mounts
but goes belly-up.

I disabled the Reiser4 syscalls and it still didn't work. Then I went
to sleep.

There seems to be some funkyness with compiling as well.
Sometimes it dies with a get: command not found.

Is there any chance of having some daily snapshot diff available?
This was talked about before. It would save a shitload of trouble
if one wouldn't have to mess with bk and track pulled snapshots and
so on and so forth...

I'll post more details on the errors and some screenshots of the
stack trace when I get the opportunity and my corner of the web
back working. Hopefully today. And of course my .config and everything
else relevant.

Thanks for the help!
The first step in fixing a bug is knowing of its existence ;)

-- 
mjt


      reply	other threads:[~2004-05-27  9:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-25  8:00 mount throws a nikita-3228 on me mjt
2004-05-25  8:30 ` 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 [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=20040527092104.GL4990@nysv.org \
    --to=mjt@nysv.org \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@namesys.com \
    --cc=zam@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.