mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lukasz Kosewski <lkosewsk@gmail.com>
To: Andrew Walrond <andrew@walrond.org>
Cc: linux-kernel@vger.kernel.org,
	Molle Bestefich <molle.bestefich@gmail.com>,
	htejun@gmail.com, linux-raid@vger.kernel.org,
	Jeff Garzik <jgarzik@pobox.com>
Subject: Re: Anybody know about nforce4 SATA II hot swapping + linux raid?
Date: Sat, 8 Oct 2005 11:01:25 -0400	[thread overview]
Message-ID: <355e5e5e0510080801p88f04c7x7992c3d75f20e65c@mail.gmail.com> (raw)
In-Reply-To: <200510081555.41159.andrew@walrond.org>

On 10/8/05, Andrew Walrond <andrew@walrond.org> wrote:
> The lack of hot swapping does seem to be a serious weakness in linux, at least
> for resilient server applications. It would really complete the linux raid
> picture, and make it quite compelling.
>
> But I'm in no position to do it myself; I can only hope this thread inspires
> some capable person to plug the gap :)

Hey Andrew,

I've actually been working on implementing the core set of routines
that will allow for hot-swapping SATA drives in Linux.  The core is
not quite ready yet, but you can expect the next iteration within the
week.  Once the core is integrated, someone will have to implement
capturing hotswap events on the nForce4 SATA controller, and using the
core functions.  I don't know how long that will take, but if the
Linux SATA maintainer, Jeff Garzik (CCed on this email) knows how to
do it, then it might be just a few weeks' time.

That said, if you want to use this for servers you might still want to
wait a bit before committing your resources to this :)

Luke Kosewski

  reply	other threads:[~2005-10-08 15:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-07 10:11 Andrew Walrond
2005-10-08  7:41 ` Tejun Heo
2005-10-08 14:26   ` Molle Bestefich
2005-10-08 14:55     ` Andrew Walrond
2005-10-08 15:01       ` Lukasz Kosewski [this message]
2005-10-08 15:52         ` Andrew Walrond
2005-10-10 17:47         ` Ken Hwang
2005-10-08 15:23       ` Gordon Henderson
2005-10-08 16:03         ` Andrew Walrond
2005-10-08 16:08       ` John Stoffel
2005-10-08 16:39         ` Andrew Walrond
2005-10-15  4:24 ` Bill Davidsen
2005-10-15  5:06   ` Lajber Zoltan
2005-10-08 19:16 Allen Martin
     [not found] <4UXuH-EU-31@gated-at.bofh.it>
     [not found] ` <4VhD6-79H-7@gated-at.bofh.it>
     [not found]   ` <4VnSe-hv-15@gated-at.bofh.it>
2005-10-08 19:09     ` Robert Hancock
     [not found] ` <4XLQk-6Z2-1@gated-at.bofh.it>
     [not found]   ` <4XMt3-7Yt-5@gated-at.bofh.it>
2005-10-15  6:29     ` Robert Hancock
2005-10-18 22:35       ` Bill Davidsen

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=355e5e5e0510080801p88f04c7x7992c3d75f20e65c@mail.gmail.com \
    --to=lkosewsk@gmail.com \
    --cc=andrew@walrond.org \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=molle.bestefich@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®