FS/XFS testing framework
 help / color / mirror / Atom feed
From: Zhenyu Zhang <zhenyzha12@gmail.com>
To: fstests@vger.kernel.org
Cc: zhenyzha@redhat.com, hshuai@redhat.com, gshan@redhat.com,
	shahuang@redhat.com, lijin@redhat.com
Subject: Confirm xfstest + nfs generic/568 failure issue
Date: Wed,  7 Jun 2023 01:17:09 -0400	[thread overview]
Message-ID: <20230607062851.256699-1-zhenyzha12@gmail.com> (raw)

Hello all,

Sorry to bother you.
When I run generic/568 on 64k kernel, I hit the following error:
 Sending command: ./check -virtiofs generic/568
 2023-06-05 05:33:10,297 avocado.test INFO | FSTYP         -- virtiofs
 PLATFORM      -- Linux/aarch64 localhost 5.14.0-319.el9.aarch64+64k #1 SMP PREEMPT_DYNAMIC Thu May 25 18:43:04 EDT 2023
 MKFS_OPTIONS  -- myfs2
 MOUNT_OPTIONS -- -o context=system_u:object_r:root_t:s0 myfs2 /mnt/myfs2
 
 generic/568       - output mismatch (see /home/xfstests-dev/results//generic/568.out.bad)
     --- tests/generic/568.out 2023-06-05 17:31:17.248857480 +0800
     +++ /home/xfstests-dev/results//generic/568.out.bad 2023-06-05 17:33:10.348857480 +0800
     @@ -1,4 +1,4 @@
      QA output created by 568
      wrote 2/2 bytes at offset block_size - 1
      XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
     -OK: File did not grow.
     +ERROR: File grew from 8192 B to 69632 B when writing to the fallocated range.
     ...
     (Run 'diff -u /home/xfstests-dev/tests/generic/568.out /home/xfstests-dev/results//generic/568.out.bad'  to see the entire diff)
 Ran: generic/568
 Failures: generic/568
 Failed 1 of 1 tests

My host and guest pagesize is 64k:
# getconf PAGESIZE
65536

I'm not sure if this is a product cache issue or a script issue.
I use --cache=never|always|none|auto both hit this issue

Best regards 
Zhenyu Zhang


                 reply	other threads:[~2023-06-07  5:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230607062851.256699-1-zhenyzha12@gmail.com \
    --to=zhenyzha12@gmail.com \
    --cc=fstests@vger.kernel.org \
    --cc=gshan@redhat.com \
    --cc=hshuai@redhat.com \
    --cc=lijin@redhat.com \
    --cc=shahuang@redhat.com \
    --cc=zhenyzha@redhat.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