public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: usb-storage@lists.one-eyed-alien.net, linux-kernel@vger.kernel.org
Subject: Re: single bit errors on files stored on USB-HDDs via USB2/usb_storage
Date: Thu, 7 Dec 2006 15:45:45 -0800	[thread overview]
Message-ID: <20061207154545.6eb516c4.zaitcev@redhat.com> (raw)
In-Reply-To: <45786E58.5070308@citd.de>

On Thu, 07 Dec 2006 20:41:12 +0100, Matthias Schniedermeyer <ms@citd.de> wrote:

> >>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)
> >>[....]
> >>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".

> > This was almost certainly caused by hardware flaws in the USB interface 
> > chips of the enclosures.  There's nothing the kernel can do about it 
> > because the errors aren't reported; all that happens is that incorrect 
> > data is sent to or from the drive.
> 
> So pretty much all ich can do is to pray that the errors don't corrupt
> the Filesystem-Metadata (XFS).

No, this is not all. You should buy a variety of different enclosures
with different chipsets (e.g. find a Freecom if you can), and also
use decent cables.

-- Pete

  reply	other threads:[~2006-12-07 23:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 22:01 single bit errors on files stored on USB-HDDs via USB2/usb_storage Matthias Schniedermeyer
2006-12-07 18:08 ` [usb-storage] " Alan Stern
2006-12-07 19:41   ` Matthias Schniedermeyer
2006-12-07 23:45     ` Pete Zaitcev [this message]
2006-12-08  9:16       ` Matthias Schniedermeyer
2006-12-08 12:21         ` Stefan Richter
2006-12-08 16:18           ` John Stoffel
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
     [not found] <fa./xvi+/Ji/HqNkvnGjUt4pIS9goM@ifi.uio.no>
2006-12-07  0:02 ` Robert Hancock
2006-12-07  9:03   ` 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
  -- strict thread matches above, loose matches on Subject: below --
2006-12-10  8:44 linux
2006-12-10 15:37 ` Clemens Koller

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=20061207154545.6eb516c4.zaitcev@redhat.com \
    --to=zaitcev@redhat.com \
    --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