Fedora

Optimal I/O size isn't calculated properly with uas module, and it may make data inconsistent on the disk and logical volume

Bug #1666109 reported by Yasuaki Taniguchi
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fedora
Confirmed
Undecided
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

1) Ubuntu release
  Ubuntu 16.04.2 LTS x86_64 desktop
2) package name
linux-generic-hwe-16.04 (4.8.0.36.8)

3) Expected behavior
When I attached more than 3 uas devices, all uas devices would be probed as SCSI disks.

4) What happened instead
The third device failed to be attached, and the first and second devices made strange behaviors.

5) Additional information
When I used linux-generic (4.4.0.62.65), it was good.
I found this bug on Fedora 25 at first, and I confirmed the same bug exists on Ubuntu 16.04 LTS.
  https://bugzilla.redhat.com/show_bug.cgi?id=1420935
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: gdm 886 F.... pulseaudio
                      yasuaki 1281 F.... pulseaudio
 /dev/snd/controlC0: gdm 886 F.... pulseaudio
                      yasuaki 1281 F.... pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-05-19 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IwConfig:
 enp0s25 no wireless extensions.

 lo no wireless extensions.
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=1a82c712-c415-4f32-b052-d7d987989726 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-20-generic N/A
 linux-backports-modules-4.15.0-20-generic N/A
 linux-firmware 1.173
RfKill:

Tags: bionic
Uname: Linux 4.15.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 01/18/2017
dmi.bios.vendor: Intel Corporation
dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
dmi.board.name: NUC5i7RYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H73774-101
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i7RYB:rvrH73774-101:cvn:ct3:cvr:

See original description
Revision history for this message
In , Yasuaki (yasuaki-redhat-bugs) wrote :
Download full text (22.7 KiB)

Description of problem:
I connect a second USB-UAS drive to the single USB interface card,
the second drive is failed to probe.
When I connect it to another USB interface card, it works fine.

Version-Release number of selected component (if applicable):
Fedora 25 x86_64, 4.9.7-201.fc25.x86_64
Dell XPS 8700,
SD-PEU3R-2EL2 x2 (Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02)),
RS-EC32-U31R x4 (USB 3.1 RAID1 external drives)

How reproducible:
Always

Steps to Reproduce:
1. Connect 2 USB-UAS drives on the same interface card.
2. Boot Fedora 25

Actual results:
Only 1 drive works.

Expected results:
Two drives work.

Additional info:
On Windows 10, it works fine.

========lspci ( dev 04:00.0 and 06:00.0) ==================================
[root@nas01 ~]# lspci
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d5)
00:1c.6 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #7 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation Z87 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
01:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01)
01:00.1 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
04:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02)
05:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
06:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02)
=====================...

Revision history for this message
In , Yasuaki (yasuaki-redhat-bugs) wrote :
Download full text (13.1 KiB)

I've changed title.
When I connected 3rd USB-UAS device, uas module fails to probe it.
And when I connected 2 drives on the same USB interface card, it was OK.

