Activity log for bug #1336541

Date Who What changed Old value New value Message
2014-07-01 20:54:45 Néher Márton bug added bug
2014-07-01 21:07:31 Néher Márton description Hi, As USB attached SSDs are becoming quite big and affordable, along comes the idea of installing systems on these. But with current USB drivers, some functionality seems to be missing from USB subsystem. The system does not recognize it is an SSD, but it is corrected manually: # cat /etc/udev/rules.d/10-forcessd.rules SUBSYSTEM=="block", ATTRS{vendor}=="SanDisk", ATTRS{model}=="Extreme", KERNEL=="sd?", ATTR{queue/rotational}="0" # cat /sys/block/sdb/queue/rotational 0 Checked hdparm, it is saying I have TRIM on the device: root@dome-stick:~# hdparm -I /dev/sdb /dev/sdb: ATA device, with non-removable media Model Number: SanDisk pSSD (...) Commands/features: Enabled Supported: (...) * Data Set Management TRIM supported (limit 8 blocks) * Deterministic read ZEROs after TRIM (...) Here is appropriate dmesg: [ 3.815604] usb 2-8: Manufacturer: SunplusIT INC. [ 4.122002] usb 3-3: new SuperSpeed USB device number 2 using xhci_hcd [ 4.138402] usb 3-3: New USB device found, idVendor=0781, idProduct=5580 [ 4.138404] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4.138405] usb 3-3: Product: Extreme [ 4.138406] usb 3-3: Manufacturer: SanDisk [ 4.138407] usb 3-3: SerialNumber: AA011109131654094942 [ 4.141393] usb-storage 3-3:1.0: USB Mass Storage device detected [ 4.141431] scsi0 : usb-storage 3-3:1.0 [ 4.141703] usbcore: registered new interface driver usb-storage And: [ 5.331311] sd 0:0:0:0: [sdb] 122544516 512-byte logical blocks: (62.7 GB/58.4 GiB) [ 5.331608] sd 0:0:0:0: [sdb] Write Protect is off [ 5.331611] sd 0:0:0:0: [sdb] Mode Sense: 33 00 00 08 [ 5.331855] sd 0:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 5.339849] sdb: sdb1 sdb2 sdb3 < sdb5 > [ 5.340783] sd 0:0:0:0: [sdb] Attached SCSI disk From here I'll be using /boot formatted to ext4 to eliminate luks,lvm and btrfs from the equasion: # mount |grep sdb2 /dev/sdb2 on /boot type ext4 (rw,noexec,discard) # fstrim -v /boot/ fstrim: /boot/: FITRIM ioctl failed: Operation not supported # strace fstrim -v /boot/ (...) open("/boot/", O_RDONLY) = 3 ioctl(3, FITRIM, 0x7fffdded85c0) = -1 EOPNOTSUPP (Operation not supported) (...) During debugging, I've tried compiling a kernel with UAS module to check, it booted, worked fine, but it seems it wasn't used at all. Any ideas why TRIM is not working on USB? Any timeframes for possible fix? Any workarounds maybe? Hi, As USB attached SSDs are becoming quite big and affordable, along comes the idea of installing systems on these. But with current USB drivers, some functionality seems to be missing from USB subsystem. The system does not recognize it is an SSD, but it is corrected manually: # cat /etc/udev/rules.d/10-forcessd.rules SUBSYSTEM=="block", ATTRS{vendor}=="SanDisk", ATTRS{model}=="Extreme", KERNEL=="sd?", ATTR{queue/rotational}="0" # cat /sys/block/sdb/queue/rotational 0 Checked hdparm, it is saying I have TRIM on the device: # hdparm -I /dev/sdb /dev/sdb: ATA device, with non-removable media  Model Number: SanDisk pSSD (...) Commands/features:  Enabled Supported: (...)     * Data Set Management TRIM supported (limit 8 blocks)     * Deterministic read ZEROs after TRIM (...) Here is appropriate dmesg: [ 3.815604] usb 2-8: Manufacturer: SunplusIT INC. [ 4.122002] usb 3-3: new SuperSpeed USB device number 2 using xhci_hcd [ 4.138402] usb 3-3: New USB device found, idVendor=0781, idProduct=5580 [ 4.138404] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4.138405] usb 3-3: Product: Extreme [ 4.138406] usb 3-3: Manufacturer: SanDisk [ 4.138407] usb 3-3: SerialNumber: AA011109131654094942 [ 4.141393] usb-storage 3-3:1.0: USB Mass Storage device detected [ 4.141431] scsi0 : usb-storage 3-3:1.0 [ 4.141703] usbcore: registered new interface driver usb-storage And: [ 5.331311] sd 0:0:0:0: [sdb] 122544516 512-byte logical blocks: (62.7 GB/58.4 GiB) [ 5.331608] sd 0:0:0:0: [sdb] Write Protect is off [ 5.331611] sd 0:0:0:0: [sdb] Mode Sense: 33 00 00 08 [ 5.331855] sd 0:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 5.339849] sdb: sdb1 sdb2 sdb3 < sdb5 > [ 5.340783] sd 0:0:0:0: [sdb] Attached SCSI disk From here I'll be using /boot formatted to ext4 to eliminate luks,lvm and btrfs from the equasion: # mount |grep sdb2 /dev/sdb2 on /boot type ext4 (rw,noexec,discard) # fstrim -v /boot/ fstrim: /boot/: FITRIM ioctl failed: Operation not supported # strace fstrim -v /boot/ (...) open("/boot/", O_RDONLY) = 3 ioctl(3, FITRIM, 0x7fffdded85c0) = -1 EOPNOTSUPP (Operation not supported) (...) During debugging, I've tried compiling a kernel with UAS module to check, it booted, system was g changed with the trim - as it wouldn't been used at all. Any ideas why TRIM is not working on USB? Any timeframes for possible fix? Any workarounds maybe?
2014-07-02 00:22:02 Ubuntu Foundations Team Bug Bot tags fitrim fstrim trim uas usb bot-comment fitrim fstrim trim uas usb
2014-07-02 15:05:50 Brian Murray affects ubuntu udev (Ubuntu)
2014-08-05 10:45:25 Martin Pitt affects udev (Ubuntu) linux (Ubuntu)
2014-08-05 11:00:30 Brad Figg linux (Ubuntu): status New Incomplete
2014-08-07 03:39:32 Néher Márton tags bot-comment fitrim fstrim trim uas usb apport-collected bot-comment fitrim fstrim trim trusty uas usb
2014-08-07 03:39:33 Néher Márton description Hi, As USB attached SSDs are becoming quite big and affordable, along comes the idea of installing systems on these. But with current USB drivers, some functionality seems to be missing from USB subsystem. The system does not recognize it is an SSD, but it is corrected manually: # cat /etc/udev/rules.d/10-forcessd.rules SUBSYSTEM=="block", ATTRS{vendor}=="SanDisk", ATTRS{model}=="Extreme", KERNEL=="sd?", ATTR{queue/rotational}="0" # cat /sys/block/sdb/queue/rotational 0 Checked hdparm, it is saying I have TRIM on the device: # hdparm -I /dev/sdb /dev/sdb: ATA device, with non-removable media  Model Number: SanDisk pSSD (...) Commands/features:  Enabled Supported: (...)     * Data Set Management TRIM supported (limit 8 blocks)     * Deterministic read ZEROs after TRIM (...) Here is appropriate dmesg: [ 3.815604] usb 2-8: Manufacturer: SunplusIT INC. [ 4.122002] usb 3-3: new SuperSpeed USB device number 2 using xhci_hcd [ 4.138402] usb 3-3: New USB device found, idVendor=0781, idProduct=5580 [ 4.138404] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4.138405] usb 3-3: Product: Extreme [ 4.138406] usb 3-3: Manufacturer: SanDisk [ 4.138407] usb 3-3: SerialNumber: AA011109131654094942 [ 4.141393] usb-storage 3-3:1.0: USB Mass Storage device detected [ 4.141431] scsi0 : usb-storage 3-3:1.0 [ 4.141703] usbcore: registered new interface driver usb-storage And: [ 5.331311] sd 0:0:0:0: [sdb] 122544516 512-byte logical blocks: (62.7 GB/58.4 GiB) [ 5.331608] sd 0:0:0:0: [sdb] Write Protect is off [ 5.331611] sd 0:0:0:0: [sdb] Mode Sense: 33 00 00 08 [ 5.331855] sd 0:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 5.339849] sdb: sdb1 sdb2 sdb3 < sdb5 > [ 5.340783] sd 0:0:0:0: [sdb] Attached SCSI disk From here I'll be using /boot formatted to ext4 to eliminate luks,lvm and btrfs from the equasion: # mount |grep sdb2 /dev/sdb2 on /boot type ext4 (rw,noexec,discard) # fstrim -v /boot/ fstrim: /boot/: FITRIM ioctl failed: Operation not supported # strace fstrim -v /boot/ (...) open("/boot/", O_RDONLY) = 3 ioctl(3, FITRIM, 0x7fffdded85c0) = -1 EOPNOTSUPP (Operation not supported) (...) During debugging, I've tried compiling a kernel with UAS module to check, it booted, system was g changed with the trim - as it wouldn't been used at all. Any ideas why TRIM is not working on USB? Any timeframes for possible fix? Any workarounds maybe? Hi, As USB attached SSDs are becoming quite big and affordable, along comes the idea of installing systems on these. But with current USB drivers, some functionality seems to be missing from USB subsystem. The system does not recognize it is an SSD, but it is corrected manually: # cat /etc/udev/rules.d/10-forcessd.rules SUBSYSTEM=="block", ATTRS{vendor}=="SanDisk", ATTRS{model}=="Extreme", KERNEL=="sd?", ATTR{queue/rotational}="0" # cat /sys/block/sdb/queue/rotational 0 Checked hdparm, it is saying I have TRIM on the device: # hdparm -I /dev/sdb /dev/sdb: ATA device, with non-removable media  Model Number: SanDisk pSSD (...) Commands/features:  Enabled Supported: (...)     * Data Set Management TRIM supported (limit 8 blocks)     * Deterministic read ZEROs after TRIM (...) Here is appropriate dmesg: [ 3.815604] usb 2-8: Manufacturer: SunplusIT INC. [ 4.122002] usb 3-3: new SuperSpeed USB device number 2 using xhci_hcd [ 4.138402] usb 3-3: New USB device found, idVendor=0781, idProduct=5580 [ 4.138404] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4.138405] usb 3-3: Product: Extreme [ 4.138406] usb 3-3: Manufacturer: SanDisk [ 4.138407] usb 3-3: SerialNumber: AA011109131654094942 [ 4.141393] usb-storage 3-3:1.0: USB Mass Storage device detected [ 4.141431] scsi0 : usb-storage 3-3:1.0 [ 4.141703] usbcore: registered new interface driver usb-storage And: [ 5.331311] sd 0:0:0:0: [sdb] 122544516 512-byte logical blocks: (62.7 GB/58.4 GiB) [ 5.331608] sd 0:0:0:0: [sdb] Write Protect is off [ 5.331611] sd 0:0:0:0: [sdb] Mode Sense: 33 00 00 08 [ 5.331855] sd 0:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 5.339849] sdb: sdb1 sdb2 sdb3 < sdb5 > [ 5.340783] sd 0:0:0:0: [sdb] Attached SCSI disk From here I'll be using /boot formatted to ext4 to eliminate luks,lvm and btrfs from the equasion: # mount |grep sdb2 /dev/sdb2 on /boot type ext4 (rw,noexec,discard) # fstrim -v /boot/ fstrim: /boot/: FITRIM ioctl failed: Operation not supported # strace fstrim -v /boot/ (...) open("/boot/", O_RDONLY) = 3 ioctl(3, FITRIM, 0x7fffdded85c0) = -1 EOPNOTSUPP (Operation not supported) (...) During debugging, I've tried compiling a kernel with UAS module to check, it booted, system was g changed with the trim - as it wouldn't been used at all. Any ideas why TRIM is not working on USB? Any timeframes for possible fix? Any workarounds maybe? --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: dome 2460 F.... pulseaudio /dev/snd/pcmC1D0p: dome 2460 F...m pulseaudio /dev/snd/controlC0: dome 2460 F.... pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=bafebd1d-6988-438f-afd4-b41bb8608616 InstallationDate: Installed on 2014-06-12 (56 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 20AR001AUK Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/system-root ro rootflags=subvol=@ cryptopts=target=crypter,source=/dev/disk/by-uuid/dc149cdf-62f9-4e29-a048-dd0403f51d56,lvm=system,discard quiet splash crashkernel=384M-:128M vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/28/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET75WW (2.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AR001AUK dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET75WW(2.25):bd03/28/2014:svnLENOVO:pn20AR001AUK:pvrThinkPadT440s:rvnLENOVO:rn20AR001AUK:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AR001AUK dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO
2014-08-07 03:39:34 Néher Márton attachment added AlsaInfo.txt https://bugs.launchpad.net/bugs/1336541/+attachment/4171614/+files/AlsaInfo.txt
2014-08-07 03:39:36 Néher Márton attachment added BootDmesg.txt https://bugs.launchpad.net/bugs/1336541/+attachment/4171615/+files/BootDmesg.txt
2014-08-07 03:39:38 Néher Márton attachment added CRDA.txt https://bugs.launchpad.net/bugs/1336541/+attachment/4171616/+files/CRDA.txt
2014-08-07 03:39:39 Néher Márton attachment added CurrentDmesg.txt https://bugs.launchpad.net/bugs/1336541/+attachment/4171617/+files/CurrentDmesg.txt
2014-08-07 03:39:41 Néher Márton attachment added IwConfig.txt https://bugs.launchpad.net/bugs/1336541/+attachment/4171618/+files/IwConfig.txt
2014-08-07 03:39:43 Néher Márton attachment added Lspci.txt https://bugs.launchpad.net/bugs/1336541/+attachment/4171619/+files/Lspci.txt
2014-08-07 03:39:44 Néher Márton attachment added Lsusb.txt https://bugs.launchpad.net/bugs/1336541/+attachment/4171620/+files/Lsusb.txt
2014-08-07 03:39:45 Néher Márton attachment added ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1336541/+attachment/4171621/+files/ProcCpuinfo.txt
2014-08-07 03:39:48 Néher Márton attachment added ProcInterrupts.txt https://bugs.launchpad.net/bugs/1336541/+attachment/4171622/+files/ProcInterrupts.txt
2014-08-07 03:39:49 Néher Márton attachment added ProcModules.txt https://bugs.launchpad.net/bugs/1336541/+attachment/4171623/+files/ProcModules.txt
2014-08-07 03:39:51 Néher Márton attachment added RfKill.txt https://bugs.launchpad.net/bugs/1336541/+attachment/4171624/+files/RfKill.txt
2014-08-07 03:39:53 Néher Márton attachment added UdevDb.txt https://bugs.launchpad.net/bugs/1336541/+attachment/4171625/+files/UdevDb.txt
2014-08-07 03:39:56 Néher Márton attachment added UdevLog.txt https://bugs.launchpad.net/bugs/1336541/+attachment/4171626/+files/UdevLog.txt
2014-08-07 03:39:59 Néher Márton attachment added WifiSyslog.txt https://bugs.launchpad.net/bugs/1336541/+attachment/4171627/+files/WifiSyslog.txt
2014-08-07 03:41:00 Néher Márton linux (Ubuntu): status Incomplete Confirmed
2014-08-07 19:46:25 Joseph Salisbury linux (Ubuntu): importance Undecided Medium
2014-08-07 19:46:43 Joseph Salisbury linux (Ubuntu): status Confirmed Incomplete
2014-08-08 03:44:34 Néher Márton tags apport-collected bot-comment fitrim fstrim trim trusty uas usb apport-collected bot-comment fitrim fstrim kernel-bug-exists-upstream trim trusty uas usb
2014-08-08 03:44:42 Néher Márton linux (Ubuntu): status Incomplete Confirmed
2016-04-13 09:22:49 Darren Newman bug added subscriber Darren Newman
2016-10-23 19:09:46 Tehnick bug added subscriber Tehnick
2016-10-30 23:03:29 Elias Abacioglu bug added subscriber Elias Abacioglu
2016-10-30 23:05:29 Elias Abacioglu bug watch added http://bugzilla.kernel.org/show_bug.cgi?id=83181
2016-12-31 13:39:28 NuageBleu@gmail.com bug added subscriber NuageBleu@gmail.com
2017-01-10 13:36:38 Pham Hong Nhat bug added subscriber Pham Hong Nhat
2017-01-10 13:43:35 Pham Hong Nhat affects linux (Ubuntu) linux-signed-lts-xenial (Ubuntu)
2017-01-10 19:25:51 Joseph Gan bug added subscriber Joseph Gan
2017-01-10 19:26:54 Joseph Gan affects linux-signed-lts-xenial (Ubuntu) linux-lts-xenial (Ubuntu)
2017-02-06 14:30:05 Daniel Llewellyn bug task added linux
2017-02-06 14:32:38 Daniel Llewellyn tags apport-collected bot-comment fitrim fstrim kernel-bug-exists-upstream trim trusty uas usb apport-collected bot-comment fitrim fstrim kernel-bug-exists-upstream trim trusty uas usb xenial yakkety
2018-08-19 09:35:34 Bug Watch Updater linux: status Unknown Confirmed
2018-08-19 09:35:34 Bug Watch Updater linux: importance Unknown Medium