kernel-packages team mailing list archive

[Sergio Callegari <sergio.callegari@xxxxxxxxx>]

In the best case where there is no freeze, the system logs get full of
entries like

Buffer I/O error on device dm-8, logical block 11595768

literally tons of them. And at the end

[ 2472.637908] Buffer I/O error on device dm-8, logical block 11595769
[ 2472.637909] Buffer I/O error on device dm-8, logical block 11595770
[ 2472.637911] Buffer I/O error on device dm-8, logical block 11595771
[ 2472.637912] Buffer I/O error on device dm-8, logical block 11595772
[ 2472.637913] Buffer I/O error on device dm-8, logical block 11595773
[ 2472.637915] Buffer I/O error on device dm-8, logical block 11595774
[ 2472.637916] Buffer I/O error on device dm-8, logical block 11595775
[ 2472.637918] EXT4-fs warning (device dm-8): ext4_end_bio:317: I/O error writing to inode 3145791 (offset 8355840 size 32768 starting block 11595768)
[ 2472.637922] quiet_error: 39 callbacks suppressed
[ 2472.637924] Buffer I/O error on device dm-8, logical block 6324224
[ 2472.637925] lost page write due to I/O error on dm-8
[ 2472.637933] Buffer I/O error on device dm-8, logical block 0
[ 2472.637934] lost page write due to I/O error on dm-8
[ 2472.637938] JBD2: Error -5 detected when updating journal superblock for dm-8-8.
[ 2472.637948] EXT4-fs error (device dm-8): ext4_journal_start_sb:349: Detected aborted journal
[ 2472.637952] EXT4-fs (dm-8): Remounting filesystem read-only
[ 2472.637956] EXT4-fs (dm-8): previous I/O error to superblock detected
[ 2472.638232] md: md0: resync done.
[ 2472.638436] md: checkpointing resync of md0.
[ 2472.638452] md: super_written gets error=-19, uptodate=0
[ 2472.638466] md: super_written gets error=-19, uptodate=0
[ 2472.638475] Buffer I/O error on device dm-8, logical block 0
[ 2472.638476] lost page write due to I/O error on dm-8
[ 2472.638489] EXT4-fs (dm-8): I/O error while writing superblock
[ 2472.638491] EXT4-fs error (device dm-8): ext4_journal_start_sb:349: Detected aborted journal
[ 2472.638506] EXT4-fs (dm-8): ext4_da_writepages: jbd2_start: 8983 pages, ino 3145792; err -30
[ 2472.638575] md: resync of RAID array md0
[ 2472.638577] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[ 2472.638578] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync.
[ 2472.638582] md: using 128k window, over a total of 976630336k.
[ 2472.638583] md: resuming resync of md0 from checkpoint.
[ 2472.638702] md: md0: resync done.
[ 2472.638781] md: super_written gets error=-19, uptodate=0
[ 2472.638788] md: super_written gets error=-19, uptodate=0
[ 2472.671648] md: unbind<sde1>
[ 2472.678542] md: export_rdev(sde1)
[ 2472.678603] md: super_written gets error=-19, uptodate=0
[ 2472.755202] xhci_hcd 0000:03:00.0: Bad Slot ID 6
[ 2472.755213] xhci_hcd 0000:03:00.0: Could not allocate xHCI USB device data structures
[ 2472.755225] hub 4-0:1.0: couldn't allocate port 2 usb_device
[ 2472.842606] md: super_written gets error=-19, uptodate=0

At this point the raid is gone.

-- 
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:
  Confirmed

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