From: "Jeremy Jackson" <jerj@coplanar.net>
To: "Dan Maas" <dmaas@dcine.com>, <linux-kernel@vger.kernel.org>
Subject: Re: unwanted disk access by the kernel?
Date: Fri, 15 Mar 2002 01:20:32 -0800 [thread overview]
Message-ID: <016401c1cc02$aa51c110$7e0aa8c0@bridge> (raw)
In-Reply-To: <20020315013644.A26891@morpheus>
You may also want to mount your (root) filesystem(s) with the
"noatime" option... check the linux laptops site for other tips.
----- Original Message -----
From: "Dan Maas" <dmaas@dcine.com>
To: <linux-kernel@vger.kernel.org>
Sent: Thursday, March 14, 2002 10:36 PM
Subject: unwanted disk access by the kernel?
> I've been trying to set up my laptop for mobile use. I'm having a
> problem with unwanted disk activity - even when the system is
> completely idle, there is still an occasional trickle of disk writes
-SNIP-
next prev parent reply other threads:[~2002-03-15 9:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 6:36 unwanted disk access by the kernel? Dan Maas
2002-03-15 7:00 ` Andrew Morton
2002-03-15 9:20 ` Jeremy Jackson [this message]
2002-03-15 18:46 ` Dan Maas
2002-03-15 19:02 ` Alan Cox
2002-03-16 1:30 ` Mike Fedyk
2002-03-16 15:11 ` Joachim Breuer
2002-03-15 14:35 ` Alan Cox
2002-03-19 15:06 ` Pavel Machek
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='016401c1cc02$aa51c110$7e0aa8c0@bridge' \
--to=jerj@coplanar.net \
--cc=dmaas@dcine.com \
--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