All of lore.kernel.org
 help / color / mirror / Atom feed
From: Melvin Vermeeren <vermeeren@vermwa.re>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@redhat.com, Milan Broz <mbroz@redhat.com>
Subject: Re: [dm-devel] Integrity discard/trim extremely slow on NVMe SSD storage (~10GiB/minute)
Date: Wed, 12 May 2021 21:26:20 +0200	[thread overview]
Message-ID: <3832189.ZKCCLTqfco@verm-r4e> (raw)
In-Reply-To: <4782666.JkfDSx4nLX@verm-r4e>


[-- Attachment #1.1: Type: text/plain, Size: 1184 bytes --]

Hi again,

On Friday, 30 April 2021 21:26:23 CEST Melvin Vermeeren wrote:
> (As mentioned in other mail I
> contacted Seagate about this, it should be fixed in drive firmware.)

After some back and forth with testing and diagnostics Seagate has provided 
updated firmware version STNSC016, drives originally had version STNSC014. 
Updating this firmware with nvme-cli utilities has resolved the issue.

For validation, I allocated 500GiB space for testing in the full stack:
FireCuda 520 -> dm-integrity -> mdadm raid1 -> luks cryptsetup -> lvm -> lv

Then I discard the LV. Disk util % of both drives moves to 100% while 
discarding, as checked with dstat. It took 20.920s real seconds to discard 
500GiB on a live system.

With old firmware, rate with this workload was approx 10GiB per 70 seconds or 
so. This means the new firmware is approx (500/10) * (70/20.92) = 167.3 times 
faster in this workload with a rate of approx 1434GiB per minute.

Perhaps there are still optimisations possible for dm-integrity, but in this 
case it really was a device issue as you suspected. Thanks again for all the 
help and work on dm-integrity!

Cheers,

-- 
Melvin Vermeeren
Systems engineer

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 97 bytes --]

--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel

  reply	other threads:[~2021-05-17  7:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 18:29 [dm-devel] Integrity discard/trim extremely slow on NVMe SSD storage (~10GiB/minute) Melvin Vermeeren
2021-04-26 15:33 ` Mikulas Patocka
2021-04-26 16:02   ` Mikulas Patocka
2021-04-30 19:26     ` Melvin Vermeeren
2021-05-12 19:26       ` Melvin Vermeeren [this message]
2021-04-30 19:23   ` Melvin Vermeeren

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=3832189.ZKCCLTqfco@verm-r4e \
    --to=vermeeren@vermwa.re \
    --cc=dm-devel@redhat.com \
    --cc=mbroz@redhat.com \
    --cc=mpatocka@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.