Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

USB: Buffer I/O error on device dm-0, logical block XYZ

217 views
Skip to first unread message

Andreas

unread,
Apr 12, 2009, 6:00:15 PM4/12/09
to
Hello,

on heavy disk I/O my external USB device gets re-mounted read-only.
(Ok - scp with 2,5MB/s over WLAN)
After this i get EXT3-Errors.

I've already:
- tweaked kernel parameters (see below)
- changed entries in sys-fs

The only thing that works is if i remove the ehci module for USB2.0.

SysLog-Errors:
==============
Apr 12 17:45:08 elrond kernel: [ 628.205804] usb-storage: device found
at 2
Apr 12 17:45:08 elrond kernel: [ 628.205825] usb-storage: waiting for
device to settle before scanning
Apr 12 17:45:13 elrond kernel: [ 633.206246] usb-storage: device scan
complete
Apr 12 17:45:13 elrond kernel: [ 633.218523] scsi 3:0:0:0:
Direct-Access WD 3200JB External 0412 PQ: 0 ANSI: 0
Apr 12 17:45:13 elrond kernel: [ 633.252002] sd 3:0:0:0: [sdc]
625142448 512-byte hardware sectors: (320 GB/298 GiB)
Apr 12 17:45:13 elrond kernel: [ 633.262009] sd 3:0:0:0: [sdc] Write
Protect is off
Apr 12 17:45:13 elrond kernel: [ 633.262057] sd 3:0:0:0: [sdc] Mode
Sense: 33 00 00 00
Apr 12 17:45:13 elrond kernel: [ 633.262083] sd 3:0:0:0: [sdc] Assuming
drive cache: write through
Apr 12 17:45:13 elrond kernel: [ 633.285968] sd 3:0:0:0: [sdc]
625142448 512-byte hardware sectors: (320 GB/298 GiB)
Apr 12 17:45:13 elrond kernel: [ 633.296113] sd 3:0:0:0: [sdc] Write
Protect is off
Apr 12 17:45:13 elrond kernel: [ 633.296148] sd 3:0:0:0: [sdc] Mode
Sense: 33 00 00 00
Apr 12 17:45:13 elrond kernel: [ 633.296170] sd 3:0:0:0: [sdc] Assuming
drive cache: write through
Apr 12 17:45:13 elrond kernel: [ 633.296313] sdc: sdc1
Apr 12 17:45:13 elrond kernel: [ 633.314525] sd 3:0:0:0: [sdc] Attached
SCSI disk
Apr 12 17:45:13 elrond kernel: [ 633.315315] sd 3:0:0:0: Attached scsi
generic sg1 type 0
Apr 12 17:45:16 elrond kernel: [ 635.773406] ext3_abort called.
Apr 12 17:45:16 elrond kernel: [ 635.773484] EXT3-fs error (device
dm-0): ext3_journal_start_sb: Detected aborted journal
Apr 12 17:45:16 elrond kernel: [ 635.773588] Remounting filesystem
read-only
Apr 12 17:46:27 elrond kernel: [ 706.828326] EXT3-fs error (device
dm-0): ext3_get_inode_loc: unable to read inode block - inode=1015809
, block=4063234
Apr 12 17:46:27 elrond kernel: [ 706.833874] EXT3-fs error (device
dm-0): ext3_get_inode_loc: unable to read inode block - inode=1015809
, block=4063234
Apr 12 17:46:27 elrond kernel: [ 706.840217] EXT3-fs error (device
dm-0): ext3_get_inode_loc: unable to read inode block - inode=1015810
, block=4063234
...
...
...

My Setup:
=========
Kernel:
2.6.29-02062901-generic #02062901 SMP (Ubuntu 2.6.29.1)

lspci:
00:00.0 Host bridge: Transmeta Corporation LongRun Northbridge (rev 03)
00:00.1 RAM memory: Transmeta Corporation SDRAM controller
00:00.2 RAM memory: Transmeta Corporation BIOS scratchpad
00:09.0 VGA compatible controller: Silicon Integrated Systems [SiS]
315PRO PCI/AGP VGA Display Adapter
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc.
VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II]
(rev 74)


/sys-parameters:
echo 1024 > /sys/block/sdb/device/max_sectors
echo 1 > /sys/block/sdb/device/scsi_diskXYZ/allow_restart


