From: charlesfdotz@tutanota.com
To: Dm Devel <dm-devel@lists.linux.dev>
Subject: Feature Request: Device Manager Fake Trim / Zero Trim
Date: Mon, 9 Oct 2023 02:56:42 +0200 (CEST) [thread overview]
Message-ID: <NgGvkdW--3-9@tutanota.com> (raw)
Hello,
I would like to request a new device manager layer be added that accepts trim requests for sectors and instead writes zeros to those sectors.
This would be useful to deal with SMR (shingled magnetic recording) drives that do not support trim. Currently after an SMR drive has had enough data written to it the performance drops dramatically because the disk must shuffle around data as if it were full and without trim support there is no way to inform the disk which sectors are no longer used. Currently there's no way to "fix" or reset this without doing an ATA secure erase despite many of these disk being sold without informing customers that they were SMR drives (western digital was sued for selling SMR drives as NAS drives).
However it seems that some of these drives are smart enough to mark sectors as unused if a sector is filled with zeros (https://old.reddit.com/r/DataHoarder/comments/g7lqaz/). So I think a device mapper that could emulate trim on these devices by simply accepting trim requests then filling those sectors with zeros. It would make a whole class of hard drives significantly more usable.
Sincerely,
Chuck
P.S. I was directed here after mailing the cryptsetup mailing list so I hope this is the right place to ask about this. Thank you.
next reply other threads:[~2023-10-09 0:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 0:56 charlesfdotz [this message]
2023-10-09 6:15 ` Feature Request: Device Manager Fake Trim / Zero Trim Hannes Reinecke
2023-10-09 9:42 ` Mikulas Patocka
2023-10-09 16:25 ` charlesfdotz
2023-10-10 6:53 ` Damien Le Moal
2023-10-10 6:48 ` Damien Le Moal
2023-10-10 7:15 ` Hannes Reinecke
2023-10-10 7:46 ` Damien Le Moal
2023-10-10 14:31 ` charlesfdotz
2023-10-11 0:33 ` Damien Le Moal
2023-10-11 19:07 ` charlesfdotz
2023-10-12 4:22 ` Christoph Hellwig
2023-10-12 6:33 ` Hannes Reinecke
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=NgGvkdW--3-9@tutanota.com \
--to=charlesfdotz@tutanota.com \
--cc=dm-devel@lists.linux.dev \
/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.