linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Fischer <Christian.Fischer@easterngraphics.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 state user question
Date: Sat, 22 Aug 2009 21:59:34 +0200	[thread overview]
Message-ID: <200908222159.34737.Christian.Fischer@easterngraphics.com> (raw)
In-Reply-To: <4A9039B7.9040908@sandeen.net>

On Saturday 22 August 2009, Eric Sandeen wrote:
> Christian Fischer wrote:
> > Hello,
> >
> > I have not found a ext4-user list or something similar, that's why my
> > user question goes to this development list.
>
> I think user questions are fine here, but thanks for asking.  :)
>
> > 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.

Thanks Eric for the fast reply.

>
> I think the xfs problems are sorted; you hit a bad spot, but Christoph
> got it worked out.

Hmm, bad spot, I use xfs for years on a lot of servers, never any other, and 
that because of its stability, and its robustness in case of harware 
failures. Never had any problems. I got gray hairs last time.

>
> > What do you think, is ext4 with 2.6.29.4 ready for productive work and to
> > prefer over xfs at the moment?
>
> As for ext4, I don't know of any current problems that would stop you
> from using it for this purpose.  But had you asked about xfs a month ago
> I would have said the same thing.  :)  I can say that ext4 is the
> default for F11, and I have had very few bug reports from users.

I use ext4dev since it came up on my thinkpad, it runs. Good to hear your 
statement.

What do you think about 2.6.29?
Is it okay or should I wait until I can use a xen patched 2.6.31?

>
> All software has bugs, unfortunately, though we do our best.  In the
> end, testing in your environment is the only way to know for sure what
> best suits your needs, I think.

I know, we are in the business. But please not on my main servers ;-)

Christian
>
> -Eric
>
> > Best Regards
> > Christian
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-08-22 20:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-22 17:21 ext4 state user question Christian Fischer
2009-08-22 18:32 ` Eric Sandeen
2009-08-22 19:59   ` Christian Fischer [this message]
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=200908222159.34737.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).