From: Christoph Hellwig <hch@lst.de>
To: Zorro Lang <zlang@redhat.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Christoph Hellwig <hch@lst.de>,
Dave Chinner <dchinner@redhat.com>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] xfs: new EOF fragmentation tests
Date: Tue, 15 Oct 2024 05:39:23 +0200 [thread overview]
Message-ID: <20241015033923.GA15971@lst.de> (raw)
In-Reply-To: <20241014174650.wms62e3ogzilcnn5@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On Tue, Oct 15, 2024 at 01:46:50AM +0800, Zorro Lang wrote:
> >From the output we can see the sector size is 4096.
> The mount option is "-o dax=always/inode/never", no more, without external
> log device, no rtdev.
Hmm. Given how unreliable these tests are maybe we should just drop
them given that they are trying to verify optimal expected behavior and
not just correctness. Maybe Dave who originally wrote them can chime
in.
next prev parent reply other threads:[~2024-10-15 3:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 8:45 xfs post-EOF block freeing fixes v2 Christoph Hellwig
2024-09-24 8:45 ` [PATCH] xfs: new EOF fragmentation tests Christoph Hellwig
2024-09-24 15:03 ` Darrick J. Wong
2024-09-25 11:15 ` Zorro Lang
2024-09-26 12:31 ` Zorro Lang
2024-10-01 14:59 ` Darrick J. Wong
2024-10-02 13:38 ` Zorro Lang
2024-10-02 14:35 ` Brian Foster
2024-10-02 14:57 ` Darrick J. Wong
2024-10-02 15:56 ` Brian Foster
2024-10-02 20:04 ` Darrick J. Wong
2024-10-13 17:49 ` Zorro Lang
2024-10-14 6:07 ` Christoph Hellwig
2024-10-14 14:14 ` Zorro Lang
2024-10-14 15:24 ` Darrick J. Wong
2024-10-14 17:46 ` Zorro Lang
2024-10-15 3:39 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-23 5:38 xfs post-EOF block freeing fixes Christoph Hellwig
2024-06-23 5:38 ` [PATCH] xfs: new EOF fragmentation tests Christoph Hellwig
2024-06-23 13:03 ` Zorro Lang
2024-06-24 8:49 ` Christoph Hellwig
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=20241015033923.GA15971@lst.de \
--to=hch@lst.de \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).