CFQ is default scheduler (incorrect udev rule)

Bug #1736825 reported by Andrei Demin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I've found out that all my drives uses CFQ scheduler by default, since that udev rule (60-ssd-scheduler.rules) that says use CFQ for rotating disk is useless. I belive that Ubuntu uses Deadline scheduler by default, but for somewhat reason it's not that on my system.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: udev 229-4ubuntu21
ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
CurrentDesktop: KDE
CustomUdevRuleFiles: 60-vboxdrv.rules 60-ssd-scheduler.rules
Date: Thu Dec 7 03:11:16 2017
InstallationDate: Installed on 2014-11-26 (1106 days ago)
InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic root=UUID=33a02342-70da-4f8d-9868-2f8e7330ec90 ro
SourcePackage: systemd
UpgradeStatus: Upgraded to xenial on 2016-07-28 (496 days ago)
dmi.bios.date: 09/12/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3901
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H67-M
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3901:bd09/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Andrei Demin (andrei-demin1996) wrote :
description: updated
Revision history for this message
Dan Streetman (ddstreet) wrote :

please reopen if this is still an issue

Changed in systemd (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.