public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Tinguely <tinguely@sgi.com>
To: "Michael L. Semon" <mlsemon35@gmail.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: v2 xfs directory unbalance assert test
Date: Wed, 18 Sep 2013 12:43:20 -0500	[thread overview]
Message-ID: <5239E638.4060908@sgi.com> (raw)
In-Reply-To: <CAJzLF9kacDY3gu7moxfFDRMTCxjQOzp_574Ojagk-kvNySedfg@mail.gmail.com>

On 09/18/13 11:36, Michael L. Semon wrote:
> Looks good.  I tried it on an 11-GB partition with an unpatched git kernel
> 3.12.0 + xfs-oss/master, coupled with the latest git xfsprogs.  It took a
> reasonable amount of time, relatively speaking.  It put forth the error I was
> expecting, and a new 32-bit core is available upon your request but not
> uploaded yet.
>
> As for the assert itself, according to kgdb, these are the first, last, and
> BBTOB(bp->b_length) numbers for this run:
>
> 1544 4591 4096
>
> Good work!
>
> Michael

Thanks for the feedback.

last > BBTOB(bp->b_length) was also true for the longer version of the 
test. The only difference is that it happens earlier in the remove.

I take a closer look at the code.

--Mark.

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

  reply	other threads:[~2013-09-18 17:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17 19:25 [PATCH] xfstests: v2 xfs directory unbalance assert test Mark Tinguely
2013-09-17 19:37 ` Eric Sandeen
2013-09-17 20:03   ` Mark Tinguely
2013-09-17 21:34 ` Dave Chinner
2013-09-17 21:35   ` Eric Sandeen
2013-09-17 22:14     ` Mark Tinguely
2013-09-18 16:36 ` Michael L. Semon
2013-09-18 17:43   ` Mark Tinguely [this message]
2013-09-23 23:30 ` Dave Chinner

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=5239E638.4060908@sgi.com \
    --to=tinguely@sgi.com \
    --cc=mlsemon35@gmail.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