From: Soeren Sonnenburg <kernel@nn7.de>
To: Bernd Schubert <bs@q-leap.de>
Cc: Tejun Heo <htejun@gmail.com>,
linux-ide@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: sata sil3114 vs. certain seagate drives results in filesystem corruptions
Date: Mon, 22 Oct 2007 12:56:17 +0000 [thread overview]
Message-ID: <1193057777.10246.37.camel@localhost> (raw)
In-Reply-To: <200710221302.12229.bs@q-leap.de>
On Mon, 2007-10-22 at 13:02 +0200, Bernd Schubert wrote:
> On Monday 22 October 2007 12:36:32 Soeren Sonnenburg wrote:
> > > but as much as it fits onto the disk. On reading back this file, the
> > > filesystem will report errors somewhere between 50GB and 230GB (disk size
> > > is 250GB).
> >
> > Wow, I really see lots of corruptions (well every 1-2 GB a couple of
> > bytes are corrupted). Are you getting similiarly many in the 50G - 230G
> > region?
>
> I never tested what is corrupted. Well, a diff over 250GB would take quite a
> lot of time...
Actually hexdump does not display duplicate lines, so if your file is
really all zeros it will only display a single line + the count, however
I think it is not so optimized...
Soeren
prev parent reply other threads:[~2007-10-22 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-20 6:55 sata sil3114 vs. certain seagate drives results in filesystem corruptions Soeren Sonnenburg
2007-10-22 2:12 ` Tejun Heo
2007-10-22 5:56 ` Soeren Sonnenburg
2007-10-22 9:48 ` Bernd Schubert
2007-10-22 10:36 ` Soeren Sonnenburg
2007-10-22 10:59 ` Bernd Schubert
2007-10-23 6:57 ` Soeren Sonnenburg
2007-10-22 11:02 ` Bernd Schubert
2007-10-22 12:56 ` Soeren Sonnenburg [this message]
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=1193057777.10246.37.camel@localhost \
--to=kernel@nn7.de \
--cc=bs@q-leap.de \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).