======== 1st drive (connect to C220 Chipset USB3.0 port================
[root@nas01 ~]# lsusb -t
/: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
/: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
    |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 4: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
        |__ Port 4: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 7: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
====================================================

======= 2nd drive (connect USB interface board)
[root@nas01 ~]# lsusb -t
/: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
/: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
    |__ Port 1: Dev 8, If 0, Class=Mass Storage, Driver=uas, 5000M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
    |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 4: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
        |__ Port 4: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 7: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
===========================

======== 3rd drive (connect the other USB interface board)
[root@nas01 ~]# lsusb -t
/: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
/: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
    |__ Port 1: Dev 8, If 0, Class=Mass Storage, Driver=uas, 5000M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
    |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, ...

Revision history for this message
In , Yasuaki (yasuaki-redhat-bugs) wrote :

It is not a Fedora specific bug.

Fedora 24 release (4.5.5-300.fc24.x86_64): Good
Fedora 24 updates (4.9.9-100.fc24.x86_64): Fail
Fedora 25 release (4.8.6-300.fc25.x86_64): Fail
Fedora 25 updates (4.9.9-200.fc25.x86_64): Fail

And on Ubuntu 16.04LTS
Ubuntu 16.04LTS ga (4.4.0) : Good
Ubuntu 16.04LTS HWE (4.8.0): Fail

So, it may be a regression between 4.5.5 and 4.8.x kernel on upstream.

Revision history for this message
In , Yasuaki (yasuaki-redhat-bugs) wrote :

I updated kernel to 4.9.13-200.fc25.x86_64, then more than three uas devices can
be attached. But because of the bug about uas and scsi like:
  https://<email address hidden>/msg60170.html ,
I can't use uas drives properly, furthermore, the USB buses is unstable,
such as keyboard and mouse hung up.

Revision history for this message
In , Justin (justin-redhat-bugs) wrote :

*********** MASS BUG UPDATE **************

We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Revision history for this message
In , Yasuaki (yasuaki-redhat-bugs) wrote :
Download full text (8.0 KiB)

I couldn't find 4.10.9-200.fc25 kernel on the update and dnf repository, but I found 4.10.8-200.fc25, so I test it on 4.10.8-200.fc25 kernel.

This bug is still alive.
(1) I *can* attach more than three uas devices, but
(2) I/O information, which I can get from /sys/block/sd*/queue, is strange,
(3) parted and LVM can't calculate optimal disk geometries.

======== 4 Disk attachment OK ==============================
[ 223.209197] usb 3-2.4: new SuperSpeed USB device number 3 using xhci_hcd
[ 223.221961] usb 3-2.4: New USB device found, idVendor=0584, idProduct=0276
[ 223.221963] usb 3-2.4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 223.221965] usb 3-2.4: Product: RS-EC32-U31R RAID1
[ 223.221967] usb 3-2.4: Manufacturer: RATOC Systems,Inc.
[ 223.221969] usb 3-2.4: SerialNumber: 32311643000A
[ 223.238444] usbcore: registered new interface driver usb-storage
[ 223.242354] scsi host4: uas
[ 223.242429] usbcore: registered new interface driver uas
[ 223.669308] scsi 4:0:0:0: Direct-Access HGST HDN 724040ALE640 MJAO PQ: 0 ANSI: 6
[ 223.683229] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 223.688262] sd 4:0:0:0: [sdc] 7813988353 512-byte logical blocks: (4.00 TB/3.64 TiB)
[ 223.688263] sd 4:0:0:0: [sdc] 4096-byte physical blocks
[ 223.688387] sd 4:0:0:0: [sdc] Write Protect is off
[ 223.688388] sd 4:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 223.688547] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 223.727131] sd 4:0:0:0: [sdc] Attached SCSI disk
[ 268.475627] usb 3-2.3: new SuperSpeed USB device number 4 using xhci_hcd
[ 268.488441] usb 3-2.3: New USB device found, idVendor=0584, idProduct=0276
[ 268.488442] usb 3-2.3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 268.488444] usb 3-2.3: Product: RS-EC32-U31R RAID1
[ 268.488445] usb 3-2.3: Manufacturer: RATOC Systems,Inc.
[ 268.488446] usb 3-2.3: SerialNumber: 32311643007F
[ 268.492934] scsi host5: uas
[ 268.892450] scsi 5:0:0:0: Direct-Access HGST HDN 724040ALE640 MJAO PQ: 0 ANSI: 6
[ 268.905874] sd 5:0:0:0: Attached scsi generic sg3 type 0
[ 268.911734] sd 5:0:0:0: [sdd] 7813988353 512-byte logical blocks: (4.00 TB/3.64 TiB)
[ 268.911735] sd 5:0:0:0: [sdd] 4096-byte physical blocks
[ 268.911861] sd 5:0:0:0: [sdd] Write Protect is off
[ 268.911862] sd 5:0:0:0: [sdd] Mode Sense: 43 00 00 00
[ 268.912021] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 269.015181] sd 5:0:0:0: [sdd] Attached SCSI disk
[ 285.100714] usb 3-2.1: new SuperSpeed USB device number 5 using xhci_hcd
[ 285.113420] usb 3-2.1: New USB device found, idVendor=0480, idProduct=a006
[ 285.113422] usb 3-2.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 285.113423] usb 3-2.1: Product: ASM1351
[ 285.113424] usb 3-2.1: Manufacturer: Asmedia
[ 285.113425] usb 3-2.1: SerialNumber: 123456789116
[ 285.118584] scsi host6: uas
[ 285.119076] scsi 6:0:0:0: Direct-Access ASMT 2135 0 PQ: 0 ANSI: 6
[ 285.143998] sd 6:0:0:0: Attached scsi generic sg4 type 0
[ 285.144114] sd 6:0:0:0: [sde] Spinning up disk...
[ 286.176992] .
[ 287.201323] .
[ 28...

Read more...

Revision history for this message
In , Yasuaki (yasuaki-redhat-bugs) wrote :

This problem occurs both 512 bytes sector and 4KB sector disks.

[root@test03 work]# cat sys/block/sde/queue/physical_block_size
512
[root@test03 work]# cat sys/block/sde/queue/logical_block_size
512
[root@test03 work]# cat sys/block/sde/queue/optimal_io_size
33553920

Revision history for this message
In , Yasuaki (yasuaki-redhat-bugs) wrote :
Download full text (6.5 KiB)

This problem occurs in Fedora 26 Alpha 4.11.0-0.rc5.git0.1.fc26.x86_64 kernel.

4KB sector disk
[root@test04 ~]# cat /sys/block/sdd/queue/physical_block_size
4096
[root@test04 ~]# cat /sys/block/sdd/queue/logical_block_size
512
[root@test04 ~]# cat /sys/block/sdd/queue/optimal_io_size
33553920
[root@test04 ~]# cat /sys/block/sdd/queue/minimum_io_size
4096

512B sector disk
[root@test04 ~]# cat /sys/block/sde/queue/physical_block_size
512
[root@test04 ~]# cat /sys/block/sde/queue/logical_block_size
512
[root@test04 ~]# cat /sys/block/sde/queue/optimal_io_size
33553920
[root@test04 ~]# cat /sys/block/sde/queue/minimum_io_size
512

==== dmesg uas probe ===============================
[ 14.599778] usb 2-3.1: USB disconnect, device number 3
[ 14.599780] usb 2-3.1.4: USB disconnect, device number 6
[ 14.599782] usb 2-3.1.4.1: USB disconnect, device number 7
[ 14.627609] usb 2-3.1.4.2: USB disconnect, device number 8
[ 14.772222] usb 2-3.2: USB disconnect, device number 4
[ 250.074028] usb 3-2: new SuperSpeed USB device number 2 using xhci_hcd
[ 250.170483] usb 3-2: New USB device found, idVendor=2109, idProduct=0813
[ 250.170488] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 250.170491] usb 3-2: Product: USB3.0 Hub
[ 250.170494] usb 3-2: Manufacturer: VIA Labs, Inc.
[ 250.172733] hub 3-2:1.0: USB hub found
[ 250.172952] hub 3-2:1.0: 4 ports detected
[ 250.768633] usb 2-2: new high-speed USB device number 9 using xhci_hcd
[ 250.938243] usb 2-2: New USB device found, idVendor=2109, idProduct=2813
[ 250.938245] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 250.938246] usb 2-2: Product: USB2.0 Hub
[ 250.938248] usb 2-2: Manufacturer: VIA Labs, Inc.
[ 250.939668] hub 2-2:1.0: USB hub found
[ 250.940530] hub 2-2:1.0: 4 ports detected
[ 311.076093] usb 3-2.4: new SuperSpeed USB device number 3 using xhci_hcd
[ 311.088982] usb 3-2.4: New USB device found, idVendor=0584, idProduct=0276
[ 311.088984] usb 3-2.4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 311.088985] usb 3-2.4: Product: RS-EC32-U31R RAID1
[ 311.088986] usb 3-2.4: Manufacturer: RATOC Systems,Inc.
[ 311.088987] usb 3-2.4: SerialNumber: 32311643000A
[ 311.099686] usbcore: registered new interface driver usb-storage
[ 311.103616] scsi host4: uas
[ 311.103658] usbcore: registered new interface driver uas
[ 311.529050] scsi 4:0:0:0: Direct-Access HGST HDN 724040ALE640 MJAO PQ: 0 ANSI: 6
[ 311.551404] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 311.556400] sd 4:0:0:0: [sdc] 7813988353 512-byte logical blocks: (4.00 TB/3.64 TiB)
[ 311.556401] sd 4:0:0:0: [sdc] 4096-byte physical blocks
[ 311.556525] sd 4:0:0:0: [sdc] Write Protect is off
[ 311.556526] sd 4:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 311.556685] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 311.610063] sdc: sdc1
[ 311.669432] sd 4:0:0:0: [sdc] Attached SCSI disk
[ 311.864341] device-mapper: table: 253:2: adding target device sdc1 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=33553920
[ 311.864342] device-mapper: table:...

