Bug 1263341
| Summary: | FTBFS: coreutils on xfs buildroot | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Pat Riehecky <riehecky> | ||||
| Component: | coreutils | Assignee: | Ondrej Vasik <ovasik> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Jakub Prokes <jprokes> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 7.1 | CC: | csieh, jprokes, jscotka, kdudka, misterbonnie, riehecky | ||||
| Target Milestone: | rc | Keywords: | EasyFix, Patch | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | coreutils-8.22-17.el7 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-11-04 07:39:10 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: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1289025, 1305230 | ||||||
| Attachments: |
|
||||||
|
Description
Pat Riehecky
2015-09-15 15:13:47 UTC
I am not able to reproduce the bug. coreutils-8.22-12.el7_1.2 builds just fine on my VM with fresh RHEL-7.2 Beta installation and the XFS file system. We have a bug about failing dd/sparse test on an XFS file system, which is going to be fixed in RHEL-7.2 (bug #1223041) but it does not seem to be related to this bug report. This test should be skipped on XFS due to no dirent->d_type support. The test does this (in init.cfg): df -x xfs . || skip ... Is the file system not tagged as 'xfs' or something? /etc/mtab shows: /dev/sda6 /var/lib/mock xfs rw 0 0 The host builder is EL6, not EL7 though. Is it possible that the difference in behavior is hiding there? (In reply to Pat Riehecky from comment #4) > The host builder is EL6, not EL7 though. Does it mean the steps to reproduce in comment #0 are not valid? > Is it possible that the difference in behavior is hiding there? How exactly do you build the package? Blast, I made a typo in the reproduction steps (s/7.1/6.7).... Sorry about that. Correct steps (in more detail): 1. Init a mock root on an EL6.7 system with /var/lib/mock as an XFS volume. The buildroot should consist of EL7.1 packages. 2. Resolve all EL7 build deps within the buildroot for coreutils 3. attempt rebuild I'll attach my mock root log, in case it is helpful. Created attachment 1074470 [details]
mockroot
The mock root might explain why df is not detecting 'xfs' correctly. What's the output from `df -T .` and `cat /proc/self/mounts` from within the mock? The output looks like: <mock-chroot>[root@sl7 /]# df -T df: ‘/selinux’: No such file or directory df: ‘/mnt/koji’: No such file or directory df: ‘/var/lib/mock’: No such file or directory df: ‘/export/disk5’: No such file or directory df: ‘/export/linux’: No such file or directory df: ‘/mnt/disk5’: No such file or directory df: ‘/mnt/src’: No such file or directory Filesystem Type 1K-blocks Used Available Use% Mounted on /dev/sda1 ext4 157935264 2365316 155569948 2% / devtmpfs devtmpfs 157935264 2365316 155569948 2% /dev /dev/sda5 xfs 157935264 2365316 155569948 2% /tmp tmpfs tmpfs 8156508 0 8156508 0% /dev/shm mock_chroot_shmfs tmpfs 8156508 0 8156508 0% /dev/shm /dev/sda3 ext4 30106576 7857368 20713208 28% /var/cache/yum /dev/sda5 xfs 25587500 41376 25546124 1% /proc/filesystems <mock-chroot>[root@sl7 /]# cat /proc/self/mounts rootfs / rootfs rw 0 0 /dev/sda1 / ext4 rw,seclabel,relatime,barrier=1,data=ordered 0 0 none /selinux selinuxfs rw,relatime 0 0 devtmpfs /dev devtmpfs rw,seclabel,relatime,size=8145364k,nr_inodes=2036341,mode=755 0 0 devtmpfs /dev devtmpfs rw,seclabel,relatime,size=8145364k,nr_inodes=2036341,mode=755 0 0 devpts /dev/pts devpts rw,seclabel,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /dev/shm tmpfs rw,seclabel,relatime 0 0 proc /proc proc rw,relatime 0 0 /proc/bus/usb /proc/bus/usb usbfs rw,relatime 0 0 none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0 nfsd /proc/fs/nfsd nfsd rw,relatime 0 0 sysfs /sys sysfs rw,seclabel,relatime 0 0 /dev/sdb1 /mnt/koji xfs rw,seclabel,relatime,attr2,delaylog,noquota 0 0 /dev/sda5 /tmp xfs rw,seclabel,relatime,attr2,delaylog,noquota 0 0 /dev/sda3 /var ext4 rw,seclabel,relatime,barrier=1,data=ordered 0 0 /dev/sda6 /var/lib/mock xfs rw,seclabel,relatime,attr2,delaylog,noquota 0 0 sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0 blue1.fnal.gov:/sl-dev /export/disk5 nfs rw,noatime,nodiratime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=131.225.111.89,mountvers=3,mountport=4048,mountproto=tcp,local_lock=none,addr=131.225.111.89 0 0 blue1.fnal.gov:/export/linux /export/linux nfs ro,nosuid,nodev,noexec,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=131.225.111.89,mountvers=3,mountport=4048,mountproto=tcp,local_lock=all,addr=131.225.111.89 0 0 blue1.fnal.gov:/sl-dev /mnt/disk5 nfs rw,noatime,nodiratime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=131.225.111.89,mountvers=3,mountport=4048,mountproto=tcp,local_lock=none,addr=131.225.111.89 0 0 blue1.fnal.gov:/sl-dev /mnt/src nfs rw,noatime,nodiratime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=131.225.111.89,mountvers=3,mountport=4048,mountproto=tcp,local_lock=none,addr=131.225.111.89 0 0 proc /proc proc rw,relatime 0 0 mock_chroot_sys /sys sysfs rw,seclabel,relatime 0 0 mock_chroot_shmfs /dev/shm tmpfs rw,rootcontext=unconfined_u:object_r:var_lib_t:s0,seclabel,relatime 0 0 mock_chroot_devpts /dev/pts devpts rw,seclabel,relatime,gid=5,mode=620,ptmxmode=666 0 0 /dev/sda3 /var/cache/yum ext4 rw,seclabel,relatime,barrier=1,data=ordered 0 0 /dev/sda3 /var/run/pesign ext4 rw,seclabel,relatime,barrier=1,data=ordered 0 0 /dev/sda5 /proc/filesystems xfs rw,seclabel,relatime,attr2,delaylog,noquota 0 0 <mock-chroot>[root@sl7 /]# (In reply to Pat Riehecky from comment #6) > Correct steps (in more detail): > 1. Init a mock root on an EL6.7 system with /var/lib/mock as an XFS volume. > The buildroot should consist of EL7.1 packages. > 2. Resolve all EL7 build deps within the buildroot for coreutils > 3. attempt rebuild Thanks for the update! I can confirm the build fails using the steps above. (In reply to Pat Riehecky from comment #9) > The output looks like: > > <mock-chroot>[root@sl7 /]# df -T Pádraig suggested to run 'df -T .' -- you are missing the dot in your command! > /dev/sda3 ext4 30106576 7857368 20713208 28% /var/cache/yum The above line is the only important since /builddir/build/BUILD/coreutils-8.22 resolves to / which is an ext4 file system according to /proc/self/mounts whose entries are not valid inside the chroot. I am not sure how to improve the skip condition to make it work inside chroot. I improved the test upstream which should avoid this issue http://lists.gnu.org/archive/html/coreutils/2015-11/msg00020.html Thanks, Pádraig. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2497.html |