FS/XFS testing framework
 help / color / mirror / Atom feed
From: Pankaj Raghav <p.raghav@samsung.com>
To: fstests@vger.kernel.org, zlang@redhat.com
Cc: linux-xfs@vger.kernel.org, gost.dev@samsung.com,
	mcgrof@kernel.org, p.raghav@samsung.com, kernel@pankajraghav.com,
	david@fromorbit.com, djwong@kernel.org
Subject: [PATCH 0/2] fix generic quota tests for XFS with 32k and 64k block sizes
Date: Thu, 24 Oct 2024 13:23:09 +0200	[thread overview]
Message-ID: <20241024112311.615360-1-p.raghav@samsung.com> (raw)

Fixes to generic quota tests for XFS with 32k and 64k block sizes. The
tests are failing for bigger block sizes due to minimum allocation unit > IO size
or the way default delayed allocation works.

I have tested this on both 4k and 64k page size systems.

Pankaj Raghav (2):
  generic/219: use filesystem blocksize while calculating the file size
  generic: increase file size to match CoW delayed allocation for XFS
    64k bs

 tests/generic/219     | 18 +++++++++++++++---
 tests/generic/305     |  2 +-
 tests/generic/305.out | 12 ++++++------
 tests/generic/326     |  2 +-
 tests/generic/326.out | 12 ++++++------
 tests/generic/328     |  2 +-
 tests/generic/328.out | 16 +++++++++-------
 7 files changed, 39 insertions(+), 25 deletions(-)


base-commit: 891f4995ab07ee0a07eca156915ed87ab5f479f6
-- 
2.44.1


             reply	other threads:[~2024-10-24 11:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 11:23 Pankaj Raghav [this message]
2024-10-24 11:23 ` [PATCH 1/2] generic/219: use filesystem blocksize while calculating the file size Pankaj Raghav
2024-10-24 18:19   ` Darrick J. Wong
2024-10-25  1:12     ` Pankaj Raghav (Samsung)
2024-10-25  5:28       ` Darrick J. Wong
2024-10-24 11:23 ` [PATCH 2/2] generic: increase file size to match CoW delayed allocation for XFS 64k bs Pankaj Raghav
2024-10-24 18:17   ` Darrick J. Wong
2024-10-25  3:23     ` Pankaj Raghav (Samsung)

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=20241024112311.615360-1-p.raghav@samsung.com \
    --to=p.raghav@samsung.com \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=gost.dev@samsung.com \
    --cc=kernel@pankajraghav.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=zlang@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