From: Andy Whitcroft <apw@shadowen.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Martin Bligh <mbligh@google.com>,
Eric Dumazet <dada1@cosmosbay.com>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: xfs fails dbench in 2.6.18-rc1-mm1
Date: Thu, 13 Jul 2006 15:42:01 +0100 [thread overview]
Message-ID: <44B65BB9.9040303@shadowen.org> (raw)
In-Reply-To: <1152751411.22840.3.camel@dyn9047017100.beaverton.ibm.com>
Badari Pulavarty wrote:
> On Wed, 2006-07-12 at 13:26 -0700, Martin Bligh wrote:
>> Badari Pulavarty wrote:
>>> Martin Bligh wrote:
>>>
>>>> Eric Dumazet wrote:
>>>>
>>>>> On Wednesday 12 July 2006 18:58, Martin Bligh wrote:
>>>>>
>>>>>> http://test.kernel.org/abat/40891/debug/test.log.1
>>>>>>
>>>>>> Filesystem type for /mnt/tmp is xfs
>>>>>> write failed on handle 13786
>>>>>> 4 clients started
>>>>>> Child failed with status 1
>>>>>> write failed on handle 13786
>>>>>> write failed on handle 13786
>>>>>> write failed on handle 13786
>>>>>>
>>>>>> Works fine in -git4
>>>>>> All other fs's seemed to run OK.
>>>>>>
>>>>>> Machine is a 4x Opteron.
>
> Sorry !! its my screw up again :(
> Here is the patch to fix it.
>
> Thanks,
> Badari
>
> Fix a bug in __xfs_file_write() which is causing writes to fail
> with -EINVAL.
>
> Signed-off-by: Badari Pulavarty <pbadari@us.ibm.com>
Ok, I've thrown this one + apkm's latest fix into the tester. Only one
result in so far, but that is our first good on that machine.
-apw
prev parent reply other threads:[~2006-07-13 14:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 16:58 xfs fails dbench in 2.6.18-rc1-mm1 Martin Bligh
2006-07-12 17:12 ` Eric Dumazet
2006-07-12 17:36 ` Andy Whitcroft
2006-07-12 20:13 ` Martin Bligh
2006-07-12 20:25 ` Badari Pulavarty
2006-07-12 20:26 ` Martin Bligh
2006-07-12 21:32 ` Badari Pulavarty
2006-07-12 21:31 ` Martin Bligh
2006-07-12 21:53 ` Keith Mannthey
2006-07-13 0:43 ` Badari Pulavarty
2006-07-13 14:42 ` Andy Whitcroft [this message]
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=44B65BB9.9040303@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@osdl.org \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=pbadari@us.ibm.com \
/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