linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz
Subject: [PATCH v4 0/4] mkfs: Fix minimal device check so that reported
Date: Wed,  1 Nov 2017 09:30:39 +0800	[thread overview]
Message-ID: <20171101013043.19294-1-wqu@suse.com> (raw)

Original reported by Wesley AC:
https://github.com/kdave/btrfs-progs/issues/70

Fix it by taking data/meta profile and minimal chunk size into
consideration.

Also introduce a test case for that.

Changelog:
v2:
  Refactor test_minimum_size() to take @min_dev_size directly. Refactor
  patch already in devel branch.
v3:
  Split test/common modification into separate patch.
v4:
  Further split run_mustfail_stdout() and prepare_test_dev()
  modification into separate patch.
  Include the real mkfs fix into patchset, to prevent possible test
  failure.
  Use suggestion from David to use run_check_mount_test_dev() and
  run_check_umount_test_dev().
  Add "-b $good_size" to mkfs command line, so we can see the size in
  test result, to help further debugging.

Qu Wenruo (4):
  btrfs-progs: mkfs: Enhance minimal device size calculation to fix mkfs
    failure on small file
  btrfs-progs: test/common: Introduce run_mustfail_stdout
  btrfs-progs: test/common: Enhance prepare_test_dev to reset device
    size
  btrfs-progs: test/mkfs: Test if the minimal device size is valid

 mkfs/common.c                            | 68 ++++++++++++++++++++++++++++----
 mkfs/common.h                            |  4 +-
 mkfs/main.c                              |  3 +-
 tests/common                             | 58 ++++++++++++++++++++++++++-
 tests/mkfs-tests/010-small-image/test.sh | 49 +++++++++++++++++++++++
 5 files changed, 171 insertions(+), 11 deletions(-)
 create mode 100755 tests/mkfs-tests/010-small-image/test.sh

-- 
2.14.3


             reply	other threads:[~2017-11-01  1:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01  1:30 Qu Wenruo [this message]
2017-11-01  1:30 ` [PATCH v4 1/4] btrfs-progs: mkfs: Enhance minimal device size calculation to fix mkfs failure on small file Qu Wenruo
2017-11-27 23:21   ` David Sterba
2017-11-28  0:40     ` Qu Wenruo
2017-11-28 12:32       ` David Sterba
2017-11-01  1:30 ` [PATCH v4 2/4] btrfs-progs: test/common: Introduce run_mustfail_stdout Qu Wenruo
2017-11-27 23:28   ` David Sterba
2017-11-01  1:30 ` [PATCH v4 3/4] btrfs-progs: test/common: Enhance prepare_test_dev to reset device size Qu Wenruo
2017-11-27 23:30   ` David Sterba
2017-11-01  1:30 ` [PATCH v4 4/4] btrfs-progs: test/mkfs: Test if the minimal device size is valid Qu Wenruo
2017-11-28 14:34   ` David Sterba

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=20171101013043.19294-1-wqu@suse.com \
    --to=wqu@suse.com \
    --cc=dsterba@suse.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).