From: Christoph Hellwig <hch@lst.de>
To: David Chinner <dgc@sgi.com>
Cc: Christoph Hellwig <hch@lst.de>, xfs@oss.sgi.com
Subject: Re: new xfsqa mismatches
Date: Tue, 8 Apr 2008 12:41:53 +0200 [thread overview]
Message-ID: <20080408104152.GA23535@lst.de> (raw)
In-Reply-To: <20080407215539.GC108924158@sgi.com>
On Tue, Apr 08, 2008 at 07:55:39AM +1000, David Chinner wrote:
> If other ppl sent xfsqa patches to the oss list, then you'd see that
> a patch to fix this was sent out for review yesterday....
Seen the commit now, but yes folks please send more patches to the list
for review!
> > 130 and 132 expetect Bytes in various places but get bytes from xfs_io
> > from CVS
>
> What's the error output? I've not seen that one....
130 [ 72.086853] XFS mounting filesystem hdd
- output mismatch (see 130.out.bad)
20c20
< XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
---
> 3 KiB, 1 ops; 0.0000 sec (inf EiB/sec and inf ops/sec)
24c24
< XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
---
> 1000.000000 bytes, 1 ops; 0.0000 sec (inf EiB/sec and inf ops/sec)
and so one for lots of lines
prev parent reply other threads:[~2008-04-08 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 10:01 new xfsqa mismatches Christoph Hellwig
2008-04-07 21:55 ` David Chinner
2008-04-08 10:41 ` Christoph Hellwig [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=20080408104152.GA23535@lst.de \
--to=hch@lst.de \
--cc=dgc@sgi.com \
--cc=xfs@oss.sgi.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