Mailing List
Home
Forum Home
Linux - General Red Hat Linux discussion list
Installation - Getting started with Red Hat Linux
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
application/x mplayer2 plugin
RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
Command stream end of file while reading
X Windows problem (xauth)
Upgrading openoffice 1 1 rpm
FTP: connection refused
FTP: connection refused
mount: /dev/cdrom: is not a valid block device
Dell Precision 650, RedHat 9, no sound
how to trace the cause resulting in the crash of bind server
Virus on the list
UNINSTALL RPM MYSQL
usb pen drives: mounting as a user
broadcom network interface
make mrproper
sendmail configuration on redhat
Couldn 't open PID file /var/run/named/named pid Permission denied
Promise 378 controller
kernel 2 6 and /dev/sound/mixer not found
Problem using up2date
mrtg step by step howto/configuration for a newbie?
Compiling and Installing Kernel 2 6
Can 't locate module ppp0, can 't locate module ppp compress 21
HOW I CAN MAKE BOOTABLE FLOPPY DISKET
Lotus Notes under Wine
/etc/security/limits conf question
Intel E/1000 driver
Command stream end of file while reading
rpm database corrupt
qla2300 modules
 
help deciphering kernel message

help deciphering kernel message

2006-01-03       - By David L. Parsley

 Back
Reply:     1     2     3  

On Tue, 2006-01-03 at 08:45 -0500, Marc Wiatrowski wrote:
> We have a box that has been running for over a year now with out problems but
as
> of the past week or so has been getting syslog messages like the following.  
>
> Jan  3 01:50:01 serverx kernel: attempt to access beyond end of device
> Jan  3 01:50:01 serverx kernel: 08:13: rw=1, want=1038022788, limit=34869082
>
> They occur at seem to be random times, sometimes hours apart, sometimes days.
 
>
> I am assuming its disk related and is the following device?
>
> $ ls -al /dev/sda13
> brw-rw----    1 root     disk       8,  13 Jun 24  2004 /dev/sda13
>
> But my partitions are:
>
> $ cat /proc/partitions
> major minor  #blocks  name     rio rmerge rsect ruse wio wmerge wsect wuse
running use aveq
[snip]
>    8    19   34869082 sdb3 5100492 44303847 391471498 4728847 124716687
159852667 2302155210
> 18012729 0 911964 13787807

> So I guess my question is, how would I find out what 8:13 is?

8:13 is hexadecimal - that would be the 8, 19 decimal device, sdb3.
Another clue is going beyond the limit of 34869082, shown above for
sdb3.

A quick google found two possible causes: filesystem corruption -
metadata referencing beyond the end of the disk; or bad RAM, causing
problems accessing swap.

regards,
  David

>
> thanks,
> marc
>
>
> --
> Taroon-list mailing list
> Taroon-list@(protected)
> https://www.redhat.com/mailman/listinfo/taroon-list

--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list