From: Ettore Perazzoli <ettore@ximian.com>
To: timw@splhi.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Interesting fs corruption story
Date: 12 Mar 2001 07:44:40 -0500 [thread overview]
Message-ID: <984401080.15372.4.camel@milkplus.unknown.domain> (raw)
In-Reply-To: <20010307122222.A1254@kochanski.internal.splhi.com>
In-Reply-To: <Pine.LNX.4.21.0103042043320.27829-100000@trna.ximian.com> <20010306170102.B1095@kochanski.internal.splhi.com> <983927410.11517.0.camel@milkplus.unknown.domain> <20010307122222.A1254@kochanski.internal.splhi.com>
On 07 Mar 2001 12:22:22 -0800, Tim Wright wrote:
> On Tue, Mar 06, 2001 at 08:10:10PM -0500, Ettore Perazzoli wrote:
> > On 06 Mar 2001 17:01:02 -0800, Tim Wright wrote:
> Yes, it does. I have the drive running in UDMA mode 2, and get ~16MB/s from
> 'hdparm -t -T'. I have the "use DMA automatically" option turned on in the
> kernel, so I inherit the BIOS settings which are correct.
>
> I've used standby and hibernation with complete success since.
This seemed to fix the problem for me as well. I have had DMA turned
on since then, and I have experienced no file system corruption anymore.
Thanks!
Maybe the help message for this kernel option (CONFIG_APM_ALLOW_INTS)
should report in big blocky letters that disabling it might cause major
data loss with some drive/bios combinations?.. I was not aware that I
was touching such a sensitive parameter when I rebuilt the kernel, and
the help message didn't warn me in any way.
--
Ettore
prev parent reply other threads:[~2001-03-12 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 2:46 Interesting fs corruption story Ettore Perazzoli
2001-03-05 4:33 ` Jonathan Morton
2001-03-05 5:08 ` Ettore Perazzoli
2001-03-07 1:01 ` Tim Wright
2001-03-07 1:10 ` Ettore Perazzoli
2001-03-07 20:22 ` Tim Wright
2001-03-12 12:44 ` Ettore Perazzoli [this message]
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=984401080.15372.4.camel@milkplus.unknown.domain \
--to=ettore@ximian.com \
--cc=linux-kernel@vger.kernel.org \
--cc=timw@splhi.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