public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] dma_intr errors on heavy writes -- cause for concern?
Date: Tue, 31 Oct 2006 21:08:35 -0700	[thread overview]
Message-ID: <7573e9640610312008w47d42e04xb6422f84a344e526@mail.gmail.com> (raw)
In-Reply-To: <324505.14222.qm@web31801.mail.mud.yahoo.com>

On 10/31/06, Richard Broersma Jr <rabroersma@yahoo.com> wrote:
> During certain times I my server under goes heavy disc writes.  When this happen I get the
> following error.  Should I be concerned?  Does anyone know of any resources that I can read up on
> that will explain that all of this mean?

I don't have any resources, but my understanding is that LBAsect is
the logical sector of the block device (i.e, the raid array), while
sector is the physical sector of disk.  LBAsect looks
suspicious...referencing a sector that is somewhere around the 91
petabytes address.  You didn't mention how large the disks are, but
even there they are requesting a sector that is about 220G from the
beginning of the disk, and returning that no such sector exists
(SectorIdNotFound).

So my guess is that your filesystem is getting confused under load,
and trying to access stuff that is beyond the end of your raid array.
So, which fs and kernel version?

-Richard
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-11-01  4:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01  1:08 [gentoo-user] dma_intr errors on heavy writes -- cause for concern? Richard Broersma Jr
2006-11-01  1:32 ` Hemmann, Volker Armin
2006-11-01  7:22   ` Alan
2006-11-01 18:09     ` Hemmann, Volker Armin
2006-11-01  4:08 ` Richard Fish [this message]
2006-11-01  6:14   ` Richard Broersma Jr
2006-11-01  8:16     ` Richard Fish

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=7573e9640610312008w47d42e04xb6422f84a344e526@mail.gmail.com \
    --to=bigfish@asmallpond.org \
    --cc=gentoo-user@lists.gentoo.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