From: Mike Fedyk <mfedyk@matchmail.com>
To: Diego Calleja Garc?a <diegocg@teleline.es>
Cc: reiser@namesys.com, linux-kernel@vger.kernel.org,
reiserfs-list@namesys.com
Subject: Re: Filesystem Tests
Date: Wed, 6 Aug 2003 12:08:50 -0700 [thread overview]
Message-ID: <20030806190850.GF21290@matchmail.com> (raw)
In-Reply-To: <20030806204514.00c783d8.diegocg@teleline.es>
On Wed, Aug 06, 2003 at 08:45:14PM +0200, Diego Calleja Garc?a wrote:
> El Wed, 6 Aug 2003 11:04:27 -0700 Mike Fedyk <mfedyk@matchmail.com> escribi?:
>
> >
> > Journaled filesystems have a much smaller chance of having problems after a
> > crash.
>
> I've had (several) filesystem corruption in a desktop system with (several)
> journaled filesystems on several disks. (They seem pretty stable these days,
> though)
>
> However I've not had any fs corrution in ext2; ext2 it's (from my experience)
> rock stable.
>
> Personally I'd consider twice the really "serious" option for a serious server.
I've had corruption caused by hardware, and nothing else. I haven't run
into any serious bugs.
But with servers, the larger your filesystem, the longer it will take to
fsck. And that is bad for uptime. Period.
I would be running ext2 also if I wasn't running so many test kernels (and
they do oops on you), and I've been glad that I didn't have to fsck every
time I oopsed (though I do every once in a while, just to make sure).
next prev parent reply other threads:[~2003-08-06 19:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 2:30 Filesystem Tests Grant Miner
2003-08-06 3:47 ` Peter Chubb
2003-08-06 10:43 ` Oleg Drokin
2003-08-06 5:41 ` Andrew Morton
2003-08-06 10:35 ` Szakacsits Szabolcs
2003-08-09 1:09 ` Jamie Lokier
2003-08-09 5:12 ` Szakacsits Szabolcs
2003-08-09 9:33 ` Jamie Lokier
2003-08-09 9:18 ` Szakacsits Szabolcs
2003-08-09 16:19 ` Jamie Lokier
2003-08-10 21:03 ` Grant Miner
2003-08-12 8:27 ` Dieter Nützel
2003-08-06 14:06 ` Hans Reiser
2003-08-06 16:34 ` Diego Calleja García
2003-08-06 18:04 ` Mike Fedyk
2003-08-06 18:45 ` Diego Calleja García
2003-08-06 19:08 ` Mike Fedyk [this message]
2003-08-06 19:40 ` Diego Calleja García
2003-08-07 13:51 ` Hans Reiser
2003-08-07 0:55 ` Clemens Schwaighofer
2003-08-06 21:19 ` Andrew Morton
2003-08-06 21:25 ` ieee1394 (Firewire) driver problem Henrik Raeder Clausen
2003-08-07 12:55 ` Filesystem Tests Hans Reiser
2003-08-07 19:09 ` Diego Calleja García
2003-08-07 19:21 ` ahorn
2003-08-06 23:37 ` Timothy Miller
2003-08-06 23:47 ` Mike Fedyk
2003-08-07 0:40 ` Timothy Miller
2003-08-07 13:55 ` jlnance
2003-08-06 9:55 ` Felipe Alfaro Solana
2003-08-06 10:48 ` Paul Dickson
2003-08-06 11:39 ` Grant Miner
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=20030806190850.GF21290@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=diegocg@teleline.es \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
/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