From: Eric Sandeen <sandeen@sandeen.net>
To: Barry Naujok <bnaujok@sgi.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: qa 166 failure on f8 kernel
Date: Tue, 07 Aug 2007 23:18:10 -0500 [thread overview]
Message-ID: <46B94402.5090801@sandeen.net> (raw)
In-Reply-To: <op.twp3lyi83jf8g2@pc-bnaujok.melbourne.sgi.com>
Barry Naujok wrote:
> On Wed, 08 Aug 2007 11:39:06 +1000, Eric Sandeen <sandeen@sandeen.net>
> wrote:
>
>> Posting this just in case it rings any bells, though I plan to
>> investigate...
>>
>> [root@inode xfstests]# ./check 166
>> FSTYP -- xfs (non-debug)
>> PLATFORM -- Linux/x86_64 inode 2.6.23-0.71.rc2.fc8
>> MKFS_OPTIONS -- -f -bsize=4096 /dev/sdb6
>> MOUNT_OPTIONS -- /dev/sdb6 /mnt/sdb6
>>
>> 166 - output mismatch (see 166.out.bad)
>> 2,6c2,7
>> < 0: [0..31]: XX..YY AG (AA..BB) 32
>> < 1: [32..127]: XX..YY AG (AA..BB) 96 10000
>> < 2: [128..159]: XX..YY AG (AA..BB) 32
>> < 3: [160..223]: XX..YY AG (AA..BB) 64 10000
>> < 4: [224..255]: XX..YY AG (AA..BB) 32
>> ---
>>> /mnt/sdb6/test_file: XX..YY AG (AA..BB)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> I suspect this line is appearing in the output due to a number
> in the mountpoint. I think the _filter_blocks() is only
> extracting lines with numbers in it.
Bingo. Yep, changing it to /mnt/foo, plus my change to the test,
passes. thanks!
-Eric
prev parent reply other threads:[~2007-08-08 4:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 1:39 qa 166 failure on f8 kernel Eric Sandeen
2007-08-08 2:56 ` David Chinner
2007-08-08 2:58 ` Eric Sandeen
2007-08-08 4:08 ` David Chinner
2007-08-08 4:11 ` Eric Sandeen
2007-08-08 4:16 ` Eric Sandeen
2007-08-08 4:19 ` David Chinner
2007-08-08 4:28 ` Eric Sandeen
2007-08-08 4:57 ` Barry Naujok
2007-08-08 5:00 ` Eric Sandeen
2007-08-08 13:13 ` Christoph Hellwig
2007-08-08 13:17 ` David Chinner
2007-08-08 4:13 ` Alex Elder
[not found] ` <D59801BCA402F5418C040937230AF7E00B9A8E@mtv-amer002e--3.americas.sgi.c om>
2007-08-08 5:47 ` nscott
2007-08-08 4:19 ` Barry Naujok
2007-08-08 4:18 ` Eric Sandeen [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=46B94402.5090801@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bnaujok@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