From: Matthew Eaton <m.eaton82@gmail.com>
To: fio@vger.kernel.org
Subject: trim entries leaked?
Date: Fri, 6 Oct 2023 12:52:47 -0700 [thread overview]
Message-ID: <CAF+0mvm8bw-wvnSv8SUm=6f+T+zSMd-uXm2weefGyONqL+qq=g@mail.gmail.com> (raw)
Hi fio group,
I'm trying to get a workload doing concurrent writes, verifies, and/or
trims. I've narrowed down my job file to this:
[verify]
ioengine=psync
direct=1
size=5g
bs=4k
rw=randwrite
numjobs=1
iodepth=1
verify=crc32c
verify_backlog=1
trim_percentage=50
trim_backlog=1
filename=/dev/nvme0n1
With this job writes are read/verified but there are no trims. If I
set backlogs to 0 I get this message before the verification phase:
fio: 654981 trim entries leaked?
I'm using the latest fio as of today, fio-3.35-134-g6f9c.
next reply other threads:[~2023-10-06 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 19:52 Matthew Eaton [this message]
2023-10-06 20:18 ` trim entries leaked? Wolford, Jeff (CBG Servers and Options Engineering)
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='CAF+0mvm8bw-wvnSv8SUm=6f+T+zSMd-uXm2weefGyONqL+qq=g@mail.gmail.com' \
--to=m.eaton82@gmail.com \
--cc=fio@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 read-only IMAP folder(s) and NNTP newsgroup(s).