public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Konst Mayer <cdlscpmv@gmail.com>
To: linux-xfs@vger.kernel.org
Subject: TRIM does not propagate real-time sections
Date: Thu, 20 Jun 2024 22:52:52 +0700	[thread overview]
Message-ID: <2W73T39BGMHNW.28KW9QVYJD5M1@gmail.com> (raw)
In-Reply-To: <2UXR5417C74F3.27N1XQP68WXAD@gmail.com>

We are using Linux 5.15, by the way.

Konst Mayer <cdlscpmv@gmail.com> wrote:
> Hello,
> 
> In our setup, we created a dedicated real-time section on top of RAID0
> (backed by multiple SSDs). The rest of the filesystem resides on another
> device.
> 
> When we ran the "fstrim" command on the mountpoint (mounted with -o
> rtdev=/dev/md/raid), the discard does not propogate to the real-time
> partition, and only the partition with metadata gets trimmed.
> 
> Is there a solution to this?
> 
> Best regards,
> Konst

  reply	other threads:[~2024-06-20 15:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 15:49 Konst Mayer
2024-06-20 15:52 ` Konst Mayer [this message]
2024-06-20 19:58   ` TRIM does not propagate real-time sections 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=2W73T39BGMHNW.28KW9QVYJD5M1@gmail.com \
    --to=cdlscpmv@gmail.com \
    --cc=linux-xfs@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