public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Fu <vincentfu@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Shivashekar Murali Shankar <ssdtshiva@gmail.com>,
	 "io-uring@vger.kernel.org" <io-uring@vger.kernel.org>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>,
	 Ankit Kumar <ankit.kumar@samsung.com>
Subject: Re: Fwd: fio: ruh info failed
Date: Fri, 26 Sep 2025 17:46:23 -0400	[thread overview]
Message-ID: <CAOp=CXk-nuKPqf9d94ikWJPC9OoTGPcfTtA_kDYNrjqAptvz0A@mail.gmail.com> (raw)
In-Reply-To: <1394af5d-ca1c-453f-8a66-f0f3a53702cf@kernel.dk>

On Fri, Sep 26, 2025 at 5:43 PM Jens Axboe <axboe@kernel.dk> wrote:
>
> On 9/26/25 1:30 PM, Shivashekar Murali Shankar wrote:
> > Hi,
> >
> > I am currently testing fio with io_uring on an FDP-capable drive, but
> > I see failures such as “fio: ruh info failed” when trying to run FDP
> > job files. This is run on an XFS file system on a mounted drive. Do we
> > have support for this?
> >
> > Below is my fio job file:
> >
> > [global]
> > ioengine=io_uring
> > direct=1
> > bs=4k
> > iodepth=32
> > rw=write
> > numjobs=1
> > group_reporting
> > fdp=1
> >
> > [largedata]
> > filename=/mnt/nvme/largedata
> > size=30G
> > fdp_pli=1
>

FDP support is currently only available for NVMe character devices.
See the example here:

https://github.com/axboe/fio/blob/master/examples/uring-cmd-fdp.fio

> It's generally a good idea to CC the folks that worked on this, and
> probably use the fio list rather than the io_uring list...
>
> Adding them.
>
> --
> Jens Axboe
>

  reply	other threads:[~2025-09-26 21:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAERsGfiZ9YVeXMGk=dL+orN3o2HXJ0Oy9EQhVwK43MMDUSA-WQ@mail.gmail.com>
     [not found] ` <CAERsGfgCA7iFwLQ2L+=QyEg0=KuwK4hq62QcYpnY5R4h9abZMg@mail.gmail.com>
2025-09-26 19:30   ` Fwd: fio: ruh info failed Shivashekar Murali Shankar
2025-09-26 21:42     ` Jens Axboe
2025-09-26 21:46       ` Vincent Fu [this message]
2025-09-27  1:50         ` Shivashekar Murali Shankar

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='CAOp=CXk-nuKPqf9d94ikWJPC9OoTGPcfTtA_kDYNrjqAptvz0A@mail.gmail.com' \
    --to=vincentfu@gmail.com \
    --cc=ankit.kumar@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=io-uring@vger.kernel.org \
    --cc=ssdtshiva@gmail.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