Read more...

Revision history for this message
Yasuaki Taniguchi (yasuakit) wrote :

Updated in accord with RedHat bugzilla.

summary: - failed to attach more than 3 uas devices on 16.04 LTS HWE kernel
+ Optimal I/O size isn't calculated properly with uas module, and it may
+ make data inconsistent on the disk and logical volume
Revision history for this message
Yasuaki Taniguchi (yasuakit) wrote :
Download full text (8.4 KiB)

This bug is still alive.
(1) I *can* attach more than three uas devices, but
(2) I/O information, which I can get from /sys/block/sd*/queue, is strange,
(3) parted and LVM can't calculate optimal disk geometries.

======== 4 Disk attachment OK ==============================
[ 223.209197] usb 3-2.4: new SuperSpeed USB device number 3 using xhci_hcd
[ 223.221961] usb 3-2.4: New USB device found, idVendor=0584, idProduct=0276
[ 223.221963] usb 3-2.4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 223.221965] usb 3-2.4: Product: RS-EC32-U31R RAID1
[ 223.221967] usb 3-2.4: Manufacturer: RATOC Systems,Inc.
[ 223.221969] usb 3-2.4: SerialNumber: 32311643000A
[ 223.238444] usbcore: registered new interface driver usb-storage
[ 223.242354] scsi host4: uas
[ 223.242429] usbcore: registered new interface driver uas
[ 223.669308] scsi 4:0:0:0: Direct-Access HGST HDN 724040ALE640 MJAO PQ: 0 ANSI: 6
[ 223.683229] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 223.688262] sd 4:0:0:0: [sdc] 7813988353 512-byte logical blocks: (4.00 TB/3.64 TiB)
[ 223.688263] sd 4:0:0:0: [sdc] 4096-byte physical blocks
[ 223.688387] sd 4:0:0:0: [sdc] Write Protect is off
[ 223.688388] sd 4:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 223.688547] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 223.727131] sd 4:0:0:0: [sdc] Attached SCSI disk
[ 268.475627] usb 3-2.3: new SuperSpeed USB device number 4 using xhci_hcd
[ 268.488441] usb 3-2.3: New USB device found, idVendor=0584, idProduct=0276
[ 268.488442] usb 3-2.3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 268.488444] usb 3-2.3: Product: RS-EC32-U31R RAID1
[ 268.488445] usb 3-2.3: Manufacturer: RATOC Systems,Inc.
[ 268.488446] usb 3-2.3: SerialNumber: 32311643007F
[ 268.492934] scsi host5: uas
[ 268.892450] scsi 5:0:0:0: Direct-Access HGST HDN 724040ALE640 MJAO PQ: 0 ANSI: 6
[ 268.905874] sd 5:0:0:0: Attached scsi generic sg3 type 0
[ 268.911734] sd 5:0:0:0: [sdd] 7813988353 512-byte logical blocks: (4.00 TB/3.64 TiB)
[ 268.911735] sd 5:0:0:0: [sdd] 4096-byte physical blocks
[ 268.911861] sd 5:0:0:0: [sdd] Write Protect is off
[ 268.911862] sd 5:0:0:0: [sdd] Mode Sense: 43 00 00 00
[ 268.912021] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 269.015181] sd 5:0:0:0: [sdd] Attached SCSI disk
[ 285.100714] usb 3-2.1: new SuperSpeed USB device number 5 using xhci_hcd
[ 285.113420] usb 3-2.1: New USB device found, idVendor=0480, idProduct=a006
[ 285.113422] usb 3-2.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 285.113423] usb 3-2.1: Product: ASM1351
[ 285.113424] usb 3-2.1: Manufacturer: Asmedia
[ 285.113425] usb 3-2.1: SerialNumber: 123456789116
[ 285.118584] scsi host6: uas
[ 285.119076] scsi 6:0:0:0: Direct-Access ASMT 2135 0 PQ: 0 ANSI: 6
[ 285.143998] sd 6:0:0:0: Attached scsi generic sg4 type 0
[ 285.144114] sd 6:0:0:0: [sde] Spinning up disk...
[ 286.176992] .
[ 287.201323] .
[ 288.225619] .
[ 289.249948] .
[ 290.274258] .
[ 291.298572] .
[ 292.322884] .
[ 293.347203] .
[ 293.347282] ready
[ 293.349561] sd 6:0:0:0...

