From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
zlang@redhat.com, fstests@vger.kernel.org, guan@eryu.me,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/1] xfs: test scaling of the mkfs concurrency options
Date: Wed, 19 Jun 2024 21:24:07 -0700 [thread overview]
Message-ID: <ZnOu537W5S9Ic6dK@infradead.org> (raw)
In-Reply-To: <20240619162808.GL103034@frogsfrogsfrogs>
On Wed, Jun 19, 2024 at 09:28:08AM -0700, Darrick J. Wong wrote:
> Weird failure case? If we don't have an output file to link, fstests
> spits out:
>
> 1842.lba268433408: could not setup output file
Not pretty, but not as weird as I expected it from a quick glance.
next prev parent reply other threads:[~2024-06-20 4:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 0:46 [PATCHSET 1/6] xfsprogs: scale shards on ssds Darrick J. Wong
2024-06-18 0:46 ` [PATCH 1/1] xfs: test scaling of the mkfs concurrency options Darrick J. Wong
2024-06-19 6:24 ` Christoph Hellwig
2024-06-19 16:28 ` Darrick J. Wong
2024-06-20 4:24 ` Christoph Hellwig [this message]
2024-06-19 16:29 ` [PATCH v1.1 " Darrick J. Wong
2024-06-20 4:24 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2024-06-20 20:52 [PATCHSET 1/6] xfsprogs: scale shards on ssds Darrick J. Wong
2024-06-20 20:54 ` [PATCH 1/1] xfs: test scaling of the mkfs concurrency options Darrick J. Wong
2024-06-03 20:12 [PATCHSET 3/3] xfsprogs: scale shards on ssds Darrick J. Wong
2024-06-03 20:13 ` [PATCH 1/1] xfs: test scaling of the mkfs concurrency options Darrick J. Wong
2023-12-31 19:57 [PATCHSET 2/8] xfsprogs: scale shards on ssds Darrick J. Wong
2023-12-27 13:43 ` [PATCH 1/1] xfs: test scaling of the mkfs concurrency options 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=ZnOu537W5S9Ic6dK@infradead.org \
--to=hch@infradead.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=linux-xfs@vger.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