laundry dice:
attempt to access beyond end of device 08:01: rw=0, want=7583324, limit=3300336 dev 08:01 blksize=4096 blocknr=1075637654 sector=15166640 size=4096 count=1 attempt to access beyond end of device 08:01: rw=0, want=7583388, limit=3300336 dev 08:01 blksize=4096 blocknr=1075637670 sector=15166768 size=4096 count=1 attempt to access beyond end of device 08:01: rw=0, want=7583452, limit=3300336 dev 08:01 blksize=4096 blocknr=1075637686 sector=15166896 size=4096 count=1 attempt to access beyond end of device 08:01: rw=0, want=7583324, limit=3300336 dev 08:01 blksize=4096 blocknr=1075637654 sector=15166640 size=4096 count=1
che cos'e'?
la device 08,01 e' la sda1
kern.log e' vuoto.
bah.
laundry dice:
attempt to access beyond end of device 08:01: rw=0, want=7583324, limit=3300336 dev 08:01 blksize=4096 blocknr=1075637654 sector=15166640 size=4096 count=1 attempt to access beyond end of device 08:01: rw=0, want=7583388, limit=3300336 dev 08:01 blksize=4096 blocknr=1075637670 sector=15166768 size=4096 count=1 attempt to access beyond end of device 08:01: rw=0, want=7583452, limit=3300336 dev 08:01 blksize=4096 blocknr=1075637686 sector=15166896 size=4096 count=1 attempt to access beyond end of device 08:01: rw=0, want=7583324, limit=3300336 dev 08:01 blksize=4096 blocknr=1075637654 sector=15166640 size=4096 count=1
che cos'e'?
la device 08,01 e' la sda1
Io ho trovato questo:
what kernel version is this? if its 2.2.{10,11,12,13} upgrade it to 2.2.14 NOW! 2.2.10 (and/or 2.2.11) had a really NASTY filesystem corruption problem that manifested itself with the exact error you are seeing. 2.2.13 just trashes filesystems silently -- until the fs is so fs*ked that it starts generating other errors.
pretty much any kernel older then 2.2.5 or newer then 2.2.7 (i think) but older then 2.2.14 will likely destroy filesystems and cause all kinds of disk related hell.
if your kernel is up to date, then it might be hardware, but im not sure. the most common cause of those errors is buggy 2.2 series kernels.
Ciao Rick
On Mon, Jan 19, 2004 at 12:52:39PM +0100, Riccardo Bini wrote:
Io ho trovato questo:
what kernel version is this? if its 2.2.{10,11,12,13} upgrade it to 2.2.14 NOW! 2.2.10 (and/or 2.2.11) had a really NASTY filesystem corruption problem that manifested itself with the exact error you are seeing. 2.2.13 just trashes filesystems silently -- until the fs is so fs*ked that it starts generating other errors.
pretty much any kernel older then 2.2.5 or newer then 2.2.7 (i think) but older then 2.2.14 will likely destroy filesystems and cause all kinds of disk related hell.
if your kernel is up to date, then it might be hardware, but im not sure. the most common cause of those errors is buggy 2.2 series kernels.
il kernel al momento e' un 2.2.20, e non ci sono modi facili di farlo funzionare con altri kernel: con i 2.4 continua a dare errori (architettura hw strana?)..
comunque entro poco lo dismettiamo.. ora che e' arrivato ICCQSOACD!
ICCQSOACD = Il Computer Che Qualcuno Si Ostina A Chiamare Dodo
:)
On Mon, Jan 19, 2004 at 02:27:14PM +0100, marcogh@linux.it riflettendo wrote
comunque entro poco lo dismettiamo.. ora che e' arrivato ICCQSOACD!
ICCQSOACD = Il Computer Che Qualcuno Si Ostina A Chiamare Dodo
ma gh, dai un nome invece di continuare a dire "questo non mi piace"
:)
;)
ciao profe
-
marco ghidinelli -
marcogh＠linux.it
-
profe -
Riccardo Bini