From: Michael Tokarev <mjt@tls.msk.ru>
To: Molle Bestefich <molle.bestefich@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: sata_nv and RAID1
Date: Wed, 15 Jun 2005 01:37:27 +0400 [thread overview]
Message-ID: <42AF4E17.2040900@tls.msk.ru> (raw)
In-Reply-To: <62b0912f05061414116f7afedc@mail.gmail.com>
Molle Bestefich wrote:
> Michael Tokarev wrote:
>
>>Without proper error handling [...]
>>linux SATA subsystem isn't ready for production,
>>and people should not rely on it *now*.
Note there was an "if" in that [...] -- "IF I/O errors are
*really* not handled properly, linux SATA subsystem isn't
ready etc"
> As long as disks aren't removed, it's OK for production..
>
> But I'll agree with anyone who says that IDE under Linux just sucks
> donkey ass compared to IDE under Windows. With Windows 2K and later,
> unplugging both SATA and PATA devices Just Works (tm). I'm having a
> hard time figuring how this works: there's enough people supporting
> Linux to build a complete web-enabled SCM system (git) in a couple of
> weeks, but noone has bothered to fix this glaring flaw for the past 5
> years? What gives?
Well.. I don't want to start a flamewar, but I tend to disagree.
I for one don't care (for now) about SATA and hot[un]plug for
harddrives. But ol'good IDE works under linux just fine, together
with proper (fsvo "proper", which isn't still proper for alot of
IDE drives, but that's hardware and linux can't do anything there)
error handling and stuff. And with out-of-the-box toolset
(smartmontools, hdparm), the support is better than win* --
I have more options to monitor my drives, to reallocate bad
blocks, to watch for drives dying, to control several h/w
aspects of devices than on win*. Well, ok, (and oh, it's
another hot flamewar topic), I'm trying to avoid usage of
IDE drives due to various limitations and defeciencies, and
tend to use SCSI devices if at all possible... And ok, ok,
IDE != SATA... ;)
/mjt
next prev parent reply other threads:[~2005-06-14 21:37 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 [this message]
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
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=42AF4E17.2040900@tls.msk.ru \
--to=mjt@tls.msk.ru \
--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;
as well as URLs for NNTP newsgroup(s).