From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>, fstests@vger.kernel.org
Subject: Re: [PATCH 1/4] filter: latest mkfs.xfs makes logical sector size noise
Date: Mon, 04 May 2015 17:45:48 -0500 [thread overview]
Message-ID: <5547F69C.6050009@sandeen.net> (raw)
In-Reply-To: <1430776893-25158-2-git-send-email-david@fromorbit.com>
On 5/4/15 5:01 PM, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> On devices that have a logical sector smaller than physical sector,
> this extra, harmless output now occurs:
>
> QA output created by 060
> +specified blocksize 1024 is less than device physical sector size 4096
> +switching to logical sector size 512
> Creating directory system to dump using src/fill.
> Setup .......................................
> Dumping to files...
>
> And it causes lots of tests to fail unnecessarily. Filter it.
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
But should we just remove that from mkfs output? It's probably my fault,
but looking at it now, it seems like unnecessary noise.
-Eric
> ---
> common/rc | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/common/rc b/common/rc
> index 6ea107e..242dedb 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -365,9 +365,12 @@ _scratch_mkfs_xfs()
> mkfs_status=$?
> fi
>
> - # output stored mkfs output
> - cat $tmp_dir.mkfserr >&2
> + # output stored mkfs output, filtering unnecessary warnings from stderr
> cat $tmp_dir.mkfsstd
> + cat $tmp_dir.mkfserr | sed \
> + -e '/less than device physical sector/d' \
> + -e '/switching to logical sector/d' \
> + >&2
> rm -f $tmp_dir.mkfserr $tmp_dir.mkfsstd
>
> return $mkfs_status
>
next prev parent reply other threads:[~2015-05-04 22:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 22:01 [PATCH 0/4] fstests: xfs utility output has changed Dave Chinner
2015-05-04 22:01 ` [PATCH 1/4] filter: latest mkfs.xfs makes logical sector size noise Dave Chinner
2015-05-04 22:45 ` Eric Sandeen [this message]
2015-05-04 22:01 ` [PATCH 2/4] filter: latest xfs_repair is more verbose Dave Chinner
2015-05-04 22:46 ` Eric Sandeen
2015-05-04 22:01 ` [PATCH 3/4] xfs/045: can't change UUID on v5 filesystems Dave Chinner
2015-05-04 22:48 ` Eric Sandeen
2015-05-05 0:51 ` Dave Chinner
2015-05-05 2:04 ` Eric Sandeen
2015-05-04 22:01 ` [PATCH 4/4] filter: inode size output of mkfs.xfs can change Dave Chinner
2015-05-05 2:06 ` Eric Sandeen
2015-05-05 5:34 ` Dave Chinner
2015-05-06 7:19 ` Eryu Guan
2015-05-06 22:56 ` Dave Chinner
2015-05-07 3:05 ` Eryu Guan
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=5547F69C.6050009@sandeen.net \
--to=sandeen@sandeen.net \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
/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