From: Mike Fedyk <mfedyk@matchmail.com>
To: Ed Sweetman <ed.sweetman@wmich.edu>
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: Mon, 25 Feb 2002 07:54:52 -0800 [thread overview]
Message-ID: <20020225155452.GT20060@matchmail.com> (raw)
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> <1014526676.587.29.camel@psuedomode>
In-Reply-To: <1014526676.587.29.camel@psuedomode>
On Sat, Feb 23, 2002 at 11:57:51PM -0500, Ed Sweetman wrote:
> 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?
> 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
Does it turn off automatically on shutdown (halt)?
Debian has recently turned off write-back caching on shutdown just after
unmounting all local filesystems. That, or turning off write-back caching
will probably fix your problem.
Mike
next prev parent reply other threads:[~2002-02-25 15:54 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
2002-02-25 15:54 ` Mike Fedyk [this message]
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=20020225155452.GT20060@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=ed.sweetman@wmich.edu \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.