From: Martin Bligh <mbligh@google.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>, Andy Whitcroft <apw@shadowen.org>
Subject: xfs fails dbench in 2.6.18-rc1-mm1
Date: Wed, 12 Jul 2006 09:58:01 -0700 [thread overview]
Message-ID: <44B52A19.3020607@google.com> (raw)
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.
next reply other threads:[~2006-07-12 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 16:58 Martin Bligh [this message]
2006-07-12 17:12 ` xfs fails dbench in 2.6.18-rc1-mm1 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
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=44B52A19.3020607@google.com \
--to=mbligh@google.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@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