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:12:57 +0300 [thread overview]
Message-ID: <20030218121257.A27125@namesys.com> (raw)
In-Reply-To: <20030215160033.A3570@humilis>
Hello!
On Sat, Feb 15, 2003 at 04:00:33PM +0100, Ookhoi wrote:
> I still get a Segmentation fault when I want to untar a kernel source on
> a fresh 512MB loop filesystem.
> Does this help you?
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?
Bye,
Oleg
next prev parent reply other threads:[~2003-02-18 9:12 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 [this message]
2003-02-18 9:31 ` Ookhoi
2003-02-18 9:33 ` Ookhoi
2003-02-18 9:42 ` Oleg Drokin
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=20030218121257.A27125@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.