mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Udo A. Steinberg" <sorisor@Hell.WH8.TU-Dresden.De>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Trashing ext2 with hdparm
Date: Wed, 06 Dec 2000 18:25:15 +0100	[thread overview]
Message-ID: <3A2E767B.D74B24B5@Hell.WH8.TU-Dresden.De> (raw)


Hi,

Following the discussion in another thread where someone
reported fs corruption when enabling DMA with hdparm, I've
played around with hdparm and found that even the rather
harmless hdparm operations are capable of trashing an ext2
filesystem quite nicely.

hdparm version is 3.9

hdparm -tT /dev/hdb1 does the trick here.

After that, several files are corrupted, such as /etc/mtab.
Reboot+fsck fixes the problem, however e2fsck never finds
any errors in the fs on disk.

I'm quite sure that earlier kernel versions didn't exhibit
this kind of behaviour, although I'm not quite sure at
which point things started to break. I have test12-pre6
here atm, but I have test-11 still lying around and will
test that in a bit.

The drive in question is an IBM-DTLA307030 running in
UDMA Mode 5 on a PDC20265, chipset revision 2.

I haven't seen any other corruption other than that which
hdparm reliably triggers. Might as well be a bug in hdparm,
so someone else might also want to check...

-Udo.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-12-06 17:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-06 17:25 Udo A. Steinberg [this message]
2000-12-06 17:40 ` Jan Niehusmann
2000-12-06 18:49 ` Byron Stanoszek
2000-12-06 19:41 ` Andre Hedrick
2000-12-06 19:49   ` Jan Niehusmann
2000-12-06 19:52   ` Udo A. Steinberg
2000-12-06 19:56     ` Andre Hedrick
2000-12-06 20:04       ` H. Peter Anvin
2000-12-06 20:23         ` Chris Meadors
2000-12-06 22:09           ` H. Peter Anvin

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=3A2E767B.D74B24B5@Hell.WH8.TU-Dresden.De \
    --to=sorisor@hell.wh8.tu-dresden.de \
    --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

all inboxes | Powered by JetHome®