From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Russell Coker <russell@coker.com.au>
Cc: ReiserFS <reiserfs-list@namesys.com>
Subject: Re: ReiserFS is not suitable for a root FS.
Date: Sat, 17 May 2003 13:14:15 +0200 [thread overview]
Message-ID: <3EC61987.5000402@gmx.net> (raw)
In-Reply-To: <200305172030.58775.russell@coker.com.au>
Russell Coker wrote:
> With a ReiserFS file system you can't FSCK a file system that is mounted
> read-only. This means that when a root file system needs to be FSCK'd you
> need to boot from installation media (or convert the swap space into a
> temporary root file system).
I take this as a feature request. Right? It would certainly be nice to have.
> It seems that the kernel drivers in 2.4.20 have some bugs whereby a corrupted
> file system can cause an immediate reboot, a system lock (caps-lock doesn't
> change the keyboard led), or a kernel Oops. Ext2/3 does not appear to have
> such problems.
Could you please provide a metadata dump of the affected filesystem? The
behaviour you describe is not supposed to happen. Do you have a decoded
Oops for us to see what happened?
Believe me, ext2 had other problems like silent corruption even without
crashes or unclean shutdowns triggering it. After about 20-30 reboots,
my ext2 root filesystem was corrupted. This bug plagued me from
2.4.0-test until recently. It now seems to be fixed.
> When machines crash it seems that there is a risk of a file system corruption,
> a crash on boot seems reasonably likely to damage the root file system. My
> laptop (my main test machine) has had two serious corruptions of the root
> file system this year which caused kernel crashing on boot.
>
> My conclusion is that until these issues are addressed ReiserFS is not
> suitable for a root file system. Then when such problems occur it will be
> easy to fsck the file system. Also ext2 has smaller kernel modules giving a
^^^^
You surely mean ext3? Ext2 would not be a fair comparison because it has
no journaling. And if you're hunting for size, try jffs or jffs2.
> smaller initrd.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
next prev parent reply other threads:[~2003-05-17 11:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 10:30 ReiserFS is not suitable for a root FS Russell Coker
2003-05-17 10:56 ` Oleg Drokin
2003-05-17 11:09 ` Russell Coker
2003-05-17 11:24 ` Oleg Drokin
2003-05-17 11:32 ` Russell Coker
2003-05-17 11:40 ` Oleg Drokin
2003-05-17 11:14 ` Carl-Daniel Hailfinger [this message]
2003-05-17 11:25 ` Russell Coker
2003-05-17 12:01 ` Carl-Daniel Hailfinger
2003-05-17 12:10 ` Oleg Drokin
2003-05-19 10:22 ` Carl-Daniel Hailfinger
2003-05-19 10:31 ` Oleg Drokin
2003-05-21 22:09 ` Newsmail
2003-09-18 11:50 ` Carl-Daniel Hailfinger
2003-09-18 14:05 ` Vitaly Fertman
2003-05-17 12:40 ` Russell Coker
2003-05-19 19:55 ` bscott
2003-05-19 20:42 ` Dieter Nützel
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=3EC61987.5000402@gmx.net \
--to=c-d.hailfinger.kernel.2003@gmx.net \
--cc=reiserfs-list@namesys.com \
--cc=russell@coker.com.au \
/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.