FAQ
The new XFS file system code from SGI is now available on the CentOS-4
Developer's testing site.

You can install the dev-testing repo from here:

http://dev.centos.org/centos/4/

And putting the CentOS-Testing.repo file in your /etc/yum.repo.d/
directory.

You can then install the new xfs module on the standard centos i686 or
x86_64 kernels.

You have to pick the proper kernel that you are running.
-------------------------------------------------------------------
Here is the command that would install the XFS module and the minimum
required XFS tools:

yum install dmapi xfsprogs xfsdump kernel-module-xfs-`uname -r`-0.1-1
--------------------------------------------------------------------

This will install the just released XFS code from SGI.

BUT ... this code is still not 100% working with 4K stacks (which all EL
4 and FC 3/4/5 kernels currently use). A note from SGI on this code:

#################################################################
# #
# NOTICE #
# This xfs module rpm has been provided for testing purposes #
# only. It is believed to be functional, but it has not been #
# heavily tested. In particular, you may have issues with the #
# 4KSTACKS option on RHEL4 ia32 kernels, depending on your IO #
# hardware, layering, nfs usage, etc. #
# #
# Please do NOT report any problems with this module, or with #
# the kernel when this module is loaded, to Red Hat. #
# You may report issues to the linux-xfs@oss.sgi.com list. #
# (Please also report successes!) #
# #
#################################################################

You may also report successes and failures to the CentOS-Devel list.

I installed this and ran 15 full tests with Bonnie++ on the XFS
partition without any errors. I was using a PATA drive and a pIII 800
Mhz PC.

------------------------------------------------------
NOTE: This will not run currently with the CentOS Plus kernel, as XFS
is already compiled as a module on that kernel.

After some testing here (if all goes well), a new CentOS Plus kernel
w/out XFS will be compiled and this code will also be moved (with
instructions) to the CentOSPLus repo.
-------------------------------------------------------
NOTE: After completing the install of the XFS code, you should
edit /etc/yum.repos.d/CentOS-Testing.repo and set the line:

enabled=1

TO

enabled=0

to turn off the testing repository for CentOS-4 until you want to
upgrade items from it again. This repo will get other Alpha/Pre Release
type code in it and you would not want to accidentally overwrite stable
CentOS packages during updates.
---------------------------------------------------
Thanks,
Johnny Hughes
CentOS-4 Lead Developer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.centos.org/pipermail/centos-devel/attachments/20051121/efdf9f15/attachment.bin

