#15880 closed bug (fixed)
KDL nvme SSD
| Reported by: | kim1963 | Owned by: | waddlesplash |
|---|---|---|---|
| Priority: | normal | Milestone: | R1/beta2 |
| Component: | Drivers/Disk/NVMe | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Rev. 54016 or later Any write operation to disk.
Attachments (9)
Change History (19)
by , 5 years ago
| Attachment: | screenshot156.png added |
|---|
by , 5 years ago
| Attachment: | photo_2020-04-17_12-33-35.jpg added |
|---|
by , 5 years ago
| Attachment: | photo_2020-04-17_12-33-39.jpg added |
|---|
by , 5 years ago
| Attachment: | photo_2020-04-17_12-33-31.jpg added |
|---|
by , 5 years ago
| Attachment: | photo_2020-04-17_12-33-26.jpg added |
|---|
by , 5 years ago
| Attachment: | photo_2020-04-17_12-33-06.jpg added |
|---|
comment:1 by , 5 years ago
| Component: | - General → Drivers/Disk/NVMe |
|---|---|
| Owner: | changed from to |
comment:4 by , 5 years ago
No, that hrev fixes crashes and disk corruption on other systems. I need time to fix it properly.
comment:5 by , 5 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fixed in hrev54077. However, I added some more asserts in that commit to catch NVMe disk corruption which trigger very reliably; so I'd advise not using the driver at all till these are fixed (as using an older driver can easily corrupt your disk!)
comment:7 by , 5 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
comment:8 by , 5 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
As I said in my reply above:
I added some more asserts in that commit to catch NVMe disk corruption which trigger very reliably
The new KDL here is tracked along with #15123; this ticket is fixed.
comment:9 by , 5 years ago
device Mass storage controller (Non-Volatile memory controller, NVM Ex [1|8|2]
vendor 15b7: Sandisk Corp device 5002: WD Black 2018/PC SN720 NVMe SSD
comment:10 by , 5 years ago
| Milestone: | Unscheduled → R1/beta2 |
|---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
Seems it's a lock order problem I failed to notice because writes under BFS never get split.