From: Robert Hancock <hancockr@shaw.ca>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: linux-kernel@vger.kernel.org, usb-storage@lists.one-eyed-alien.net
Subject: Re: single bit errors on files stored on USB-HDDs via USB2/usb_storage
Date: Wed, 06 Dec 2006 18:02:58 -0600 [thread overview]
Message-ID: <45775A32.2050506@shaw.ca> (raw)
In-Reply-To: <fa./xvi+/Ji/HqNkvnGjUt4pIS9goM@ifi.uio.no>
Matthias Schniedermeyer wrote:
> Hi
>
>
> I'm using a Bunch auf HDDs in USB-Enclosures for storing files.
> (currently 38 HDD, with a total capacity of 9,5 TB of which 8,5 TB is used)
All the same enclosure type?
> This time i kept the defective files and used "vbindiff" to show me the
> difference. Strangly in EVERY case the difference is a single bit in a
> sequence of "0xff"-Bytes inside a block of varing bit-values that
> changed a "0xff" into a "0xf7".
> Also interesting is that each error is at a 0xXXXXXXX5-Position
>
> Attached is a file with 5 of the 6 differences named 1-5. Of each of the
> 5 2x3 lines-blocks the first 3 lines are the original the following 3
> lines contain the error in the middle row 6th value.
>
> NEVER did i see any messages in syslog regarding erros or an aborting
> program due to errors passed down from the kernel or something like that.
The fact that the corruption seems data dependent would seem to me to
point to some kind of hardware problem. I would tend to suspect the
USB-to-IDE converters in the enclosures as being faulty or something
like that..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-12-07 1:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa./xvi+/Ji/HqNkvnGjUt4pIS9goM@ifi.uio.no>
2006-12-07 0:02 ` Robert Hancock [this message]
2006-12-07 9:03 ` single bit errors on files stored on USB-HDDs via USB2/usb_storage Matthias Schniedermeyer
[not found] ` <fa.nPT9ZJ5poT8fZx3aWy0MqRK/gto@ifi.uio.no>
[not found] ` <fa.aML3aAeWqfac08XNpQa7Zu0AC8w@ifi.uio.no>
2006-12-08 3:18 ` Robert Hancock
2006-12-08 9:07 ` Matthias Schniedermeyer
2006-12-08 10:25 ` Stefan Richter
2006-12-08 10:39 ` Matthias Schniedermeyer
2006-12-08 11:01 ` Oliver Neukum
2006-12-08 12:27 ` Stefan Richter
2006-12-09 6:11 ` Ben Nizette
2006-12-09 8:18 ` Oliver Neukum
2006-12-09 10:16 ` Ben Nizette
2006-12-10 8:44 linux
2006-12-10 15:37 ` Clemens Koller
-- strict thread matches above, loose matches on Subject: below --
2006-12-07 18:08 [usb-storage] " Alan Stern
2006-12-07 19:41 ` Matthias Schniedermeyer
2006-12-07 23:45 ` Pete Zaitcev
2006-12-08 9:16 ` Matthias Schniedermeyer
2006-12-08 12:21 ` Stefan Richter
2006-12-08 16:18 ` John Stoffel
2006-12-06 22:01 Matthias Schniedermeyer
2006-12-07 22:10 ` DervishD
2006-12-07 22:57 ` Matthias Schniedermeyer
2006-12-07 23:05 ` Jan Engelhardt
2006-12-08 9:32 ` DervishD
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=45775A32.2050506@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=ms@citd.de \
--cc=usb-storage@lists.one-eyed-alien.net \
/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