Search Discussions

  • Eric Sandeen at Nov 22, 2005 at 5:03 am

    Johnny Hughes wrote:
    BUT ... this code is still not 100% working with 4K stacks (which all EL
    4 and FC 3/4/5 kernels currently use). A note from SGI on this code:
    FWIW, I believe only the ia32 kernels have 4KSTACKS turned on... last I
    checked Opteron still did not have this option... feel free to correct
    me if I'm wrong.

    xfs over normal ide/scsi should be fine w/ 4kstacks; if you start piling
    lvm on top of md under nfs etc etc, you could start running into stack
    issues with 4KSTACKS.
    #################################################################
    # #
    # NOTICE #
    # This xfs module rpm has been provided for testing purposes #
    # only. It is believed to be functional, but it has not been #
    # heavily tested. In particular, you may have issues with the #
    # 4KSTACKS option on RHEL4 ia32 kernels, depending on your IO #
    # hardware, layering, nfs usage, etc. #
    # #
    # Please do NOT report any problems with this module, or with #
    # the kernel when this module is loaded, to Red Hat. #
    # You may report issues to the linux-xfs@oss.sgi.com list. #
    # (Please also report successes!) #
    # #
    #################################################################
    Just had to cover myself a bit ;-)

    Thanks,

    -Eric
  • Johnny Hughes at Nov 22, 2005 at 5:18 am

    On Mon, 2005-11-21 at 23:03 -0600, Eric Sandeen wrote:
    Johnny Hughes wrote:
    BUT ... this code is still not 100% working with 4K stacks (which all EL
    4 and FC 3/4/5 kernels currently use). A note from SGI on this code:
    FWIW, I believe only the ia32 kernels have 4KSTACKS turned on... last I
    checked Opteron still did not have this option... feel free to correct
    me if I'm wrong.
    You are correct ... I meant x86 (or i386/i586/i686 or ia32 ... whichever
    term you want to use) for EL4 and FC 3/4/5
    xfs over normal ide/scsi should be fine w/ 4kstacks; if you start piling
    lvm on top of md under nfs etc etc, you could start running into stack
    issues with 4KSTACKS.
    #################################################################
    # #
    # NOTICE #
    # This xfs module rpm has been provided for testing purposes #
    # only. It is believed to be functional, but it has not been #
    # heavily tested. In particular, you may have issues with the #
    # 4KSTACKS option on RHEL4 ia32 kernels, depending on your IO #
    # hardware, layering, nfs usage, etc. #
    # #
    # Please do NOT report any problems with this module, or with #
    # the kernel when this module is loaded, to Red Hat. #
    # You may report issues to the linux-xfs@oss.sgi.com list. #
    # (Please also report successes!) #
    # #
    #################################################################
    Just had to cover myself a bit ;-)

    Thanks,

    -Eric
    Thanks,
    Johnny Hughes
    -------------- next part --------------
    A non-text attachment was scrubbed...
    Name: not available
    Type: application/pgp-signature
    Size: 189 bytes
    Desc: This is a digitally signed message part
    Url : http://lists.centos.org/pipermail/centos-devel/attachments/20051121/a4f87c6f/attachment.bin
  • James Pearson at Nov 24, 2005 at 1:18 pm

    NOTE: This will not run currently with the CentOS Plus kernel, as XFS
    is already compiled as a module on that kernel.

    After some testing here (if all goes well), a new CentOS Plus kernel
    w/out XFS will be compiled and this code will also be moved (with
    instructions) to the CentOSPLus repo.
    I would personally prefer if this XFS code could be merged into the
    CentOS Plus kernel. Having it as a separate RPM is a bit messy.

    If anyone is interested, I've done this and it's available as a patch to
    the existing kernel-2.6.9-22.0.1.106.unsupported.src.rpm via:

    http://home.btconnect.com/james/centos4/

    BTW: what is the significance of '106' in the unsupported kernel name?

    James Pearson
  • Karanbir Singh at Nov 24, 2005 at 1:30 pm

    James Pearson wrote:
    NOTE: This will not run currently with the CentOS Plus kernel, as XFS
    is already compiled as a module on that kernel.

    After some testing here (if all goes well), a new CentOS Plus kernel
    w/out XFS will be compiled and this code will also be moved (with
    instructions) to the CentOSPLus repo.

    I would personally prefer if this XFS code could be merged into the
    CentOS Plus kernel. Having it as a separate RPM is a bit messy.
    If you work back, the number of different options that are available,
    its better to have individual rpm's that complement a standard stable
    kernel.

    Elaborating : there are a few dozen options enabled with the centosplus
    kernel, in the event that any one of those creates a problem for your
    setup - you have an unusalbe xfs setup. Having an individual rpm ensures
    you dont carry the extra baggage of these other options with you.

    Anyway, yum should handle dep's for you, there is no reason why an rpm
    that complements the kernel should be 'messy'.

    As we work to bring in more options like this - I am going to vote for
    seperate rpms' for each, allowing people to pick and choose what they
    need - and be able to use that functionality on a stock stable distro
    kernel.

    just my thoughts.


    --
    Karanbir Singh : http://www.karan.org/ : 2522219@icq
  • James Pearson at Nov 24, 2005 at 1:50 pm

    Karanbir Singh wrote:
    James Pearson wrote:
    NOTE: This will not run currently with the CentOS Plus kernel, as XFS
    is already compiled as a module on that kernel.

    After some testing here (if all goes well), a new CentOS Plus kernel
    w/out XFS will be compiled and this code will also be moved (with
    instructions) to the CentOSPLus repo.


    I would personally prefer if this XFS code could be merged into the
    CentOS Plus kernel. Having it as a separate RPM is a bit messy.

    If you work back, the number of different options that are available,
    its better to have individual rpm's that complement a standard stable
    kernel.

    Elaborating : there are a few dozen options enabled with the centosplus
    kernel, in the event that any one of those creates a problem for your
    setup - you have an unusalbe xfs setup. Having an individual rpm ensures
    you dont carry the extra baggage of these other options with you.

    Anyway, yum should handle dep's for you, there is no reason why an rpm
    that complements the kernel should be 'messy'.
    Might be OK for most 'extras' - but not a file system that could be used
    at install time ... OK, you have to rebuild the installer with the
    CentOS Plus kernel to get to this stage, but this becomes more difficult
    if XFS isn't part of the installer kernel.

    James Pearson
  • Karanbir Singh at Nov 24, 2005 at 1:57 pm

    James Pearson wrote:
    I would personally prefer if this XFS code could be merged into the
    CentOS Plus kernel. Having it as a separate RPM is a bit messy.
    If you work back, the number of different options that are available,
    its better to have individual rpm's that complement a standard stable
    kernel.

    Elaborating : there are a few dozen options enabled with the
    centosplus kernel, in the event that any one of those creates a
    problem for your setup - you have an unusalbe xfs setup. Having an
    individual rpm ensures you dont carry the extra baggage of these other
    options with you.

    Anyway, yum should handle dep's for you, there is no reason why an rpm
    that complements the kernel should be 'messy'.

    Might be OK for most 'extras' - but not a file system that could be used
    at install time ... OK, you have to rebuild the installer with the
    CentOS Plus kernel to get to this stage, but this becomes more difficult
    if XFS isn't part of the installer kernel.
    There is no reason why you could not use the XFS rpm to build an
    installer image.

    Anyway, you need to poke the installer as well, it does not support xfs
    even if the installer kernel + images have xfs support available.

    --
    Karanbir Singh : http://www.karan.org/ : 2522219@icq
  • James Pearson at Nov 24, 2005 at 2:14 pm

    Karanbir Singh wrote:
    James Pearson wrote:
    I would personally prefer if this XFS code could be merged into the
    CentOS Plus kernel. Having it as a separate RPM is a bit messy.

    If you work back, the number of different options that are available,
    its better to have individual rpm's that complement a standard stable
    kernel.

    Elaborating : there are a few dozen options enabled with the
    centosplus kernel, in the event that any one of those creates a
    problem for your setup - you have an unusalbe xfs setup. Having an
    individual rpm ensures you dont carry the extra baggage of these
    other options with you.

    Anyway, yum should handle dep's for you, there is no reason why an
    rpm that complements the kernel should be 'messy'.


    Might be OK for most 'extras' - but not a file system that could be
    used at install time ... OK, you have to rebuild the installer with
    the CentOS Plus kernel to get to this stage, but this becomes more
    difficult if XFS isn't part of the installer kernel.

    There is no reason why you could not use the XFS rpm to build an
    installer image.
    This is the messy bit - you would have to modify anaconda to use the XFS
    rpm - modifying anaconda is not for the faint hearted. Or, create a
    'driver disk' with the XFS modules - again messy.
    Anyway, you need to poke the installer as well, it does not support xfs
    even if the installer kernel + images have xfs support available.
    You can - just add 'xfs' to the installer boot command line.

    James Pearson
  • Karanbir Singh at Nov 24, 2005 at 2:48 pm

    James Pearson wrote:
    Anyway, you need to poke the installer as well, it does not support
    xfs even if the installer kernel + images have xfs support available.

    You can - just add 'xfs' to the installer boot command line.
    have you tried this ?


    --
    Karanbir Singh : http://www.karan.org/ : 2522219@icq
  • James Pearson at Nov 24, 2005 at 3:55 pm

    Karanbir Singh wrote:
    James Pearson wrote:
    Anyway, you need to poke the installer as well, it does not support
    xfs even if the installer kernel + images have xfs support available.


    You can - just add 'xfs' to the installer boot command line.
    have you tried this ?
    Yes. Works fine.

    James Pearson

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcentos-devel @
categoriescentos
postedNov 22, '05 at 4:40a
activeNov 24, '05 at 3:55p
posts10
users4
websitecentos.org
irc#centos

People

Translate

site design / logo © 2022 Grokbase