From: Ben Greear <greearb@candelatech.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.2 ext2 filesystem corruption ? (was 2.4.2: What happened ?(No
Date: Wed, 07 Mar 2001 23:32:11 -0700 [thread overview]
Message-ID: <3AA7276B.DB9AEC11@candelatech.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0103080027150.5588-100000@weyl.math.psu.edu>
Alexander Viro wrote:
>
> On Wed, 7 Mar 2001, Ben Greear wrote:
>
> > However, messing with the hdparms options can do random things, at
> > least from my perspective as a user: It may bring exciting new performance
> > to your system, and it may subtly, or not so, corrupt your file system.
>
> It's root-only. If you run unfamiliar stuff as root without thorough
> RTFM or choose to ignore "use with extreme caution" contained in the
> manpage - hdparm is the least of your problems. Think of it as evolution
> in action...
> Cheers,
> Al
I see it differently: If it's possible for the driver to protect the
user, and it does not, then it strikes me as irresponsible programming. If
there is a reason other than 'only elite users are cool enough to tune
their system, and they never make mistakes', then that's ok, but I have
not heard that argument yet.
Of course, I'd love it if the HD driver automatically brought it over
4MBps (it's 7200 RPM, for goodness sake!!). (It sounds like, from
reading the hdparm man page, that my HD should do at least 20MBps..)
Either way, I've said my piece, and will go back to wrestling with
why my network/overall performance is sucking so badly all of a sudden...
Enjoy,
Ben
--
Ben Greear (greearb@candelatech.com) http://www.candelatech.com
Author of ScryMUD: scry.wanfear.com 4444 (Released under GPL)
http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2001-03-08 6:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 5:21 2.4.2 ext2 filesystem corruption ? (was 2.4.2: What happened ? (No such file or directory)) Frédéric L. W. Meunier
2001-03-06 6:49 ` Ben Greear
2001-03-06 12:07 ` 2.4.2 ext2 filesystem corruption ? (was 2.4.2: What happened ? (No Alan Cox
2001-03-07 3:54 ` Ben Greear
2001-03-07 12:57 ` Alan Cox
2001-03-08 5:40 ` Ben Greear
2001-03-08 5:34 ` Alexander Viro
2001-03-08 6:32 ` Ben Greear [this message]
2001-03-08 6:21 ` 2.4.2 ext2 filesystem corruption ? (was 2.4.2: What happened ?(No Alexander Viro
2001-03-08 20:30 ` God
2001-03-08 21:31 ` Alexander Viro
2001-03-08 20:10 ` God
2001-03-08 20:37 ` Andre Hedrick
2001-03-08 21:04 ` Roman Zippel
2001-03-08 20:34 ` 2.4.2 ext2 filesystem corruption ? (was 2.4.2: What happened ? (No Oliver Xymoron
2001-03-07 13:49 ` Anton Altaparmakov
2001-03-06 10:14 ` 2.4.2 ext2 filesystem corruption ? (was 2.4.2: What happened ? (No such file or directory)) SteveC
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=3AA7276B.DB9AEC11@candelatech.com \
--to=greearb@candelatech.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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