xfs
[Top] [All Lists]

Re: [PATCH] xfstests/071 FAIL with pwrite64: Invalid argument

To: Peng Haitao <penght@xxxxxxxxxxxxxx>
Subject: Re: [PATCH] xfstests/071 FAIL with pwrite64: Invalid argument
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 4 Jan 2012 11:53:41 -0500
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, hch@xxxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <4EE02022.5000403@xxxxxxxxxxxxxx>
References: <4EDD8F16.4050402@xxxxxxxxxxxxxx> <20111206110533.GD28326@dastard> <4EDF2133.7030702@xxxxxxxxxxxxxx> <20111207100748.GB14273@dastard> <4EE02022.5000403@xxxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Thu, Dec 08, 2011 at 10:25:38AM +0800, Peng Haitao wrote:
> 
> Dave Chinner said the following on 2011-12-7 18:07:
> > 
> > I think you misunderstand what I was saying - I was not suggesting
> > removing the error messages at all, just filtering them with sed to
> > ensure the output is always constant for the error different
> > messages different platforms dump out.
> > 
> 
> Thanks for your reply.
> Sorry for misunderstanding your comments.
> 
> I make a new patch, please review, thanks.

This still fails in my 32-bit test VM:

--- 071.out     2009-05-10 16:48:46.000000000 +0000
+++ 071.out.bad 2012-01-04 16:47:05.000000000 +0000
@@ -40,14 +40,14 @@
 
  
 Writing 512 bytes, offset is +0 (direct=false)
-pwrite64: File too large
+wrote 512/512 bytes at offset <OFFSET>
 Reading 512 bytes (direct=false)
-read 0/512 bytes at offset <OFFSET>
+read 512/512 bytes at offset <OFFSET>

and so on

<Prev in Thread] Current Thread [Next in Thread>