All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Guggenberger  <christian.guggenberger@physik.uni-regensburg.de>
To: mgarski@post.pl
Cc: lord@xfs.org, nathans@sgi.com, alistair@devzero.co.uk,
	linux-kernel@vger.kernel.org
Subject: Re: Copying huge amount of data on ReiserFS, XFS and Silicon Image 3112 cause oops.
Date: Tue, 14 Sep 2004 21:04:30 +0200	[thread overview]
Message-ID: <1095188670.2931.10.camel@localhost> (raw)

On Tue, Sep 14, 2004 at 12:44:25AM +0200, Marcin Garski wrote:
> [Please CC me on replies, I am not subscribed to the list, thanks]
> 
> Hello,
> 
> I bought a new HDD Maxtor 6Y160M0 and connected it as hdg to Sil 3112 
> (CONFIG_BLK_DEV_SIIMAGE) on Abit NF7-S V2.0. I also have ST380013AS 
> (with Fedora Core 2 on hde2 and 2.6.5 kernel) as hde.

IIRC, there have been some reports on lkml regarding data/fs corruption in combination with
SIL 3112 (both IDE and SATA drivers) and Seagate drives.

searching lkml archives leads at least to

http://marc.theaimsgroup.com/?l=linux-kernel&m=108766862501122&w=4
(this report is based on 2.6.5/2.6.7)

maybe Jeff Garzik can comment more on these problems. I'm not sure, if
these probs are supposed zo be fixed in recent kernels.


cheers.
 - christian



             reply	other threads:[~2004-09-14 19:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-14 19:04 Christian Guggenberger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-09-18 21:18 Copying huge amount of data on ReiserFS, XFS and Silicon Image 3112 cause oops Marcin Garski
2004-09-14 15:42 Marcin Garski
2004-09-13 22:44 Marcin Garski
2004-09-14  8:14 ` Nathan Scott
2004-09-14 10:59   ` Alistair John Strachan
2004-09-14 14:12     ` Steve Lord
2004-09-14 15:01       ` Alistair John Strachan

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=1095188670.2931.10.camel@localhost \
    --to=christian.guggenberger@physik.uni-regensburg.de \
    --cc=alistair@devzero.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lord@xfs.org \
    --cc=mgarski@post.pl \
    --cc=nathans@sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.