From: Clemens Schwaighofer <cs@tequila.co.jp>
To: "Diego Calleja García" <diegocg@teleline.es>
Cc: Mike Fedyk <mfedyk@matchmail.com>,
reiser@namesys.com, linux-kernel@vger.kernel.org,
reiserfs-list@namesys.com
Subject: Re: Filesystem Tests
Date: Thu, 07 Aug 2003 09:55:21 +0900 [thread overview]
Message-ID: <3F31A379.2060807@tequila.co.jp> (raw)
In-Reply-To: <20030806204514.00c783d8.diegocg@teleline.es>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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)
well, I only had one time huge problems with a journaling FS, this was
when I thought I could use Reise FS Beta on a Production File Server ;)
> However I've not had any fs corrution in ext2; ext2 it's (from my
experience)
> rock stable.
well, ever had a check of several hundrets of Gigabytes in ext2 after a
poweroutage ... when you had this several times in a row, you even take
ext3 and thank for its existence ...
> Personally I'd consider twice the really "serious" option for a
serious server.
I'd never use ext2 on a server anymore nowadays. You have so many
choises of stable journaling filesystems, you don't have to use ext2
anymore (except perhaps for small partitions like /tmp or /boot ...)
- --
Clemens Schwaighofer - IT Engineer & System Administration
==========================================================
Tequila Japan, 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN
Tel: +81-(0)3-3545-7703 Fax: +81-(0)3-3545-7343
http://www.tequila.jp
==========================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/MaN5jBz/yQjBxz8RAqEDAJ9MZBTBokLsCxDQga3GVNHKY9q/3ACgpX2S
nIezpbMMsLb58jTnYnHI53w=
=fO1v
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-08-07 0:55 UTC|newest]
Thread overview: 35+ 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-06 10:35 ` Szakacsits Szabolcs
2003-08-09 1:09 ` Jamie Lokier
2003-08-09 5:12 ` Szakacsits Szabolcs
2003-08-09 5:12 ` Szakacsits Szabolcs
2003-08-09 9:33 ` Jamie Lokier
2003-08-09 9:18 ` Szakacsits Szabolcs
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
2003-08-06 19:40 ` Diego Calleja García
2003-08-07 13:51 ` Hans Reiser
2003-08-07 0:55 ` Clemens Schwaighofer [this message]
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=3F31A379.2060807@tequila.co.jp \
--to=cs@tequila.co.jp \
--cc=diegocg@teleline.es \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
--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 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.