From: Oleg Drokin <green@namesys.com>
To: Ookhoi <ookhoi@humilis.net>
Cc: reiserfs-list@namesys.com
Subject: Re: reiser4 and 2.5.60
Date: Tue, 18 Feb 2003 12:42:36 +0300 [thread overview]
Message-ID: <20030218124236.A31148@namesys.com> (raw)
In-Reply-To: <20030218103151.B19634@humilis>
Hello!
On Tue, Feb 18, 2003 at 10:31:51AM +0100, Ookhoi wrote:
> > Kind of.
> > It seems that inode_file_plugin(inode)->key_by_inode pointer is zero
> > for one of inodes. But I do not see how that can happen at all.
> > I personally untarred (and then compiled) kernel on this reiser4
> > snapshot without any problems more than once (in fact this is on of my
> > basic tests). I tried bot UP and SMP,
> > block device and loop device with file. Can you describe your system
> > in more details?
> Sure. It is a P-MMX, 200MHz, with 512MB ram, and a 4GB scsi disk.
Hm. That must be real slow, is it? (just because not all of the RAM is covered
by L2 cache, I mean. Or do you have some sensible chipset in there?).
> As said before, I do reiser4 on a loop fs. I did the same with reiser3,
> and that worked ok. Could the loop fs be a problem for reiser4?
Well, it should not, but if you can test it not on loop device just to
be sure, that would be nice.
> I attach dmesg, cpuinfo, lspci and .config
Thank you.
> Do you need more info, or want me to test things?
I need to experiment a bit more locallywith info I got from you, I think.
> It seems that reiser4 in BK is not updated for a few days now.
<joke>Because it is already perfect, nothing to improve</joke> ;)
Bye,
Oleg
next prev parent reply other threads:[~2003-02-18 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-15 15:00 reiser4 and 2.5.60 Ookhoi
2003-02-18 9:12 ` Oleg Drokin
2003-02-18 9:31 ` Ookhoi
2003-02-18 9:33 ` Ookhoi
2003-02-18 9:42 ` Oleg Drokin [this message]
2003-02-18 9:52 ` Ookhoi
2003-02-18 10:05 ` Oleg Drokin
2003-02-18 14:11 ` Ookhoi
2003-02-18 10:08 ` Ookhoi
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=20030218124236.A31148@namesys.com \
--to=green@namesys.com \
--cc=ookhoi@humilis.net \
--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.