From: Ben Greear <greearb@candelatech.com>
To: "Frédéric L. W. Meunier" <0@pervalidus.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.2 ext2 filesystem corruption ? (was 2.4.2: What happened ? (No such file or directory))
Date: Mon, 05 Mar 2001 23:49:51 -0700 [thread overview]
Message-ID: <3AA4888F.77E3B422@candelatech.com> (raw)
In-Reply-To: <20010305022117.C103@pervalidus>
For what it's worth, I was able to completely screw up my root FS
using redhat's Fisher beta kernel (2.2.18 + stuff). I did this by
running a bad hdparm command while running a full GNOME desktop:
(This was not a good idea...and I know, and knew that...but....)
hdparm -X34 -d1 -u1 /dev/hda
(As found here: http://www.oreillynet.com/pub/a/linux/2000/06/29/hdparm.html?page=2
HD is a 40GB 7200 RPM Western Digital drive. (ATA-100 I believe)
that I just got from Fry's a few days ago...
fdisk was sort of able to recover most of the file system by
booting off of the CD in rescue mode and running fsck on /dev/hda, but
many files were not what they said they were, ie /sbin/ifup was
some other binary... Some files turned into directories it
seems....
Sorry for the lame bug report, but I'm scared to try it again, and
I didn't realize the complexity of the problem when I simply powered
down my machine with the HD light on solid...
Thanks,
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-06 6:21 UTC|newest]
Thread overview: 18+ 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 [this message]
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 ` 2.4.2 ext2 filesystem corruption ? (was 2.4.2: What happened ?(No Ben Greear
2001-03-08 6:21 ` 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
2001-03-05 6:37 Frédéric L. W. Meunier
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=3AA4888F.77E3B422@candelatech.com \
--to=greearb@candelatech.com \
--cc=0@pervalidus.net \
--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;
as well as URLs for NNTP newsgroup(s).