FS/XFS testing framework
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: fstests@vger.kernel.org
Cc: josef@toxicpanda.com, David Sterba <dsterba@suse.com>
Subject: [PATCH 4/6] generic/269: require no compression
Date: Fri, 17 May 2024 00:12:48 +0200	[thread overview]
Message-ID: <ea5a2c054381fccd48bdf5dd987247a0c6bd55fe.1715896529.git.dsterba@suse.com> (raw)
In-Reply-To: <cover.1715896529.git.dsterba@suse.com>

From: Josef Bacik <josef@toxicpanda.com>

This is meant to test ENOSPC, but we're dd'ing /dev/zero, which won't
fill up anything with compression on.

Additionally we're killing dd and then immediately trying to unmount.
With compression we could have references to the inode being held by the
async compression workers, so sometimes this will fail with EBUSY on the
unmount.

Make it easier on us and just skip this if we have compression enabled.

Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Signed-off-by: David Sterba <dsterba@suse.com>
---
 tests/generic/269 | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/tests/generic/269 b/tests/generic/269
index b7cdecd94f219a..6ee0cb04581632 100755
--- a/tests/generic/269
+++ b/tests/generic/269
@@ -11,6 +11,9 @@ _begin_fstest auto rw prealloc ioctl enospc stress
 
 # Import common functions.
 . ./common/filter
+
+_require_no_compress
+
 # Disable all sync operations to get higher load
 FSSTRESS_AVOID="$FSSTRESS_AVOID -ffsync=0 -fsync=0 -ffdatasync=0"
 _workout()
-- 
2.45.0


  parent reply	other threads:[~2024-05-16 22:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 22:12 [PATCH 0/6] Btrfs test updates and fixups David Sterba
2024-05-16 22:12 ` [PATCH 1/6] common: udev settle before _scratch_pool_mkfs David Sterba
2024-05-17 21:57   ` Anand Jain
2024-05-20 19:21     ` David Sterba
2024-05-20 23:48       ` Anand Jain
2024-05-16 22:12 ` [PATCH 2/6] generic/352: require no compression David Sterba
2024-05-21  0:04   ` Anand Jain
2024-05-16 22:12 ` [PATCH 3/6] generic/027: " David Sterba
2024-05-21  0:09   ` Anand Jain
2024-05-16 22:12 ` David Sterba [this message]
2024-05-21  0:37   ` [PATCH 4/6] generic/269: " Anand Jain
2024-05-21 18:29     ` David Sterba
2024-05-16 22:12 ` [PATCH 5/6] btrfs/011: mkfs the scratch dev before exiting David Sterba
2024-05-17 15:37   ` Darrick J. Wong
2024-05-20 19:18     ` David Sterba
2024-05-16 22:12 ` [PATCH 6/6] btrfs/{140,141}: verify read-repair test data by md5sum David Sterba
2024-05-23 15:31   ` Anand Jain
2024-05-23 15:35 ` [PATCH 0/6] Btrfs test updates and fixups Anand Jain

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=ea5a2c054381fccd48bdf5dd987247a0c6bd55fe.1715896529.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=fstests@vger.kernel.org \
    --cc=josef@toxicpanda.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