From: Ryan <rgb005@latech.edu>
To: "J. Ryan Earl" <heretic@clanhk.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: hot plugable?
Date: Mon, 19 Apr 2004 02:35:40 -0500 [thread overview]
Message-ID: <1082360140.4083814c6250c@webmail.LaTech.edu> (raw)
In-Reply-To: <4083223D.4050907@clanhk.org>
> All SATA HWIF chips support hot-swap (AFAIK), however, none are
> supported under Linux because libata does not support it. I think this
> is what I said originally. For some reason, libata supports everything
> to do with power management, and nothing to do with hot-plugging. =(
True, that. Hotswap is part of the SATA standard, after all. I just hope it
won't stay that way forever...
> It seems that particular hardware has premature support under Linux. I
> would be worried about disk compatibility with other
> controllers/interfaces too, though I'm sure there are methods to
> transfer your volumes over to a new controller, it would prolong and
> complicate in place upgrades for people doing things on the cheap.
I'm not worried about this as it's not a production-level server and downtime is
of no consequence. I'm willing to move my data to another location in order to
recreate the array if/when the necesary support becomes available. Of course,
not having 240gb on any one machine other than the server really does
cmoplicate things...but I know people >8)
> It may take some time for the SX4 to have mature support under Linux.
> 3Ware is the only open-driver hardware that has a driver capable of
> hotplug that I know of, but it gives dubious performance. I pray for
> the day libata does hot-swap so that I don't have to standardize on any
> slow hardware platforms for hot-swap. I'm excited about getting the
> twin Raptors off the PCI bus/siimage and directly onto the
> southbridge/sata_via.
I hope to see some progress toward that end. Supposedly Promise is offering
support to kernel developers, but since I'm not involved with any kernel
development, much less libata, I don't know for sure. We can only take the
developers' word for it and hope >8)
>
> -ryan
>
-ryan
--
huh?
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
prev parent reply other threads:[~2004-04-19 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 18:37 hot plugable? Andreas Jellinghaus
2004-04-17 1:51 ` J. Ryan Earl
[not found] ` <1082317319.4082da07a2449@webmail.LaTech.edu>
[not found] ` <4082E38F.3000009@clanhk.org>
[not found] ` <1082330599.40830de70a6b5@webmail.LaTech.edu>
[not found] ` <4083223D.4050907@clanhk.org>
2004-04-19 7:35 ` Ryan [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=1082360140.4083814c6250c@webmail.LaTech.edu \
--to=rgb005@latech.edu \
--cc=heretic@clanhk.org \
--cc=linux-ide@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 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.