From: Eric Sandeen <sandeen@sandeen.net>
To: Michael Weissenbacher <mw@dermichi.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS Support in RHEL Server 6.4 x86_64
Date: Wed, 24 Apr 2013 14:50:00 -0500 [thread overview]
Message-ID: <51783768.5050508@sandeen.net> (raw)
In-Reply-To: <5177B899.4000707@dermichi.com>
On 4/24/13 5:48 AM, Michael Weissenbacher wrote:
> Hi List!
> I was under the impression that XFS was officially supported by Red Hat
> Enterprise Linux.
>
> During the installation i noticed that Anaconda wouldn't allow XFS as
> root file system. Well, that's not a big problem for me. But after
> installation i realized that they don't even include xfsprogs so that i
> could do mkfs.xfs. Well, also not a big problem, i used the latest
> tarball and compiled them myself.
Which gets you into unsupported land I'm afraid. As others mentioned,
it's an add-on product in RHEL6, available w/ a separate subscription.
That subscription comes with official RHEL xfsprogs, and support.
> But the big question now is: can anybody actually recommend using XFS on
> stock RHEL? It does feel like being just a stepchild there. On the other
> hand there seem be be quite a number of patches that were backported for
> Red Hat's kernel and it does use delaylog by default (which IIRC wasn't
> the default with a stock 2.6.32 Kernel).
As Ric said, it's very much *not* a stepchild. :)
-Eric
> tia,
> Michael
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-04-24 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 10:48 XFS Support in RHEL Server 6.4 x86_64 Michael Weissenbacher
2013-04-24 15:00 ` James Braid
2013-04-24 17:32 ` Ric Wheeler
2013-04-24 19:50 ` Eric Sandeen [this message]
2013-04-25 7:31 ` Michael Weissenbacher
2013-06-15 11:07 ` Ric Wheeler
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=51783768.5050508@sandeen.net \
--to=sandeen@sandeen.net \
--cc=mw@dermichi.com \
--cc=xfs@oss.sgi.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