← Back to team overview

kernel-packages team mailing list archive

[Bug 1205816] Re: Linux software raid + usb3 storage + heavy disk activity = recipe for disaster in raring?

 

Tried 3.10.5 from the mainline ppa.

The situation if possible is even worse.

At boot I get tons of I/O errors on the usb3 disks that make up the raid
components.

In dmesg I find

[   32.202815] sd 8:0:0:0: [sdf] No Caching mode page present
[   32.202831] sd 8:0:0:0: [sdf] Assuming drive cache: write through
[   33.740587] sd 8:0:0:1: [sdg] No Caching mode page present
[   33.740603] sd 8:0:0:1: [sdg] Assuming drive cache: write through
[   37.195945] usb 3-2: USB disconnect, device number 3
[   37.258746] sd 8:0:0:0: [sdf] Unhandled error code
[   37.258750] sd 8:0:0:0: [sdf]  
[   37.258752] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.258755] sd 8:0:0:0: [sdf] CDB: 
[   37.258756] Read(10): 28 00 00 00 00 00 00 00 08 00
[   37.258762] end_request: I/O error, dev sdf, sector 0
[   37.258773] Buffer I/O error on device sdf, logical block 0
[   37.258793] sd 8:0:0:1: [sdg] Unhandled error code
[   37.258794] sd 8:0:0:1: [sdg]  
[   37.258795] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.258797] sd 8:0:0:1: [sdg] CDB: 
[   37.258798] Read(10): 28 20 00 00 00 00 00 00 08 00
[   37.258802] end_request: I/O error, dev sdg, sector 0
[   37.258811] Buffer I/O error on device sdg, logical block 0
[   37.258814] ldm_validate_partition_table(): Disk read failed.
[   37.258827] Dev sdf: unable to read RDB block 0
[   37.258847] sd 8:0:0:1: [sdg] Unhandled error code
[   37.258848]  sdf: unable to read partition table
[   37.258852] sd 8:0:0:1: [sdg]  
[   37.258854] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.258856] sd 8:0:0:1: [sdg] CDB: 
[   37.258858] Read(10): 28 20 00 00 00 00 00 00 08 00
[   37.258864] end_request: I/O error, dev sdg, sector 0
[   37.258875] Buffer I/O error on device sdg, logical block 0
[   37.258941] sd 8:0:0:1: [sdg] Unhandled error code
[   37.258944] sd 8:0:0:1: [sdg]  
[   37.258946] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.258948] sd 8:0:0:1: [sdg] CDB: 
[   37.258949] Read(10): 28 20 00 00 00 00 00 00 08 00
[   37.258956] end_request: I/O error, dev sdg, sector 0
[   37.258967] Buffer I/O error on device sdg, logical block 0
[   37.258994] sd 8:0:0:1: [sdg] Unhandled error code
[   37.258996] sd 8:0:0:1: [sdg]  
[   37.258998] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.258999] sd 8:0:0:1: [sdg] CDB: 
[   37.259000] Read(10): 28 20 00 00 00 00 00 00 08 00
[   37.259005] end_request: I/O error, dev sdg, sector 0
[   37.259015] Buffer I/O error on device sdg, logical block 0
[   37.259036] sd 8:0:0:1: [sdg] Unhandled error code
[   37.259038] sd 8:0:0:1: [sdg]  
[   37.259039] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.259041] sd 8:0:0:1: [sdg] CDB: 
[   37.259041] Read(10): 28 20 00 00 00 00 00 00 08 00
[   37.259046] end_request: I/O error, dev sdg, sector 0
[   37.259064] Buffer I/O error on device sdg, logical block 0
[   37.259067] sd 8:0:0:0: [sdf] READ CAPACITY failed
[   37.259068] sd 8:0:0:0: [sdf]  
[   37.259069] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.259070] sd 8:0:0:0: [sdf] Sense not available.
[   37.259090] ldm_validate_partition_table(): Disk read failed.
[   37.259095] sd 8:0:0:0: [sdf] Asking for cache data failed
[   37.259099] sd 8:0:0:1: [sdg] Unhandled error code
[   37.259100] sd 8:0:0:1: [sdg]  
[   37.259100] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.259101] sd 8:0:0:1: [sdg] CDB: 
[   37.259103] Read(10): 28 20 00 00 00 00 00 00 08 00
[   37.259104] end_request: I/O error, dev sdg, sector 0
[   37.259105] Buffer I/O error on device sdg, logical block 0
[   37.259114] sd 8:0:0:1: [sdg] Unhandled error code
[   37.259116] sd 8:0:0:1: [sdg]  
[   37.259117] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.259119] sd 8:0:0:1: [sdg] CDB: 
[   37.259124] Read(10): 28 20 00 00 00 00 00 00 08 00
[   37.259125] end_request: I/O error, dev sdg, sector 0
[   37.259125] Buffer I/O error on device sdg, logical block 0
[   37.259135] sd 8:0:0:1: [sdg] Unhandled error code
[   37.259136] sd 8:0:0:1: [sdg]  
[   37.259136] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.259137] sd 8:0:0:1: [sdg] CDB: 
[   37.259140] Read(10): 28 20 00 00 00 00 00 00 08 00
[   37.259141] end_request: I/O error, dev sdg, sector 0
[   37.259142] Buffer I/O error on device sdg, logical block 0
[   37.259151] sd 8:0:0:1: [sdg] Unhandled error code
[   37.259152] sd 8:0:0:1: [sdg]  
[   37.259152] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.259153] sd 8:0:0:1: [sdg] CDB: 
[   37.259155] Read(10): 28 20 00 00 00 00 00 00 08 00
[   37.259156] end_request: I/O error, dev sdg, sector 0
[   37.259156] Buffer I/O error on device sdg, logical block 0
[   37.259160] Dev sdg: unable to read RDB block 0
[   37.259167] sd 8:0:0:1: [sdg] Unhandled error code
[   37.259167] sd 8:0:0:1: [sdg]  
[   37.259168] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.259169] sd 8:0:0:1: [sdg] CDB: 
[   37.259171] Read(10): 28 20 00 00 00 00 00 00 08 00
[   37.259180] sd 8:0:0:1: [sdg] Unhandled error code
[   37.259181] sd 8:0:0:1: [sdg]  
[   37.259182] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.259183] sd 8:0:0:1: [sdg] CDB: 
[   37.259185] Read(10): 28 20 00 00 00 00 00 00 08 00
[   37.259197] sd 8:0:0:1: [sdg] Unhandled error code
[   37.259199] sd 8:0:0:1: [sdg]  
[   37.259200] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.259202] sd 8:0:0:1: [sdg] CDB: 
[   37.259207] Read(10): 28 20 00 00 00 18 00 00 08 00
[   37.259214] sd 8:0:0:1: [sdg] Unhandled error code
[   37.259215] sd 8:0:0:1: [sdg]  
[   37.259215] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.259216] sd 8:0:0:1: [sdg] CDB: 
[   37.259218] Read(10): 28 20 00 00 00 18 00 00 08 00
[   37.259228] sd 8:0:0:1: [sdg] Unhandled error code
[   37.259229] sd 8:0:0:1: [sdg]  
[   37.259229] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.259230] sd 8:0:0:1: [sdg] CDB: 
[   37.259232] Read(10): 28 20 00 00 00 00 00 00 08 00
[   37.259242] sd 8:0:0:1: [sdg] Unhandled error code
[   37.259243] sd 8:0:0:1: [sdg]  
[   37.259245] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.259246] sd 8:0:0:1: [sdg] CDB: 
[   37.259249] Read(10): 28 20 00 00 00 00 00 00 08 00
[   37.259252]  sdg: unable to read partition table
[   37.259298] sd 8:0:0:0: [sdf] Assuming drive cache: write through
[   37.259331] sd 8:0:0:0: [sdf] Attached SCSI disk
[   37.259377] sd 8:0:0:1: [sdg] READ CAPACITY failed
[   37.259379] sd 8:0:0:1: [sdg]  
[   37.259381] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   37.259382] sd 8:0:0:1: [sdg] Sense not available.
[   37.259397] sd 8:0:0:1: [sdg] Asking for cache data failed
[   37.259417] sd 8:0:0:1: [sdg] Assuming drive cache: write through
[   37.259443] sd 8:0:0:1: [sdg] Attached SCSI disk
[   38.778511] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro
[   39.945341] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
[   40.570302] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
[   40.938592] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
[   41.501325] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
[   41.810105] usb 3-2: new high-speed USB device number 6 using xhci_hcd
[   41.833142] usb 3-2: New USB device found, idVendor=152d, idProduct=2551
[   41.833147] usb 3-2: New USB device strings: Mfr=10, Product=11, SerialNumber=3
[   41.833149] usb 3-2: Product: USB Mass Storage
[   41.833151] usb 3-2: Manufacturer: G-Max Technology Co., Ltd.
[   41.833153] usb 3-2: SerialNumber: 000000000025
[   41.836782] usb-storage 3-2:1.0: USB Mass Storage device detected
[   41.836851] scsi9 : usb-storage 3-2:1.0
[   42.841789] scsi 9:0:0:0: Direct-Access     HGST HTS 541010A9E680     0000 PQ: 0 ANSI: 2 CCS
[   42.842468] scsi 9:0:0:1: Direct-Access     HGST HTS 541010A9E680     0000 PQ: 0 ANSI: 2 CCS
[   42.842687] sd 9:0:0:0: Attached scsi generic sg6 type 0
[   42.842828] sd 9:0:0:1: Attached scsi generic sg7 type 0
[   42.843332] sd 9:0:0:0: [sdf] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[   42.843469] sd 9:0:0:1: [sdg] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)

