From: Christian Fischer <Christian.Fischer@easterngraphics.com>
To: linux-ext4@vger.kernel.org
Cc: Eric Sandeen <sandeen@sandeen.net>
Subject: ext4 state user question
Date: Sat, 22 Aug 2009 19:21:15 +0200 [thread overview]
Message-ID: <200908221921.15949.Christian.Fischer@easterngraphics.com> (raw)
Hello,
I have not found a ext4-user list or something similar, that's why my user
question goes to this development list.
I had a lot of file system crashes with xfs the last time, Eric knows that, if
he remembers.
I look for an alternate file system for our new production servers, and I need
to use 2.6.29.4 for the moment due to all systems running on xen, and as far
as I know 2.6.29.4 xen patched ist the best solution at the moment.
I've updated all xen kernels from 2.6.18 (which is the latest official xen
kernel) to 2.6.29.4 because xfs tried to write to the superblock to run into
the next bug, a radix_tree problem with xfs over nfs. I've backported 2.6.30
patches to avoid the problem, that runs at the moment.
But I don't feel like waiting for the next crash.
I was never before as unshure as now which file system is to choose, IMO I
have the choice between zfs on solaris, xfs or ext4.
Zfs is not really ported to linux, the stable time of xfs seems gone, and ext4
is relatively young.
What do you think, is ext4 with 2.6.29.4 ready for productive work and to
prefer over xfs at the moment?
Best Regards
Christian
--
next reply other threads:[~2009-08-22 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-22 17:21 Christian Fischer [this message]
2009-08-22 18:32 ` ext4 state user question Eric Sandeen
2009-08-22 19:59 ` Christian Fischer
2009-08-23 18:07 ` Eric Sandeen
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=200908221921.15949.Christian.Fischer@easterngraphics.com \
--to=christian.fischer@easterngraphics.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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.