public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: John Bradford <john@grabjohn.com>
Cc: JG <jg@cms.ac>, linux-kernel@vger.kernel.org
Subject: Re: could someone plz explain those ext3/hard disk errors
Date: Wed, 18 Feb 2004 08:31:11 -0500	[thread overview]
Message-ID: <4033691F.7070804@tmr.com> (raw)
In-Reply-To: <200402091026.i19AQ15t000678@81-2-122-30.bradfords.org.uk>

John Bradford wrote:
>>now...hm, it all started when i upgraded from kernel 2.4.19 to 2.6.0
>>in late decemeber, the system worked very fine for a week or so
>>(having great response times!) but then all of a sudden the problems
>>started. 2 disks died. then my gigabit network card was only able to
>>transmit 200kb/s (but this was really a hardware problem, a new card
>>is working fine again, well...). a week later the next disks are
>>having problems and i have yet to RMA three disks. and now the next
>>two disks..., i'm getting insane ;) i can't see any EXT3 error anymore
>>*g* the next disks will be reiserfs only to see other error messages
>>;) well, but that doesn't solve the problem of 6 disks within 2
>>months...this is so unlikely.
> 
> 
> Please read the FAQ, fix your mail application - you are sending long
> lines, and don't break the CC list.
> 
> As to your problem, look at the LBA sector addresses in the error
> message:
> 
> 280923064991615
> 
> is your drive really over 100 EB?  No...

I think we could assume that (a) he never told the kernel the disk was 
"over 100 EB" and (b) the kernel was trying to use that LBA anyway. 
Which could be due to either a kernel bug or memory corruption (or CPU 
problems, but unlikely).

-- 
bill davidsen <davidsen@tmr.com>
   CTO TMR Associates, Inc
   Doing interesting things with small computers since 1979

  parent reply	other threads:[~2004-02-18 13:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-08 17:53 could someone plz explain those ext3/hard disk errors JG
2004-02-08 18:55 ` Micha Feigin
2004-02-08 19:05   ` JG
2004-02-09  1:47 ` Heriberto A Tejeda
2004-02-09  9:52   ` JG
2004-02-09 10:26     ` John Bradford
2004-02-09 11:06       ` JG
2004-02-18 13:31       ` Bill Davidsen [this message]
2004-02-18 14:42         ` John Bradford
2004-02-18 15:54           ` JG
2004-02-18 18:26           ` Bill Davidsen
2004-02-09 11:52     ` Gene Heskett
2004-02-18 13:41       ` Bill Davidsen

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=4033691F.7070804@tmr.com \
    --to=davidsen@tmr.com \
    --cc=jg@cms.ac \
    --cc=john@grabjohn.com \
    --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