Bug 1374164

Summary: Install fails on XFS V5 file system
Product: Red Hat Enterprise Linux 7 Reporter: Frank Büttner <bugzilla>
Component: xfsprogsAssignee: Eric Sandeen <esandeen>
Status: CLOSED NEXTRELEASE QA Contact: Filesystem QE <fs-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: bugzilla
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-14 14:24:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
syslog file
none
storage log
none
Program log none

Description Frank Büttner 2016-09-08 07:09:04 UTC 
Description of problem:
Anaconda reject the installation on an empty xfs file system, when it was created as xfs V5.

How reproducible:
every time 

Steps to Reproduce:
1. create the the /boot partition as xfs v4 via mkfs.xfs -m crc=0 /dev/sda1
2. create the / partition as xfs v5 via mkfs.xfs -m crc=1 -m finobt=1 /dev/sda2
3. reboot and try to install RHEL 7.2

Actual results:
You can select /dev/sda1 as /boot, but select /dev/sda2 as root will fail with the message, that the partition can't be used.


Expected results:
Working installation with an xfs V5 / file system. 


Additional info:
/boot must be xfs V4 because grub has problems with xfs V5.
But the documentation there are no hint of any problems with xfs V5 as the root file system.
Comment 2 Frank Büttner 2016-09-08 12:03:17 UTC 
Here the output of the anaconda log:
14:33:13,435 INFO anaconda: spoke is not ready: <pyanaconda.ui.gui.spokes.storage.StorageSpoke object at 0x7fb42a600a10>
14:33:13,436 INFO anaconda: setting <pyanaconda.ui.gui.spokes.storage.StorageSpoke object at 0x7fb42a600a10> status to: Saving storage configuration...
14:33:13,438 INFO anaconda: spoke is ready: <pyanaconda.ui.gui.spokes.storage.StorageSpoke object at 0x7fb42a600a10>
14:33:15,220 DEBUG anaconda: page clicked: Unknown
14:33:15,220 DEBUG anaconda: show mountpoint: Unknown
14:33:15,222 DEBUG anaconda: populate_right_side: existing 476 MiB partition sda1 (7) with existing xfs filesystem
14:33:15,227 DEBUG anaconda: updated device_disks to [u'sda']
14:33:15,227 DEBUG anaconda: updated device_container_name to None
14:33:15,227 DEBUG anaconda: updated device_container_raid_level to None
14:33:15,227 DEBUG anaconda: updated device_container_encrypted to False
14:33:15,227 DEBUG anaconda: updated device_container_size to 0
14:33:15,231 DEBUG anaconda: device_type_changed: 2 <gi.overrides.Gtk.TreeModelRow object at 0x7fb426d7c210>
14:33:15,232 DEBUG anaconda: populate_raid: 2, None
14:33:15,233 DEBUG anaconda: populate_raid: 2, None
14:33:25,927 INFO anaconda: ui: saving changes to device sda1
14:33:25,928 DEBUG anaconda: reformat: False
14:33:25,934 DEBUG anaconda: old disks: [u'sda']
14:33:25,934 DEBUG anaconda: new disks: [u'sda']
14:33:25,935 DEBUG anaconda: device: existing 476 MiB partition sda1 (7) with existing xfs filesystem
14:33:25,940 DEBUG anaconda: old container_encrypted: False
14:33:25,940 DEBUG anaconda: new container_encrypted: False
14:33:25,940 DEBUG anaconda: old name: sda1
14:33:25,940 DEBUG anaconda: new name: None
14:33:25,940 DEBUG anaconda: old encrypted: False
14:33:25,941 DEBUG anaconda: new encrypted: False
14:33:25,941 DEBUG anaconda: old container_raid_level: None
14:33:25,941 DEBUG anaconda: new container_raid_level: None
14:33:25,941 DEBUG anaconda: old raid_level: None
14:33:25,941 DEBUG anaconda: new raid_level: None
14:33:25,941 DEBUG anaconda: old fstype: xfs
14:33:25,941 DEBUG anaconda: new fstype: xfs
14:33:25,941 DEBUG anaconda: old min_luks_entropy: 256
14:33:25,941 DEBUG anaconda: new min_luks_entropy: 256
14:33:25,941 DEBUG anaconda: old device_type: 2
14:33:25,941 DEBUG anaconda: new device_type: 2
14:33:25,942 DEBUG anaconda: old container_name: None
14:33:25,942 DEBUG anaconda: new container_name: None
14:33:25,942 DEBUG anaconda: old mountpoint: 
14:33:25,942 DEBUG anaconda: new mountpoint: /boot
14:33:25,942 DEBUG anaconda: old label: 
14:33:25,942 DEBUG anaconda: new label: 
14:33:25,942 DEBUG anaconda: old container_size: 0
14:33:25,942 DEBUG anaconda: new container_size: 0
14:33:25,942 DEBUG anaconda: old size: 476 MiB
14:33:25,947 DEBUG anaconda: new size: 476 MiB
14:33:25,952 DEBUG anaconda: updating mountpoint of sda1 to /boot
14:33:25,958 DEBUG anaconda: populate_right_side: existing 476 MiB partition sda1 (7) with existing xfs filesystem mounted at /boot
14:33:25,963 DEBUG anaconda: updated device_disks to [u'sda']
14:33:25,963 DEBUG anaconda: updated device_container_name to None
14:33:25,963 DEBUG anaconda: updated device_container_raid_level to None
14:33:25,963 DEBUG anaconda: updated device_container_encrypted to False
14:33:25,963 DEBUG anaconda: updated device_container_size to 0
14:33:25,966 DEBUG anaconda: populate_raid: 2, None
14:33:27,124 DEBUG anaconda: current selector: existing 476 MiB partition sda1 (7) with existing xfs filesystem mounted at /boot
14:33:27,130 DEBUG anaconda: new selector: existing 19.53 GiB partition sda2 (12) with existing xfs filesystem
14:33:27,135 DEBUG anaconda: populate_right_side: existing 19.53 GiB partition sda2 (12) with existing xfs filesystem
14:33:27,141 DEBUG anaconda: updated device_disks to [u'sda']
14:33:27,141 DEBUG anaconda: updated device_container_name to None
14:33:27,141 DEBUG anaconda: updated device_container_raid_level to None
14:33:27,141 DEBUG anaconda: updated device_container_encrypted to False
14:33:27,141 DEBUG anaconda: updated device_container_size to 0
14:33:27,144 DEBUG anaconda: populate_raid: 2, None
14:33:30,180 DEBUG anaconda: current selector: existing 19.53 GiB partition sda2 (12) with existing xfs filesystem
14:33:30,186 DEBUG anaconda: new selector: existing 476 MiB partition sda1 (7) with existing xfs filesystem mounted at /boot
14:33:30,191 DEBUG anaconda: populate_right_side: existing 476 MiB partition sda1 (7) with existing xfs filesystem mounted at /boot
14:33:30,196 DEBUG anaconda: updated device_disks to [u'sda']
14:33:30,196 DEBUG anaconda: updated device_container_name to None
14:33:30,197 DEBUG anaconda: updated device_container_raid_level to None
14:33:30,197 DEBUG anaconda: updated device_container_encrypted to False
14:33:30,197 DEBUG anaconda: updated device_container_size to 0
14:33:30,199 DEBUG anaconda: populate_raid: 2, None
14:33:30,200 DEBUG anaconda: populate_right_side: existing 476 MiB partition sda1 (7) with existing xfs filesystem mounted at /boot
14:33:30,205 DEBUG anaconda: updated device_disks to [u'sda']
14:33:30,205 DEBUG anaconda: updated device_container_name to None
14:33:30,205 DEBUG anaconda: updated device_container_raid_level to None
14:33:30,205 DEBUG anaconda: updated device_container_encrypted to False
14:33:30,205 DEBUG anaconda: updated device_container_size to 0
14:33:30,208 DEBUG anaconda: populate_raid: 2, None
14:33:31,876 DEBUG anaconda: current selector: existing 476 MiB partition sda1 (7) with existing xfs filesystem mounted at /boot
14:33:31,885 DEBUG anaconda: new selector: existing 476 MiB partition sda1 (7) with existing xfs filesystem mounted at /boot
14:33:31,894 DEBUG anaconda: populate_right_side: existing 476 MiB partition sda1 (7) with existing xfs filesystem mounted at /boot
14:33:31,902 DEBUG anaconda: updated device_disks to [u'sda']
14:33:31,903 DEBUG anaconda: updated device_container_name to None
14:33:31,903 DEBUG anaconda: updated device_container_raid_level to None
14:33:31,903 DEBUG anaconda: updated device_container_encrypted to False
14:33:31,903 DEBUG anaconda: updated device_container_size to 0
14:33:31,907 DEBUG anaconda: populate_raid: 2, None
14:33:33,348 DEBUG anaconda: current selector: existing 476 MiB partition sda1 (7) with existing xfs filesystem mounted at /boot
14:33:33,354 DEBUG anaconda: new selector: existing 19.53 GiB partition sda2 (12) with existing xfs filesystem
14:33:33,359 DEBUG anaconda: populate_right_side: existing 19.53 GiB partition sda2 (12) with existing xfs filesystem
14:33:33,365 DEBUG anaconda: updated device_disks to [u'sda']
14:33:33,365 DEBUG anaconda: updated device_container_name to None
14:33:33,365 DEBUG anaconda: updated device_container_raid_level to None
14:33:33,365 DEBUG anaconda: updated device_container_encrypted to False
14:33:33,365 DEBUG anaconda: updated device_container_size to 0
14:33:33,368 DEBUG anaconda: populate_raid: 2, None
14:33:37,799 INFO anaconda: ui: saving changes to device sda2
14:33:37,799 DEBUG anaconda: reformat: False
14:33:37,801 DEBUG anaconda: populate_right_side: existing 19.53 GiB partition sda2 (12) with existing xfs filesystem
14:33:37,807 DEBUG anaconda: updated device_disks to [u'sda']
14:33:37,807 DEBUG anaconda: updated device_container_name to None
14:33:37,807 DEBUG anaconda: updated device_container_raid_level to None
14:33:37,807 DEBUG anaconda: updated device_container_encrypted to False
14:33:37,807 DEBUG anaconda: updated device_container_size to 0
14:33:37,810 DEBUG anaconda: populate_raid: 2, None
Comment 3 David Lehman 2016-09-08 14:58:06 UTC 
Please collect /tmp/syslog, /tmp/program.log, and /tmp/storage.log from vt2 after the failure has occurred and attach them to this bug report. Thanks.
Comment 4 Frank Büttner 2016-09-09 10:21:23 UTC 
Created attachment 1199372 [details]
syslog file
Comment 5 Frank Büttner 2016-09-09 10:26:31 UTC 
Created attachment 1199373 [details]
storage log
Comment 6 Frank Büttner 2016-09-09 10:29:42 UTC 
Created attachment 1199374 [details]
Program log
Comment 7 David Lehman 2016-09-09 21:06:19 UTC 
The message you saw is probably because the installer does not allow the use of a preexisting filesystem for the root filesystem.
Comment 8 Frank Büttner 2016-09-10 06:33:18 UTC 
My intention for doing this, was the fact, that anaconda format the xfs file system only with v4. But meta data checksum to protect the journal during an hardware error are only supported with xfs v5.
Comment 9 David Lehman 2016-09-12 15:05:00 UTC 
The only option I am aware of that would allow you to easily install to an xfs v5 root filesystem is kickstart (the '--mkfsoptions' option to the 'partition' command).

