From: Justin Pryzby <justinpryzby@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Subject: attempt to access beyond end of device
Date: Thu, 05 Dec 2002 13:54:23 -0500 [thread overview]
Message-ID: <E18K18h-0005Ru-00@perseus.homeunix.net> (raw)
2.4.20-ac1, Debian testing.
While running `updatedb --localuser=nobody 2>/dev/null`, I receive several pages of the following message:
Dec 5 13:43:25 perseus kernel: Directory sread (sector 0x18) failed
Dec 5 13:43:25 perseus kernel: attempt to access beyond end of device
Dec 5 13:43:25 perseus kernel: 02:00: rw=0, want=12, limit=4
Some of the numbers are different sometimes. I can post my syslog if anyone is interested, but I'm not even sure if this is a kernel issue.
Disk configuration is as follows:
pryzbyj@perseus:~$ mount
/dev/hda1 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
/dev/hda3 on /home type ext3 (rw)
/dev/hda4 on /usr/src type ext3 (rw)
Justin
next reply other threads:[~2002-12-05 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 18:54 Justin Pryzby [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-06 5:21 Justin Pryzby
2000-12-07 15:56 Jan Niehusmann
2000-12-07 16:34 ` Andries Brouwer
2000-12-07 17:10 ` John Kennedy
2000-11-24 9:02 Janek
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=E18K18h-0005Ru-00@perseus.homeunix.net \
--to=justinpryzby@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®