The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Fran?ois Cami <stilgar2k@wanadoo.fr>,
	"J.A. Magallon" <jamagallon@able.es>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHSET] Linux 2.4.18-rc4-jam1
Date: 23 Feb 2002 23:57:51 -0500	[thread overview]
Message-ID: <1014526676.587.29.camel@psuedomode> (raw)
In-Reply-To: <20020224030620.GR20060@matchmail.com>
In-Reply-To: <20020223234217.C2023@werewolf.able.es> <3C782531.6050701@wanadoo.fr> <1014514801.492.14.camel@psuedomode> <1014516072.491.28.camel@psuedomode>  <20020224030620.GR20060@matchmail.com>

On Sat, 2002-02-23 at 22:06, Mike Fedyk wrote:
> On Sat, Feb 23, 2002 at 09:01:06PM -0500, Ed Sweetman wrote:
> > Or it could be my ext3 fs corrupting files again.
> > 
> 
> Oy, do you have one of those write-back (behind) ide hard drives?
> -
> 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/

Probably, it's a WD 100GB.  hdparm says   WriteCache=enabled
I dont know if the bios is set to writeback off hand, I'd have to
reboot, which I'll probably do soon to add in another hdd and possibly
run memtest86 instead of just memtest


  reply	other threads:[~2002-02-24  4:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-23 22:42 [PATCHSET] Linux 2.4.18-rc4-jam1 J.A. Magallon
2002-02-23 23:26 ` François Cami
2002-02-24  1:39   ` Ed Sweetman
2002-02-24  1:50     ` Ed Sweetman
2002-02-24  2:01     ` Ed Sweetman
2002-02-24  3:06       ` Mike Fedyk
2002-02-24  4:57         ` Ed Sweetman [this message]
2002-02-25 15:54           ` Mike Fedyk
2002-02-24  5:22     ` D. M. Monarres

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=1014526676.587.29.camel@psuedomode \
    --to=ed.sweetman@wmich.edu \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.com \
    --cc=stilgar2k@wanadoo.fr \
    /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