grub-parameters:
all_generic_ide combined_mode=ide enable_atapi=1 noapic

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Andreas

unread,
Apr 13, 2009, 4:00:21 AM4/13/09
to
More information from dmesg:

[ 223.882858] EXT3 FS on dm-0, internal journal
[ 223.882917] EXT3-fs: recovery complete.
[ 223.924925] EXT3-fs: mounted filesystem with ordered data mode.
[ 967.909484] kjournald starting. Commit interval 5 seconds
[ 967.915929] EXT3 FS on dm-0, internal journal
[ 967.917466] EXT3-fs: mounted filesystem with ordered data mode.
[ 1740.369047] ehci_hcd 0000:00:10.3: fatal error
[ 1740.370244] ehci_hcd 0000:00:10.3: HC died; cleaning up
[ 1740.370489] usb 1-3: USB disconnect, address 2
[ 1740.394603] sd 2:0:0:0: [sdb] Unhandled error code
[ 1740.394636] sd 2:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT
driverbyte=DRIVER_OK,SUGGEST_OK
[ 1740.394671] end_request: I/O error, dev sdb, sector 614444231
[ 1740.394867] Buffer I/O error on device dm-0, logical block 76805264
[ 1740.394943] lost page write due to I/O error on dm-0
[ 1740.394984] Buffer I/O error on device dm-0, logical block 76805265
[ 1740.395053] lost page write due to I/O error on dm-0
[ 1740.395149] sd 2:0:0:0: [sdb] Unhandled error code
[ 1740.395164] sd 2:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT
driverbyte=DRIVER_OK,SUGGEST_OK
[ 1740.395191] end_request: I/O error, dev sdb, sector 614444247
[ 1740.395519] Buffer I/O error on device dm-0, logical block 76805266
[ 1740.395607] lost page write due to I/O error on dm-0
[ 1740.395647] Buffer I/O error on device dm-0, logical block 76805267
[ 1740.396746] lost page write due to I/O error on dm-0
[ 1740.453282] Buffer I/O error on device dm-0, logical block 76805268
[ 1740.453424] lost page write due to I/O error on dm-0
[ 1740.469714] Buffer I/O error on device dm-0, logical block 76805269
[ 1740.469853] lost page write due to I/O error on dm-0
[ 1740.469899] Buffer I/O error on device dm-0, logical block 76805270
[ 1740.469971] lost page write due to I/O error on dm-0
[ 1740.470618] Buffer I/O error on device dm-0, logical block 76805271
[ 1740.470718] lost page write due to I/O error on dm-0
[ 1740.474334] Buffer I/O error on device dm-0, logical block 76805272
[ 1740.474445] lost page write due to I/O error on dm-0
[ 1740.474484] Buffer I/O error on device dm-0, logical block 76805273
[ 1740.474552] lost page write due to I/O error on dm-0
[ 1740.588666] JBD: Detected IO errors while flushing file data on dm-0
[ 1740.602160] Aborting journal on device dm-0.
[ 1740.645164] ext3_abort called.
[ 1740.645282] EXT3-fs error (device dm-0): ext3_journal_start_sb:
Detected aborted journal
[ 1740.645387] Remounting filesystem read-only
[ 1740.673193] usb 3-1: new full speed USB device using uhci_hcd and
address 2
[ 1741.041341] JBD: Detected IO errors while flushing file data on dm-0
[ 1741.927016] usb 3-1: not running at top speed; connect to a high
speed hub
[ 1741.959914] usb 3-1: configuration #1 chosen from 1 choice
[ 1743.164192] uba: uba1
[ 1743.230384] usbcore: registered new interface driver ub
[ 1743.402098] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177505, block=76709892
[ 1743.402663] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177505, block=76709892
[ 1743.412724] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177506, block=76709892
[ 1743.417446] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177506, block=76709892
[ 1743.422406] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177507, block=76709892
[ 1743.423233] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177507, block=76709892
[ 1743.448445] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177508, block=76709892
[ 1743.453589] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177508, block=76709892
[ 1743.458889] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177509, block=76709892
[ 1743.459245] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177509, block=76709892
[ 1743.466356] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177510, block=76709892
[ 1743.466728] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177510, block=76709892
[ 1743.474432] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177511, block=76709892
[ 1743.474930] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177511, block=76709892
[ 1743.487927] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177512, block=76709892
[ 1743.508633] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177512, block=76709892
[ 1743.553544] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177513, block=76709892
[ 1743.554867] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177513, block=76709892
[ 1743.560664] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177514, block=76709892
[ 1743.561071] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177514, block=76709892
[ 1743.566794] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177515, block=76709892
[ 1743.567090] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177515, block=76709892
[ 1743.578335] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177516, block=76709892
[ 1743.578626] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177516, block=76709892
[ 1743.602519] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177517, block=76709892
[ 1743.602806] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177517, block=76709892
[ 1743.623868] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177518, block=76709892
[ 1743.632459] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177518, block=76709892
[ 1743.638713] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177519, block=76709892
[ 1743.639212] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177519, block=76709892
[ 1743.647400] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177520, block=76709892
[ 1743.647715] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177520, block=76709892
[ 1743.651519] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177521, block=76709893
[ 1743.651780] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177521, block=76709893
[ 1743.655171] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177522, block=76709893
[ 1743.655428] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177522, block=76709893
[ 1743.672695] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177523, block=76709893
[ 1743.672975] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177523, block=76709893
[ 1743.678953] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177524, block=76709893
[ 1743.679240] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177524, block=76709893
[ 1743.683107] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177525, block=76709893
[ 1743.683379] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable
to read inode block - inode=19177525, block=76709893
[ 1743.689641] EXT3-fs error (device dm-0): ext3_find_entry: reading
directory #19177473 offset 0
[ 1743.694495] EXT3-fs error (device dm-0): ext3_find_entry: reading
directory #19177473 offset 0
[ 1743.698144] EXT3-fs error (device dm-0): ext3_find_entry: reading
directory #19177473 offset 0
[ 1743.702033] EXT3-fs error (device dm-0): ext3_find_entry: reading
directory #19177473 offset 0
[ 1743.710452] EXT3-fs error (device dm-0): ext3_find_entry: reading
directory #12806119 offset 0
[ 1743.714198] EXT3-fs error (device dm-0): ext3_find_entry: reading
directory #12806119 offset 0
[ 1743.725600] EXT3-fs error (device dm-0): ext3_find_entry: reading
directory #12806119 offset 0
[ 1743.729815] EXT3-fs error (device dm-0): ext3_find_entry: reading
directory #12806119 offset 0

