From: Martin Bligh <mbligh@google.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Eric Dumazet <dada1@cosmosbay.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Andy Whitcroft <apw@shadowen.org>
Subject: Re: xfs fails dbench in 2.6.18-rc1-mm1
Date: Wed, 12 Jul 2006 13:26:18 -0700 [thread overview]
Message-ID: <44B55AEA.1010608@google.com> (raw)
In-Reply-To: <44B55A9E.2010403@us.ibm.com>
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.
>>>
>>>
>>>
>>> You need to revert 92eb7a2f28d551acedeb5752263267a64b1f5ddf
>>
>>
>> Still fails (thanks Andy).
>>
> Wondering if its my changes :(
> Can you back out these and try ?
>
> Please, Please tell me that, its not me :)
>
> Thanks,
> Badari
>
> #
> vectorize-aio_read-aio_write-fileop-methods.patch
> remove-readv-writev-methods-and-use-aio_read-aio_write.patch
> streamline-generic_file_-interfaces-and-filemap.patch
> streamline-generic_file_-interfaces-and-filemap-ecryptfs.patch
You could submit a job to elm3b6 to run dbench on xfs ;-)
M.
next prev parent reply other threads:[~2006-07-12 20:28 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 [this message]
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
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=44B55AEA.1010608@google.com \
--to=mbligh@google.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--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