From: "Balazs Javor" <jb3@freemail.hu>
To: "Kernel" <linux-kernel@vger.kernel.org>
Subject: Filesystem corruptions etc. - Which is the last safe kernel?
Date: Sun, 2 Dec 2001 15:26:31 +0100 [thread overview]
Message-ID: <020801c17b3d$574fbeb0$0501a8c0@llama> (raw)
Hi,
I've recently subscribed to this list when someone pointed out on one of the
Debian lists, that the 2.5.15 fs corruption issue
was discussed here much earlier.
Since then I was reading this list with much interest and growing
uncertainty...
It seems to me that every kernel since 2.4.15 had serious problems where
your files can get corrupted / lost.
(Maybe even kernels before that. I just don't know.)
I run a linux machine currently with kernel 2.4.14 at home as a fileserver
where I keep all my personal files etc. on to
80GB harddrives.
I am a little bit nervouse, though...
I thought the even numbered kernel releases like 2.4.x are safe to be used,
without the risk of major data loss etc.!!!
It seems to me less and less so.
I was also eagerly waiting for the ext3 fs to be included in the kernel for
the same concern, especially that while trying to set up XFree
I often encounter complete lockups where only a hard reset helps :(
Unfortunatly I'm a bit afraid to install any kernel that inlcudes it since
they seem to cause more problems then they solve.
Now the question is, is any of the 2.4.x kernels safe to use?
And why is it that supposedly released and stable kernels can have such
serious issues?
Many thanks in advance!
best regards,
Balazs
next reply other threads:[~2001-12-02 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 14:26 Balazs Javor [this message]
2001-12-02 16:19 ` Filesystem corruptions etc. - Which is the last safe kernel? Alan Cox
2001-12-02 16:53 ` Francois Romieu
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='020801c17b3d$574fbeb0$0501a8c0@llama' \
--to=jb3@freemail.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.