From: "Darrick J. Wong" <djwong@kernel.org>
To: David Timber <dxdt@dev.snart.me>
Cc: Zorro Lang <zlang@kernel.org>, Christoph Hellwig <hch@lst.de>,
fstests@vger.kernel.org
Subject: Re: [PATCH 2/2] generic/740: add --force option to mkfs.ntfs
Date: Thu, 25 Jun 2026 11:45:44 -0700 [thread overview]
Message-ID: <20260625184544.GR6070@frogsfrogsfrogs> (raw)
In-Reply-To: <20260618192236.654082-2-dxdt@dev.snart.me>
On Fri, Jun 19, 2026 at 04:22:36AM +0900, David Timber wrote:
> mkntfs refuses to format the target if it's backed by a "real" device
> but not a partition to maintain compatibility with Windows. When
> formatting the scratch device in NTFS for testing, this behaviour has
> to be overridden so that any type of blockdev can be used as a scratch
> device.
>
> Signed-off-by: David Timber <dxdt@dev.snart.me>
> ---
> tests/generic/740 | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/tests/generic/740 b/tests/generic/740
> index 4f8bf099..718d983d 100755
> --- a/tests/generic/740
> +++ b/tests/generic/740
> @@ -72,8 +72,10 @@ do
> postargs=2000
> ;;
> ntfs)
> - # "quick" format that doesn't zero the entire device
> - postargs="--quick"
> + # "quick" format that doesn't zero the entire device. Use -F so
"Use --force..." ?
--D
> + # that NTFS-3G mkfs formats the volume even if the scratch
> + # blockdev is not a partition.
> + postargs="--quick --force"
> ;;
> reiser4)
> preop="echo y |"
> --
> 2.54.0
>
>
next prev parent reply other threads:[~2026-06-25 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 19:22 [PATCH 1/2] generic/740: set env for mkfs.exfat David Timber
2026-06-18 19:22 ` [PATCH 2/2] generic/740: add --force option to mkfs.ntfs David Timber
2026-06-19 4:53 ` Christoph Hellwig
2026-06-25 18:45 ` Darrick J. Wong [this message]
2026-06-19 4:53 ` [PATCH 1/2] generic/740: set env for mkfs.exfat Christoph Hellwig
2026-06-25 18:45 ` Darrick J. Wong
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=20260625184544.GR6070@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=dxdt@dev.snart.me \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=zlang@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.