linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: Jim Duchek <jim.duchek@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Array 'freezes' for some time after large writes?
Date: Tue, 30 Mar 2010 11:00:21 -0700	[thread overview]
Message-ID: <5bdc1c8b1003301100o39138befwb99ff4bdbb4dfe2c@mail.gmail.com> (raw)
In-Reply-To: <dead81ad1003301047t6be7b3b4r5bf70ad6317f9d1e@mail.gmail.com>

On Tue, Mar 30, 2010 at 10:47 AM, Jim Duchek <jim.duchek@gmail.com> wrote:
> Well it appears that I can absolutely reproduce it 100% of the time by
> copying a large (>1 gig) video file and then immediately playing it.
> It seems to hit the freeze on just about the same frame every time,
> and playing it seems to be necessary (it doesn't freeze if I just do
> the copy and go about my business).  Possibly an issue w/disk buffers?
>  You're having this happen even if the disk in question is not in an
> array?  If so perhaps it's an SATA issue and not a RAID one, and we
> should move this discussion accordingly.  I reproduced your steps and
> I'm seeing pretty much the same thing, although not quite hitting 100%
> wa (although I'm guessing it would if I shut everything else down --
> Got a full desktop running).
>
> I'm using a Biostar T41-A7 mobo, Intel Core 2 Quad Q8400 Yorkfield
> 2.66GHz 4MB L2, and 3 Western Digital Caviar Blue WD5000AAJS drives
> and 1 WD5002ABYS.  I note that the 3 older drives claim using ATA-7
> and the newer one says ATA-8. Any similarities?
>
> Jim
>

Intex DX58SO motherboard
6GB
i7 920
3 WD10EARS green 1TB (4K/sector)
nvidia 9500GT
2.6.32-gentoo kernel

In my setup (and being Gentoo based where we build everything from
scratch) I see this mostly when building code. I haven't copied any
large files yet but I'm not surprised at your report as my dmesg error
is about writes being blocked so that makes sense.

Closest similarity would be both motherboards are based on Intel
chipsets. SATA support is in the South Bridge.

Your motherboard chipset

North Bridge 	Intel G41
South Bridge 	Intel ICH7

My motherboard chipset

North Bridge  	Intel X58
South Bridge 	Intel ICH10R

You did see the same message about writes being block, correct?
Nothing else as of yet?


- Mark
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-03-30 18:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 17:07 Array 'freezes' for some time after large writes? Jim Duchek
2010-03-30 17:18 ` Mark Knecht
2010-03-30 17:47   ` Jim Duchek
2010-03-30 18:00     ` Mark Knecht [this message]
2010-03-30 18:05     ` Mark Knecht
2010-03-30 20:32       ` Jim Duchek
2010-03-30 20:45         ` Mark Knecht
2010-03-30 20:59           ` Jim Duchek
2010-03-30 22:21             ` Mark Knecht
2010-03-30 23:50               ` Mark Knecht
2010-03-31  0:22                 ` Jim Duchek
2010-03-31  1:35 ` Roger Heflin
2010-03-31 16:12   ` Mark Knecht
2010-03-31 16:25     ` Jim Duchek
2010-03-31 16:37 ` Asdo

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=5bdc1c8b1003301100o39138befwb99ff4bdbb4dfe2c@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=jim.duchek@gmail.com \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).