From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: khromy <khromy@khromy.ath.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: EXT2-fs error
Date: Fri, 30 Mar 2001 08:57:48 +0200 (MEST) [thread overview]
Message-ID: <200103300657.IAA07806@cave.bitwizard.nl> (raw)
In-Reply-To: <20010329220630.A32834@khromy.lnuxlab.net> from khromy at "Mar 29, 2001 10:06:30 pm"
khromy wrote:
> Linux vingeren.girl 2.4.3-pre7 #5 Mon Mar 26 23:33:59 EST 2001 i686 unknown
>
> EXT2-fs error (device ide2(33,3)): ext2_free_blocks: bit already cleared for block 1048576
> EXT2-fs error (device ide2(33,3)): ext2_free_blocks: bit already cleared for block 1048576
>
> ^
> I got the following while rm -rf'ing my mozilla cvs checkout. Deadly or not deadly?
Highly deadly.
Your disk is dropping bits, or, more likely, your RAM. This is very,
very bad.
Can you compile 100 kernes without error?
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
next prev parent reply other threads:[~2001-03-30 6:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-30 3:06 EXT2-fs error khromy
2001-03-30 6:57 ` Rogier Wolff [this message]
2001-04-02 23:13 ` Alan Cox
2001-03-30 13:49 ` Dale E Martin
-- strict thread matches above, loose matches on Subject: below --
2001-02-23 19:12 Ian Wehrman
2001-02-23 11:46 ` John Heil
2001-02-23 19:26 ` Alan Cox
2001-02-23 11:50 ` John Heil
2001-02-24 11:02 ` A E Lawrence
2001-02-24 16:59 ` Alan Cox
2001-02-24 22:30 ` A E Lawrence
2001-02-24 23:08 ` A E Lawrence
2001-02-25 20:52 ` A E Lawrence
2001-02-25 13:53 ` John Heil
2001-02-25 17:58 ` Mike Brown
2001-02-22 7:02 Mohammad A. Haque
2001-02-22 8:10 ` Andreas Dilger
2001-02-22 14:58 ` Mohammad A. Haque
2000-12-06 21:50 Ext2-fs error mkloppstech
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=200103300657.IAA07806@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=khromy@khromy.ath.cx \
--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