From: Olaf Zaplinski <o.zaplinski@mediascape.de>
To: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Warning, 2.5.3 eats filesystems
Date: Wed, 06 Feb 2002 18:49:36 +0100 [thread overview]
Message-ID: <3C616CB0.7080705@mediascape.de> (raw)
In-Reply-To: <20020205192826.GA112@elf.ucw.cz>
Pavel Machek wrote:
> Hi!
>
> 2.5.3 managed to damage my ext2 filesystem (few lost directories);
> beware.
> Pavel
/me too. 2.5.3 ate my bookmarks.html (and perhaps other files too, I did not
check yet). I just ran it up to the 1st freeze, then switched back to
2.4.17. Reiserfs then did a rather long log replay...
Olaf
prev parent reply other threads:[~2002-02-06 17:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 19:28 Warning, 2.5.3 eats filesystems Pavel Machek
2002-02-05 23:14 ` Daniel Pittman
2002-02-06 0:59 ` Skip Ford
2002-02-06 1:39 ` Dave Jones
2002-02-06 4:59 ` Daniel Pittman
2002-02-06 15:42 ` Pavel Machek
2002-02-06 23:30 ` Heinz Diehl
2002-02-06 23:39 ` Alexander Viro
2002-02-07 20:34 ` Heinz Diehl
2002-02-08 10:50 ` Pavel Machek
2002-02-08 21:48 ` Heinz Diehl
2002-02-08 11:14 ` Pavel Machek
2002-02-08 21:50 ` Andre Hedrick
2002-02-08 11:36 ` WARNING: 2.5.3 -- IDE damages data! [was Re: Warning, 2.5.3 eats filesystems] Pavel Machek
2002-02-06 17:49 ` Olaf Zaplinski [this message]
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=3C616CB0.7080705@mediascape.de \
--to=o.zaplinski@mediascape.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