public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Serial ATA (SATA) for Linux status report
Date: Fri, 05 Dec 2003 13:29:24 -0500	[thread overview]
Message-ID: <3FD0CE84.8060902@pobox.com> (raw)
In-Reply-To: <3FD0CB76.4000202@backtobasicsmgmt.com>

Kevin P. Fleming wrote:
> Jeff Garzik wrote:
> 
>> Yes, a tested patch would be great, thanks!
>>
> 
> (hijacking this subthread, sorry)
> 
> Jeff, you mentioned in the status report "don't remove an operating disk 
> from an ICH5, hotplug is not supported".
> 
> Does this mean hardware damage, or just serious libata/ICH5 confusion? 
> I've got a six-disk server here with two disks on an ICH5 and four on an 
> SATA150 TX4, and I really would like to be able to hot-replace a disk in 
> case of a failure. If the ICH5 cannort support this, I'm going to have 
> to get a 3ware card.


_Probably_ no hardware damage, but I do not know for sure.  I do not it 
will likely lockup, and data corruption is also a possibility.

As I mentioned in another email, ICH5 hardware does not support hot 
removal.  HOWEVER.  If the OS driver is given sufficient notice, it can 
shut down the port, and the sysadmin may then unplug the SATA cable.

As a tangent, your TX4 hardware fully supports hotplug, but libata does 
not yet support it.

	Jeff




  reply	other threads:[~2003-12-05 18:29 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 20:44 Serial ATA (SATA) for Linux status report Jeff Garzik
2003-12-03 23:27 ` Andre Tomt
2003-12-03 23:36   ` Jeff Garzik
2003-12-04  0:21     ` Miquel van Smoorenburg
2003-12-04  0:59     ` Samuel Flory
2003-12-04  1:02     ` Andre Tomt
2003-12-04 13:38     ` Justin Cormack
2003-12-04 14:54       ` Jeff Garzik
2003-12-04  8:17 ` Arnaud Launay
2003-12-04 15:01   ` Jeff Garzik
2003-12-05 17:42     ` Mickael Marchand
2003-12-05 17:47       ` Jeff Garzik
2003-12-05 18:07         ` [PATCH] Silicon image 3114 SATA link (really basic support) Mickael Marchand
2003-12-09 18:22           ` Aron Rubin
2003-12-09 18:54             ` Mickael Marchand
2003-12-09 20:14               ` Bartlomiej Zolnierkiewicz
2003-12-12  0:07                 ` Mickael Marchand
2003-12-05 18:16         ` Serial ATA (SATA) for Linux status report Kevin P. Fleming
2003-12-05 18:29           ` Jeff Garzik [this message]
2003-12-09  9:39 ` Petr Sebor
2003-12-09 19:59 ` J. Ryan Earl
2004-01-14 22:18 ` Greg Stark
2004-01-14 22:56   ` Erik Andersen
2004-01-14 23:31     ` James Courtier-Dutton
2004-01-15  0:41       ` Jeff Garzik
2004-01-15  2:38         ` Erik Andersen
2004-01-18 12:34         ` Martin Schlemmer
2004-01-14 23:32     ` Raphael Rigo
2004-01-15  0:08       ` Erik Steffl
2004-01-15  2:39         ` Matthias Hentges
2004-01-15 21:08           ` Greg Stark
2004-01-14 23:12   ` Erik Steffl
2004-01-18 13:32 ` Witold Krecicki
2004-01-18 18:00   ` Jeff Garzik
2004-01-18 20:33     ` Craig Bradney
  -- strict thread matches above, loose matches on Subject: below --
2003-12-04 18:03 Jon Burgess
2004-08-24 19:49 Jeff Garzik

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=3FD0CE84.8060902@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=kpfleming@backtobasicsmgmt.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