Bug 1287133 - Abysmal SSD performance on SSD and all 4.2 kernels
Summary: Abysmal SSD performance on SSD and all 4.2 kernels
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 22
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-01 15:03 UTC by Frank Sweetser
Modified: 2016-07-19 19:59 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 19:59:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Frank Sweetser 2015-12-01 15:03:18 UTC
Description of problem:

I'm running a Dell Optiplex 9010, with dual Samsung 840 Pro SSDs in software RAID 1.  When I first boot up, everything is running as normal.  However, within 15 to 20 minutes, all read and write performance to my drives drops to barely functioning levels.  My IO monitors (I have kgrellm running) initially show throughput typically maxing out around 280MB/s, but they eventually drop to no more than 5MB/s.

I haven't been able to wait long enough for a bonnie++ run to complete and get hard data.

Version-Release number of selected component (if applicable):

Extreme slowdown is reliably observed on my system in all 4.2 kernels.

How reproducible:

100%.

Steps to Reproduce:

Just boot a 4.2 kernel, and wait.

I'll be more than happy to try any troubleshooting steps that might either fix a problem with my setup, or shed more light on what the underlying cause might be.

thanks!

Comment 1 Fedora End Of Life 2016-07-19 19:59:43 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.