Robert Hancock

unread,
Apr 13, 2009, 8:50:08 PM4/13/09
to
(ccing linux-usb)

Andreas wrote:
> More information from dmesg:
>
> [ 223.882858] EXT3 FS on dm-0, internal journal
> [ 223.882917] EXT3-fs: recovery complete.
> [ 223.924925] EXT3-fs: mounted filesystem with ordered data mode.
> [ 967.909484] kjournald starting. Commit interval 5 seconds
> [ 967.915929] EXT3 FS on dm-0, internal journal
> [ 967.917466] EXT3-fs: mounted filesystem with ordered data mode.
> [ 1740.369047] ehci_hcd 0000:00:10.3: fatal error
> [ 1740.370244] ehci_hcd 0000:00:10.3: HC died; cleaning up
> [ 1740.370489] usb 1-3: USB disconnect, address 2

This is the real killer here, everything else is just collateral damage.
Looks like your USB host controller indicated a fatal host system
error, apparently because of an error on the PCI bus, which seems rather
bizarre. Some kind of hardware problem?

> [ 1740.394603] sd 2:0:0:0: [sdb] Unhandled error code
> [ 1740.394636] sd 2:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT
> driverbyte=DRIVER_OK,SUGGEST_OK
> [ 1740.394671] end_request: I/O error, dev sdb, sector 614444231
> [ 1740.394867] Buffer I/O error on device dm-0, logical block 76805264
> [ 1740.394943] lost page write due to I/O error on dm-0
> [ 1740.394984] Buffer I/O error on device dm-0, logical block 76805265
> [ 1740.395053] lost page write due to I/O error on dm-0
> [ 1740.395149] sd 2:0:0:0: [sdb] Unhandled error code
> [ 1740.395164] sd 2:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT
> driverbyte=DRIVER_OK,SUGGEST_OK
> [ 1740.395191] end_request: I/O error, dev sdb, sector 614444247
> [ 1740.395519] Buffer I/O error on device dm-0, logical block 76805266
> [ 1740.395607] lost page write due to I/O error on dm-0

--

0 new messages