All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Ben Myers <bpm@sgi.com>
Cc: Eric Sandeen <sandeen@redhat.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstest 285: userspace vs. fragmented multiblock dir2
Date: Wed, 6 Jun 2012 09:48:03 +1000	[thread overview]
Message-ID: <20120605234803.GE22848@dastard> (raw)
In-Reply-To: <20120605224600.GN4721@sgi.com>

On Tue, Jun 05, 2012 at 05:46:00PM -0500, Ben Myers wrote:
> Hey Eric,
> 
> On Mon, May 21, 2012 at 05:05:53PM -0500, Eric Sandeen wrote:
> > Current xfs_repair is unhappy with fragmented multiblock
> > v2 directories.  This test shows it ... patches to fix
> > it soon to follow.
> > 
> > Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> 
> This failed on my system... looks like it's just PEBKAC.  My partitions
> are too small?
> 
> # ./check 287
> No patches applied
> KERNEL_TOPDIR -- /root/xfs
> BRANCH        -- refs/heads/master2
> DESC          -- v3.4-10158-gf8f5701
> PATCHES:
> FSTYP         -- xfs (debug)
> PLATFORM      -- Linux/x86_64 nfs10 3.5.0-rc1-0.7-default+
> MKFS_OPTIONS  -- -f -bsize=4096 /dev/sdb4
> MOUNT_OPTIONS -- /dev/sdb4 /mnt/scratch
> 
> 287      - no qualified output

It failed because there is not 287.out file in the patch. Every test
has to have a golden image to compare the result against...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-06-05 23:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21 22:05 [PATCH] xfstest 285: userspace vs. fragmented multiblock dir2 Eric Sandeen
2012-06-05 22:46 ` Ben Myers
2012-06-05 23:48   ` Dave Chinner [this message]
2012-06-06  0:57     ` Eric Sandeen
2012-06-06  2:29 ` [PATCH V2] xfstest 287: " Eric Sandeen
2012-11-20 15:28   ` Mark Tinguely

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=20120605234803.GE22848@dastard \
    --to=david@fromorbit.com \
    --cc=bpm@sgi.com \
    --cc=sandeen@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.