Read more...

Revision history for this message
In , Yasuaki (yasuaki-redhat-bugs) wrote :

I made a mistake.

========= Strange I/O Information from sysfs ======================
*BAD* optimal_io_size (512*0xffff)
                       ^^^^^^^^^^^
[root@test03 work]# cat /sys/block/sdc/queue/optimal_io_size
33553920

Bug Watch Updater (bug-watch-updater)
Changed in fedora:
importance: Unknown → Undecided
status: Unknown → Confirmed
Ubuntu Kernel Bot (ubuntu-kernel-bot)
affects: linux-hwe (Ubuntu) → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1666109

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Yasuaki Taniguchi (yasuakit) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected bionic
description: updated
Revision history for this message
Yasuaki Taniguchi (yasuakit) wrote : CRDA.txt

apport information

Revision history for this message
Yasuaki Taniguchi (yasuakit) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Yasuaki Taniguchi (yasuakit) wrote : Lspci.txt

apport information

Revision history for this message
Yasuaki Taniguchi (yasuakit) wrote : Lsusb.txt

apport information

Revision history for this message
Yasuaki Taniguchi (yasuakit) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Yasuaki Taniguchi (yasuakit) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Yasuaki Taniguchi (yasuakit) wrote : ProcEnviron.txt

apport information

Revision history for this message
Yasuaki Taniguchi (yasuakit) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Yasuaki Taniguchi (yasuakit) wrote : ProcModules.txt

apport information

Revision history for this message
Yasuaki Taniguchi (yasuakit) wrote : UdevDb.txt

apport information

Revision history for this message
Yasuaki Taniguchi (yasuakit) wrote : WifiSyslog.txt

apport information

Revision history for this message
Yasuaki Taniguchi (yasuakit) wrote :

I've just sent apport-collect information.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Have you tried "usb-storage.quirks=" [1] ?

Commit 8c4e97ddfe73a0958bb0abf7e6a3bc4cc3e04936 ("usb-storage: Add support for FL_ALWAYS_SYNC flag in the UAS driver") also worth a try but it's not in any released kernel yet. Need to compile a kernel by yourself.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/admin-guide/kernel-parameters.txt#n4530

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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