... and only from this point on the system seems to be able to mount the
raid.

It is totally unclear to me at this point if latest kernels have the
same problem as 3.8, a completely different problem or both.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1205816

Title:
  Linux software raid + usb3 storage + heavy disk activity = recipe for
  disaster in raring?

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I have a system with a Nec PCI USB 3 adapter (Renesas Technology Corp.
  uPD720201 USB 3.0 Host Controller) with a Lindy USB3 disk case for 2
  disks attached to it (JMicron Technology Corp. chipset) and two 1TB
  disks inside.  The Lindy disk case is configured to show the 2 disk
  units (in windows it supports fake raid to with proper dip-switch
  configuration).

  Linux is configured to see the two disks as a software raid 1 unit.
  LVM is set up on top of the raid.  Ext4 partitions are created in LVM.

  Apparently things work just fine.  However, if I have heavy disk
  activity (e.g. copy a large iso file to the raid storage), there are
  very frequent issues. In the worst case the machine freezes (flashing
  leds) trashing all the last data written on the raid storage. When the
  machine comes up the raid starts resync which is a painful activity.
  No visible oops, nothing in syslog. In the best case, the array simply
  looses sync.

  Even when things work fine, the disks in the array make clunky noise
  that does not seem proper.

  Also tried with a VIA USB3 controller and with the motherboard
  integrated USB2 controllers. With USB2 things are much slowlier, but
  the result is invariably the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image 3.8.0.26.44
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  callegar   2818 F.... pulseaudio
  Date: Sun Jul 28 12:09:31 2013
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=c50b4249-43ed-49ef-a3d8-ec7aa9718265
  IwConfig:
   usb0      no wireless extensions.
   
   eth0      no wireless extensions.
   
   lo        no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-26-generic root=/dev/mapper/DISK00-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-26-generic N/A
   linux-backports-modules-3.8.0-26-generic  N/A
   linux-firmware                            1.106
  RfKill:
   0: hci0: Bluetooth
   	Soft blocked: no
   	Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to raring on 2013-05-05 (83 days ago)
  WpaSupplicantLog:
   
  dmi.bios.date: 04/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: N68-S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205816/+subscriptions


References