linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Mary Edie Meredith <maryedie@osdl.org>,
	linux-kernel@vger.kernel.org, jenny@osdl.org
Subject: Re: Nick's scheduler v18
Date: Fri, 14 Nov 2003 16:45:36 +1100	[thread overview]
Message-ID: <3FB46C00.6050104@cyberone.com.au> (raw)
In-Reply-To: <20031113113906.65431b18.akpm@osdl.org>



Andrew Morton wrote:

>Mary Edie Meredith <maryedie@osdl.org> wrote:
>
>>Nick,
>>
>>We ran your patch on STP against one of our database workloads (DBT3 on
>>postgreSQL which uses file system rather than raw).
>>
>>The test was able to compile, successfully start up the database,
>>successfully load the database from source file, successfully run the
>>power test (single stream update/query/delete).   
>>
>>It failed, however at the next stage, where it starts 8 streams of query
>>and one stream of updates/deletes where it ran for approximately 40
>>minutes (usually takes over an hour to complete).  The updates appear to
>>have completed and only queries were active at the time of failure.  See
>>the error message below from the database log.
>>
>>...
>>
>>PANIC:  fdatasync of log file 1, segment 81 failed: Input/output error
>>
>>
>
>It's hard to see how a CPU scheduler change could cause fdatasync() to
>return EIO.
>
>What filesystem was being used?
>
>If it was ext2 then perhaps you hit the recently-fixed block allocator
>race.  That fix was merged after test9.  Please check the kernel logs for
>any filesystem error messages.
>

The kernel tested was test9-bk14 + my patch.

I don't think it would be due to a problem my patch. Perhaps different
scheduling patterns made some race more likely though.

>
>Also, please retry the run, see if it is repeatable.
>

I will let someone else take over from here ;) I'll run the test
again with the latest bk when I submit another round of STP tests
sometime.



  parent reply	other threads:[~2003-11-14  5:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10 17:20 Nick's scheduler v18 Nick Piggin
2003-11-13 18:07 ` Mary Edie Meredith
2003-11-13 19:39   ` Andrew Morton
2003-11-13 22:27     ` Mike Fedyk
2003-11-14 10:34       ` Sven Luther
2003-11-14  5:45     ` Nick Piggin [this message]
2003-11-13 21:30 ` Martin J. Bligh
2003-11-14  2:12   ` Nick Piggin
     [not found] <1068589319.1557.1.camel@localhost.localdomain>
2003-11-11 22:30 ` Tom Sightler
2003-11-12  0:38   ` Nick Piggin

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=3FB46C00.6050104@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=akpm@osdl.org \
    --cc=jenny@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maryedie@osdl.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).