From: Alex Zarochentsev <zam@namesys.com>
To: "Markus TЖrnqvist" <mjt@nysv.org>
Cc: "Raymond A. Meijer" <rmeijer@internet.gr>, reiserfs-list@namesys.com
Subject: Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?
Date: Wed, 2 Jun 2004 20:34:45 +0400 [thread overview]
Message-ID: <20040602163444.GG8091@backtop.namesys.com> (raw)
In-Reply-To: <20040602162348.GH4990@nysv.org>
On Wed, Jun 02, 2004 at 07:23:48PM +0300, Markus Törnqvist wrote:
> On Wed, Jun 02, 2004 at 08:02:34PM +0400, Alex Zarochentsev wrote:
> >> But there was a kernel Oops and something like:
> >> "page_extent: trying to read past end of device. Want=23252123 Limit=83380"
> >It would be fine to see a (decoded) stack trace.
<linux source dir>/Documentation/oops-tracing.txt
> Not that I would have had this problem, but are there some general
> guidelines/FAQ-like answer on how to acquire this?
>
> >> I can try again and write down the messages if you want...
> >Does the snapshot from 2004.04.21 or from 2004.03.26 work still ?
>
> It's against 2.6.5, not 2.6.6, and I think that was the general idea...
Do you use RAID or LVM ?
> --
> mjt
>
--
Alex.
next prev parent reply other threads:[~2004-06-02 16:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 12:54 Working Reiser4 patch for kernel 2.6.6(-mm2)? Raymond A. Meijer
2004-06-02 12:56 ` Alex Zarochentsev
2004-06-02 13:03 ` Raymond A. Meijer
2004-06-02 16:02 ` Alex Zarochentsev
2004-06-02 16:23 ` mjt
2004-06-02 16:34 ` Alex Zarochentsev [this message]
2004-06-02 16:39 ` Alex Zarochentsev
2004-06-02 16:52 ` mjt
2004-06-03 11:07 ` Raymond A. Meijer
2004-06-03 11:17 ` Raymond A. Meijer
2004-06-03 12:51 ` Raymond A. Meijer
2004-06-03 14:04 ` Raymond A. Meijer
2004-06-03 14:30 ` Alex Zarochentsev
2004-06-03 15:22 ` Alex Zarochentsev
2004-06-04 7:29 ` Raymond A. Meijer
2004-06-04 9:44 ` Raymond A. Meijer
2004-06-04 9:54 ` Alex Zarochentsev
-- strict thread matches above, loose matches on Subject: below --
2004-06-04 12:14 Marcel Hilzinger
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=20040602163444.GG8091@backtop.namesys.com \
--to=zam@namesys.com \
--cc=mjt@nysv.org \
--cc=reiserfs-list@namesys.com \
--cc=rmeijer@internet.gr \
/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.