All of lore.kernel.org
 help / color / mirror / Atom feed
From: Naohiro Aota <naohiro.aota@wdc.com>
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, Naohiro Aota <naohiro.aota@wdc.com>
Subject: [PATCH v2 0/8] fstests: add checks for testing zoned btrfs
Date: Thu, 12 Aug 2021 00:12:24 +0900	[thread overview]
Message-ID: <20210811151232.3713733-1-naohiro.aota@wdc.com> (raw)

This series revisit my old series to test zoned btrfs [1].

[1] https://lore.kernel.org/fstests/PH0PR04MB7416870032582BC2A8FC5AD99B299@PH0PR04MB7416.namprd04.prod.outlook.com/T/

Several tests are failing on zoned btrfs, but actually they are invalid.
There are two reasons of the failures. One is creating too small
filesystem. Since zoned btrfs needs at lease 5 zones (= 1.25 GB if zone
size = 256MB) to create a filesystem, tests creating e.g., 1 GB filesystem
will fail.

The other reason is lacking of zone support of some dm targets and loop
device. So, they need to skip the test if the testing device is zoned.

Patches 1 to 4 handle the too small file system failure.

And, patches 5 to 8 add checks for tests requiring non-zoned devices.

Naohiro Aota (8):
  common/rc: introduce minimal fs size check
  common/rc: fix blocksize detection for btrfs
  btrfs/057: use _scratch_mkfs_sized to set filesystem size
  fstests: btrfs: add minimal file system size check
  common: add zoned block device checks
  shared/032: add check for zoned block device
  fstests: btrfs: add checks for zoned block device
  fstests: generic: add checks for zoned block device

 README            |  4 ++++
 common/btrfs      | 18 ++++++++++++++++++
 common/dmerror    |  3 +++
 common/dmhugedisk |  3 +++
 common/rc         | 24 +++++++++++++++++++++++-
 tests/btrfs/003   | 13 +++++++++----
 tests/btrfs/011   | 21 ++++++++++++---------
 tests/btrfs/012   |  2 ++
 tests/btrfs/023   |  2 ++
 tests/btrfs/049   |  2 ++
 tests/btrfs/057   |  2 +-
 tests/btrfs/116   |  2 ++
 tests/btrfs/124   |  4 ++++
 tests/btrfs/125   |  2 ++
 tests/btrfs/131   |  2 ++
 tests/btrfs/136   |  2 ++
 tests/btrfs/140   |  2 ++
 tests/btrfs/141   |  1 +
 tests/btrfs/142   |  1 +
 tests/btrfs/143   |  1 +
 tests/btrfs/148   |  2 ++
 tests/btrfs/150   |  1 +
 tests/btrfs/151   |  1 +
 tests/btrfs/156   |  1 +
 tests/btrfs/157   |  3 +++
 tests/btrfs/158   |  3 +++
 tests/btrfs/175   |  1 +
 tests/btrfs/194   |  2 +-
 tests/btrfs/195   |  8 ++++++++
 tests/btrfs/197   |  1 +
 tests/btrfs/198   |  1 +
 tests/btrfs/215   |  1 +
 tests/btrfs/236   | 33 ++++++++++++++++++++-------------
 tests/generic/108 |  1 +
 tests/generic/471 |  1 +
 tests/generic/570 |  1 +
 tests/shared/032  |  2 ++
 37 files changed, 145 insertions(+), 29 deletions(-)

-- 
2.32.0


             reply	other threads:[~2021-08-11 15:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 15:12 Naohiro Aota [this message]
2021-08-11 15:12 ` [PATCH v2 1/8] common/rc: introduce minimal fs size check Naohiro Aota
2021-08-11 15:12 ` [PATCH v2 2/8] common/rc: fix blocksize detection for btrfs Naohiro Aota
2021-08-11 15:12 ` [PATCH v2 3/8] btrfs/057: use _scratch_mkfs_sized to set filesystem size Naohiro Aota
2021-08-11 15:12 ` [PATCH v2 4/8] fstests: btrfs: add minimal file system size check Naohiro Aota
2021-08-11 15:12 ` [PATCH v2 5/8] common: add zoned block device checks Naohiro Aota
2021-08-15 14:42   ` Eryu Guan
2021-08-16  6:06     ` Naohiro Aota
2021-08-11 15:12 ` [PATCH v2 6/8] shared/032: add check for zoned block device Naohiro Aota
2021-08-11 15:12 ` [PATCH v2 7/8] fstests: btrfs: add checks " Naohiro Aota
2021-08-15 15:12   ` Eryu Guan
2021-08-16  6:10     ` Naohiro Aota
2021-08-11 15:12 ` [PATCH v2 8/8] fstests: generic: " Naohiro Aota
2021-08-15 15:20   ` Eryu Guan
2021-08-16  6:19     ` Naohiro Aota
2021-08-12 15:41 ` [PATCH v2 0/8] fstests: add checks for testing zoned btrfs David Sterba
2021-08-15 15:21 ` 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=20210811151232.3713733-1-naohiro.aota@wdc.com \
    --to=naohiro.aota@wdc.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.