https://github.com/rhinstaller/pykickstart/blob/rhel7-branch/docs/kickstart-docs.rst#part-or-partition
Comment 10 Frank Büttner 2016-09-13 12:03:28 UTC 
Yes, this workaround will work.
But will it be not better to fix anaconda, so that an V5 file system is created?
For this case 2 option are available.
- first add the 2 parameter by default when creating an xfs file system.
- second, update the xfs tools to the last version, because here the both option are default for now.

I have also tested, that grub can boot from xfs V5. It will work also.
Comment 11 David Lehman 2016-09-13 17:54:16 UTC 
If you would like to request that xfs v5 become the default for new xfs filesystems in RHEL-7 you should do that in a bug report against xfsprogs. You can either open a new bug for that or reassign this one (change the summary to reflect the bug's purpose).
Comment 12 Frank Büttner 2016-09-14 12:09:49 UTC 
OK David, I will change the component type to xfsprogs
Comment 13 Frank Büttner 2016-09-14 12:22:24 UTC 
Package version: xfsprogs-3.2.2-2.el7.x86_64
Comment 14 Eric Sandeen 2016-09-14 14:24:59 UTC 
RHEL7.3 will have a newer version of xfsprogs, and CRCS will be enabled by default, so new installs will do exactly what you are hoping for.

-Eric