We've been using XFS with CentOS for a while now, but we always created the volumes post-kickstart as part of our puppet runs. After hearing that CentOS/RHEL 5.4 would support XFS in Kickstart, we gave it a try. It didn't really work the way we thought it would and started looking around in Google results. Sadly, this information isn't really written down anywhere, so here it is. We're not doing anything novel here, I just thought that I'd post it to save people a lot of time and trouble. Keep in mind that we don't create our root partitions with XFS (we still use EXT3 for that), but we do create our "data" partitions using XFS.
parted -s /dev/sdb mklabel gpt parted -s /dev/sdb unit s mkpart primary 2048 100%
rpm -Uvhi /mnt/tmpnfs/src/xfsdump-2.2.46-1.el5.centos.x86_64.rpm rpm -Uvhi /mnt/tmpnfs/src/xfsprogs-2.9.4-1.el5.centos.x86_64.rpm
mkdir /data /sbin/mkfs.xfs -f -d su=64k,sw=3 -l size=32m,su=16k -L /data /dev/sdb1
Thomas
7/3/2012 06:59:55 am
Hi,
Thomas, you found a Weebly bug! Looks like the exact text didn't quite get pasted in properly. I've verified it and escalated the issue with our developers. Anyhow, you're right that it should be --fstype=xfs. I've updated the appropriate text. If you're getting a failure with --fstype=xfs, try either a "modprobe xfs" in a %pre step or adding the keyword "xfs" to your PXE kernel boot line. Example:
Thomas
7/5/2012 03:32:23 am
Thanks for the response and correction. I am getting the following message. I tried Thomas, which version of CentOS are you running? Is it possible to check /tmp/anaconda.log or dmesg output from the host? The error looks related to partition definitions, but I can't say it's related to the XFS entry. Could be related to something else and there's a typo somewhere? What does parted print output say? I'd look down these routes for your answer.
Thomas
7/6/2012 12:57:34 am
I'm running CentOS 5.5. The following is my part definition.
OK well that's the problem then. You cannot let the kickstart partitioner create the partition for you. Even though you set noformat, it doesn't understand xfs. You added --grow and a size, so it's going to want to muck with stuff. If you just have --onpart and --noformat with no size or grow options, the installer will just add a fstab entry and ignore it. Re-read the section in the post about the %pre section and creating your own partition.
Thomas
7/9/2012 08:07:07 am
You are correct. I was trying to incorporate this with foreman and had some of the lines in the wrong location. Comments are closed.
|
AuthorA NOLA native just trying to get by. I live in San Francisco and work as a digital plumber for the joint that runs this thing. (Square/Weebly) Thoughts are mine, not my company's. Archives
May 2021
Categories
All
|