Bug 2145213
| Summary: | [virtio-win] Windows 10 "Optimize drive"/Trim/Discard causes all data to be rewritten [rhel-9.1.0.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | RHEL Program Management Team <pgm-rhel-tools> |
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> |
| virtio-win sub component: | virtio-win-prewhql | QA Contact: | Peixiu Hou <phou> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | medium | CC: | ailan, coli, fdeutsch, gveitmic, jinzhao, juzhang, mdean, menli, qizhu, vrozenfe, ymankad |
| Version: | 9.0 | Keywords: | Triaged, ZStream |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Windows | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: |
both virtio storage drivers - viostor and vioscsi can show very slow defragmintation performance on trim (unmap) enabled volumes. This can happen because the default slab (cluster) size reported by QEMU is 4K, while Windows volume defragmentation can be significantly improved if the slab size is 8MB or bigger (Windows Hyper-V uses 32MB slab size). The slab size can be adsjusted by "discard_granularity" QEMU parameter.
|
Story Points: | --- |
| Clone Of: | 2020998 | Environment: | |
| Last Closed: | 2023-01-23 15:20:17 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2020998 | ||
| Bug Blocks: | |||
|
Comment 1
menli@redhat.com
2022-11-24 06:21:59 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (virtio-win bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:0327 |