From: Mike Hardy <mhardy@h3c.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Molle Bestefich <molle.bestefich@gmail.com>,
Michael Tokarev <mjt@tls.msk.ru>,
linux-raid@vger.kernel.org
Subject: Re: sata_nv and RAID1
Date: Tue, 14 Jun 2005 16:46:20 -0700 [thread overview]
Message-ID: <42AF6C4C.206@h3c.com> (raw)
In-Reply-To: <42AF631C.1050806@tmr.com>
Bill Davidsen wrote:
> Actually I suspect most Linux users are smart enough not to pull a PATA
> drive out while in use, and it works just fine if you offline the drive
> before removal. I may be wrong recently, it seems that the ability to
> disable the interface was taken out of either hdparm or a recent kernel.
> I read about, exchange comments with Alan Cox, and I don't recall the
> details.
>
> There may have been a step backward, hopefully just a brain fart and not
> a deliberate decision to disable hot swap.
This is barely pertinent to the original discussion, but I still use
hdparm -[U|R] to enable/disable an interface and attach/detach an
optical drive on my laptop (Dell D800 - not that new or fancy anymore).
It works fine, as far as I can tell, once you get udev to have the
devices in /dev/ for you
Partial uname:
2.6.11-1.27_FC3 #1 Tue May 17 20:27:37 EDT 2005 i686
Hopefully they haven't disabled it after that, I'll be disappointed.
I do agree in general that SMART support for SATA at least should be in
kernels by this point, and correct error propagation as well. Perhaps
all the kernel devs either don't get the new hardware, or they're on
SCSI though. I'm still building with PATA until SATA's got it all anyway.
-Mike
next prev parent reply other threads:[~2005-06-14 23:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 16:13 sata_nv and RAID1 Diego M. Vadell
2005-06-11 19:26 ` Jeff Garzik
2005-06-11 20:29 ` Michael Tokarev
2005-06-13 3:15 ` Diego M. Vadell
2005-06-13 6:45 ` Jeff Garzik
2005-06-13 11:57 ` Michael Tokarev
2005-06-13 12:27 ` Peter T. Breuer
2005-06-13 14:40 ` Diego M. Vadell
2005-06-13 16:07 ` Peter T. Breuer
2005-06-13 16:51 ` Diego M. Vadell
2005-06-13 17:59 ` Jeff Garzik
2005-06-13 21:00 ` Diego M. Vadell
2005-06-13 21:20 ` Jeff Garzik
2005-06-13 21:41 ` Diego M. Vadell
[not found] ` <1118818568.3089.5.camel@raz-laptop>
[not found] ` <200506151427.09114.dvadell@lantech.com.ar>
2005-06-16 6:43 ` raz ben jehuda
2005-06-14 21:11 ` Molle Bestefich
2005-06-13 19:00 ` Peter T. Breuer
2005-06-13 20:41 ` Raz Ben-Jehuda(caro)
2005-06-13 21:16 ` Diego M. Vadell
2005-06-14 21:11 ` Molle Bestefich
2005-06-14 21:37 ` Michael Tokarev
2005-06-14 22:10 ` Diego M. Vadell
2005-06-14 22:17 ` Michael Tokarev
2005-06-15 0:08 ` Jeff Garzik
2005-06-14 22:26 ` Molle Bestefich
2005-06-14 23:07 ` Bill Davidsen
2005-06-14 23:18 ` Molle Bestefich
2005-06-15 0:12 ` Jeff Garzik
2005-06-15 0:19 ` Molle Bestefich
2005-06-14 23:46 ` Mike Hardy [this message]
2005-06-15 0:11 ` Jeff Garzik
2005-06-15 0:34 ` Guy
2005-06-14 21:53 ` David Greaves
2005-06-14 22:30 ` Molle Bestefich
2005-06-15 19:17 ` Mark Hahn
2005-06-15 19:32 ` Molle Bestefich
2005-06-15 19:34 ` Molle Bestefich
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=42AF6C4C.206@h3c.com \
--to=mhardy@h3c.com \
--cc=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--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;
as well as URLs for NNTP newsgroup(s).