From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.6 "IDE cache-flush at shutdown fixes"
Date: Wed, 12 May 2004 00:09:32 -0600 [thread overview]
Message-ID: <008201c437e7$b1a35160$6601a8c0@northbrook> (raw)
In-Reply-To: <fa.cmd38j8.1tgg9ro@ifi.uio.no>
If this is indeed the case, that those drives don't support the "flush write
cache" command, I'd like to see Maxtor's excuse as to why.. I believe that
Windows always powers down IDE drives before shutdown, maybe this is because
of non-universal support for the "flush write cache" command?
----- Original Message -----
From: "Rene Herman" <rene.herman@keyaccess.nl>
Newsgroups: fa.linux.kernel
To: <gene.heskett@verizon.net>
Cc: <linux-kernel@vger.kernel.org>
Sent: Monday, May 10, 2004 6:08 AM
Subject: Re: Linux 2.6.6 "IDE cache-flush at shutdown fixes"
> Gene Heskett wrote:
>
> >> hda: Maxtor 6Y120P0, ATA DISK drive
>
> > I note the drive is the same model here too, Rene.
> >
> > The question remains however, is our data in danger?
>
> There's a fair change that we'll be told, yes, very much so, since these
> drives don't seem to correctly support this life saving feature. The
> real answer though will be more easily deducted by calculating the ratio
> of unexplained file system corruptions you've had and reboots you've
> managed (0, that is).
>
> Rene.
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2004-05-12 6:09 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.jr282gn.1ni2t37@ifi.uio.no>
[not found] ` <fa.cmd38j8.1tgg9ro@ifi.uio.no>
2004-05-12 6:09 ` Robert Hancock [this message]
2004-05-12 18:52 ` Eric D. Mudama
2004-05-12 19:55 ` Rene Herman
2004-05-12 21:05 ` Bartlomiej Zolnierkiewicz
2004-05-12 22:27 ` Rene Herman
2004-05-12 21:28 ` Gene Heskett
2004-05-13 17:41 ` Eric D. Mudama
2004-05-10 9:20 Rene Herman
2004-05-10 11:32 ` Gene Heskett
2004-05-10 12:04 ` Rene Herman
2004-05-10 20:28 ` Arjan van de Ven
2004-05-10 19:25 ` Bartlomiej Zolnierkiewicz
2004-05-10 21:13 ` Rene Herman
2004-05-10 21:52 ` Bartlomiej Zolnierkiewicz
2004-05-11 4:56 ` Andrew Morton
2004-05-11 5:17 ` Andrew Morton
2004-05-11 11:24 ` Rene Herman
[not found] ` <200405111537.23535.bzolnier@elka.pw.edu.pl>
[not found] ` <40A1073E.3030605@keyaccess.nl>
2004-05-11 19:06 ` Rene Herman
[not found] ` <200405120236.00085.bzolnier@elka.pw.edu.pl>
2004-05-12 14:44 ` Rene Herman
2004-05-11 21:22 ` Mike Houston
2004-05-11 22:05 ` Bill Davidsen
2004-05-14 3:26 ` Pavel Machek
2004-05-15 0:53 ` Andrew Morton
2004-05-15 0:59 ` Andrew Morton
2004-05-15 1:05 ` Bartlomiej Zolnierkiewicz
2004-05-15 5:53 ` Herbert Xu
2004-05-15 6:16 ` Andrew Morton
2004-05-17 22:13 ` Greg KH
2004-05-17 22:55 ` Andrew Morton
2004-05-14 3:25 ` Pavel Machek
2004-05-11 11:24 ` Rene Herman
2004-05-11 12:56 ` Craig Bradney
2004-05-11 15:51 ` Athanasius
2004-05-11 16:10 ` dobrev
2004-05-12 18:07 ` Bartlomiej Zolnierkiewicz
2004-05-12 18:45 ` dobrev
2004-05-13 0:24 ` Patrick Wildi
2004-05-13 9:55 ` dobrev
2004-05-10 21:59 ` Rene Herman
2004-05-10 23:36 ` Mike Houston
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='008201c437e7$b1a35160$6601a8c0@northbrook' \
--to=hancockr@shaw.ca \
--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
all inboxes | Powered by JetHome®