From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: zlang@redhat.com, fstests@vger.kernel.org,
linux-xfs@vger.kernel.org, guan@eryu.me
Subject: Re: [PATCH 3/4] generic/{166,167,333,334,671}: actually fill the filesystem with snapshots
Date: Wed, 27 Mar 2024 09:59:13 -0700 [thread overview]
Message-ID: <ZgRQYV_uc94IImTk@infradead.org> (raw)
In-Reply-To: <171150741593.3286541.18115194618541313905.stgit@frogsfrogsfrogs>
On Tue, Mar 26, 2024 at 07:43:35PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> XFS has this behavior in its reflink implementation where it returns
> ENOSPC if one of the AGs that would be involved in the sharing operation
> becomes more than 90% full. As Kent Overstreet points out, that means
> the snapshot creator shuts down when the filesystem is only about a
> third full. We could exercise the system harder by not *forcing*
> reflink, which will actually fill the filesystem full.
All these tests are supposed to test the reflink code, how does
using cp --reflink=auto make sense for that?
next prev parent reply other threads:[~2024-03-27 16:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 2:43 [PATCHSET] fstests: random fixes for v2024.02.09 Darrick J. Wong
2024-03-27 2:43 ` [PATCH 1/4] xfs/270: fix rocompat regex Darrick J. Wong
2024-03-27 2:48 ` [PATCH v1.1 " Darrick J. Wong
2024-03-27 11:32 ` Christoph Hellwig
2024-03-27 2:43 ` [PATCH 2/4] xfs/176: fix stupid failure Darrick J. Wong
2024-03-27 11:32 ` Christoph Hellwig
2024-03-27 2:43 ` [PATCH 3/4] generic/{166,167,333,334,671}: actually fill the filesystem with snapshots Darrick J. Wong
2024-03-27 16:59 ` Christoph Hellwig [this message]
2024-03-29 23:07 ` Darrick J. Wong
2024-03-30 5:39 ` Christoph Hellwig
2024-03-30 7:14 ` Zorro Lang
2024-03-27 2:43 ` [PATCH 4/4] generic: test MADV_POPULATE_READ with IO errors Darrick J. Wong
2024-03-30 7:12 ` Zorro Lang
2024-03-30 15:31 ` 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=ZgRQYV_uc94IImTk@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 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.