All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Max Power <ratty@they.org>
Cc: reiserfs-list@namesys.com
Subject: Re: (yet another) attempt to access beyond end of device
Date: Wed, 21 Aug 2002 13:33:03 +0400	[thread overview]
Message-ID: <20020821133303.A12839@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0208210204460.16503-100000@ns.they.org>

Hello!

On Wed, Aug 21, 2002 at 02:26:18AM -0700, Max Power wrote:

> # > Aug 21 00:33:46 stroke kernel: attempt to access beyond end of device
> # > Aug 21 00:33:46 stroke kernel: 16:41: rw=0, want=1411977092, (=0x54290f84), limit=1411977092
> # > I've tried all manor of reiserfscking repeatedly. Each time it seems to
> # > fix something different. I've read about the issues with fdisk and not
> # > rebooting and admit that this _could_ be my issue but that doesn't explain
> # > why all the "want" and "limit" numbers are identical. I'm also curious why
> # What do you mean by "identical"? I see they are different each time and this is
> # very strance since limit should be always the same.
> I was referring to the per-line sameness. In some of the mail list
> archives I looked thru the "want" number was different than the "limit"
> number each time. Mine are the same. And I don't get why if I "want" X and
> the "limit" is X then why can't I have X?

Ah, I see now. Very strange indeed. Can you try some stock kernel (say 2.4.19)
and see what happens there because I am not familiar with what is in
Mandrake kernels.

Bye,
    Oleg

      reply	other threads:[~2002-08-21  9:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-21  8:28 (yet another) attempt to access beyond end of device Max Power
2002-08-21  8:40 ` Oleg Drokin
2002-08-21  9:26   ` Max Power
2002-08-21  9:33     ` Oleg Drokin [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=20020821133303.A12839@namesys.com \
    --to=green@namesys.com \
    --cc=ratty@they.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.