From: Rusty Russell <rusty@rustcorp.com.au>
To: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Greg KH <greg@kroah.com>
Subject: 2.6: USB disk unusable level of data corruption
Date: Fri, 04 Feb 2005 23:16:22 +1100 [thread overview]
Message-ID: <1107519382.1703.7.camel@localhost.localdomain> (raw)
OK, I recently made the mistake of buying a USB case with a drive in it
and putting my home directory on it. I have since then had multiple
ext3 and ext2 errors: 2.6.8, 2.6.9, 2.6.10 and 2.6.11-rc3 all exhibit
the problem within an hour of stress (untarring a fresh kernel tree, cp
-al'ing to apply patches repeatedly, my normal workload). I haven't had
any similar problems on my internal IDE drive. 2.4 succeeded once, and
once had data corruption (although nowhere near as as bad as the 2.6
corruption, and it got much further).
I realize "ub" exists, but it doesn't seem to want to deal with a disk
device.
Is USB/SCSI just terminally broken under 2.6? I'll be getting a power
supply to test the drive using firewire, which it also supports, to
ensure this isn't a disk issue (although the 2.4 goodness undermines
this theory).
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 6 ports detected
usb 2-1: USB disconnect, address 2
usb 4-3: new high speed USB device using address 2
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: HTS72606 Model: 0M9AT00 Rev: MH4O
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sda: 117210240 512-byte hdwr sectors (60012 MB)
sda: assuming drive cache: write through
/dev/scsi/host1/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 >
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
USB Mass Storage device found at 2
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
next reply other threads:[~2005-02-04 12:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 12:16 Rusty Russell [this message]
2005-02-04 20:41 ` [linux-usb-devel] 2.6: USB disk unusable level of data corruption David Brownell
2005-02-05 0:39 ` John Stoffel
2005-02-06 15:59 ` Giuseppe Bilotta
2005-02-07 4:01 ` David Brownell
2005-02-07 22:39 ` Giuseppe Bilotta
2005-02-07 2:55 ` Rusty Russell
2005-02-07 5:15 ` David Brownell
2005-02-07 6:46 ` Rusty Russell
2005-02-04 20:55 ` Alan Stern
2005-02-04 21:31 ` David Brownell
2005-02-06 5:18 ` 2.6: USB Storage hangs machine on bootup for ~2 minutes Parag Warudkar
2005-02-04 21:37 ` 2.6: USB disk unusable level of data corruption Pete Zaitcev
2005-02-05 0:40 ` Parag Warudkar
2005-02-05 1:44 ` Greg KH
2005-02-05 2:30 ` Parag Warudkar
2005-02-05 4:54 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1107519382.1703.7.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox