| Summary: | Updated xfsprogs to 5.1.0 to match kernel | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | andrewsfarm, brtians1, sysadmin-bugs, tmb |
| Version: | 7 | Keywords: | advisory, validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA7-64-OK | ||
| Source RPM: | xfsprogs | CVE: | |
| Status comment: | |||
|
Description
David Walser
2019-05-13 03:45:25 CEST
This was missed. We're now on kernel 5.1.x, so it should be updated to 5.1.0. Whiteboard:
(none) =>
MGA7TOO Fixed in cauldron. For Mga7: SRPMS: xfsprogs-5.1.0-1.mga7.src.rpm i586: libxfs1-5.1.0-1.mga7.i586.rpm libxfs-devel-5.1.0-1.mga7.i586.rpm libxfs-static-devel-5.1.0-1.mga7.i586.rpm xfsprogs-5.1.0-1.mga7.i586.rpm x86_64: lib64xfs1-5.1.0-1.mga7.x86_64.rpm lib64xfs-devel-5.1.0-1.mga7.x86_64.rpm lib64xfs-static-devel-5.1.0-1.mga7.x86_64.rpm xfsprogs-5.1.0-1.mga7.x86_64.rpm Version:
Cauldron =>
7 Baseline of system, this is physical hardware. $ uname -a Linux localhost 5.1.20-desktop-2.mga7 #1 SMP Fri Jul 26 23:04:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux /dev/sda1 on / type xfs (rw,relatime,attr2,inode64,noquota) /dev/sda6 on /home type xfs (rw,relatime,attr2,inode64,noquota) Before Patching [root@localhost brian]# xfs_bmap / /: no extents [root@localhost brian]# xfs_bmap /home /home: no extents [root@localhost brian]# xfs_estimate /home /home will take about 2308.7 megabytes [root@localhost brian]# Installing the changes The following 5 packages are going to be installed: - lib64uuid-devel-2.33.2-1.mga7.x86_64 - lib64xfs-devel-5.1.0-1.mga7.x86_64 - lib64xfs-static-devel-5.1.0-1.mga7.x86_64 - lib64xfs1-5.1.0-1.mga7.x86_64 - xfsprogs-5.1.0-1.mga7.x86_64 382KB of additional disk space will be used. --- after install I rebooted the machine---- Hurray it booted up!!! Not knowing how deep these libraries go into the base XFS instructure, I'm guessing here. $ mount | grep dev/sda /dev/sda1 on / type xfs (rw,relatime,attr2,inode64,noquota) /dev/sda6 on /home type xfs (rw,relatime,attr2,inode64,noquota) # xfs_bmap / /: no extents # xfs_bmap /home /home: no extents # xfs_estimate /home /home will take about 2303.4 megabytes (it changed, but I'm guessing that's due to the reboot or calculation). I checked the journalctl logs Aug 02 06:52:06 localhost kernel: SGI XFS with ACLs, security attributes, realtime, no debug enabled Aug 02 06:52:06 localhost kernel: XFS (sda1): Mounting V5 Filesystem Aug 02 06:52:06 localhost kernel: XFS (sda1): Ending clean mount Aug 02 06:52:07 localhost systemd-fsck[531]: /usr/sbin/fsck.xfs: XFS file system. Aug 02 06:52:15 localhost systemd-fsck[737]: /usr/sbin/fsck.xfs: XFS file system. Aug 02 06:52:15 localhost kernel: XFS (sda6): Mounting V5 Filesystem Aug 02 06:52:15 localhost kernel: XFS (sda6): Ending clean mount Aug 02 16:42:52 localhost kernel: XFS (sda6): Unmounting Filesystem Aug 02 16:43:29 localhost kernel: SGI XFS with ACLs, security attributes, realtime, no debug enabled Aug 02 16:43:29 localhost kernel: XFS (sda1): Mounting V5 Filesystem Aug 02 16:43:29 localhost kernel: XFS (sda1): Ending clean mount Aug 02 16:43:30 localhost systemd-fsck[536]: /usr/sbin/fsck.xfs: XFS file system. Aug 02 16:43:38 localhost systemd-fsck[738]: /usr/sbin/fsck.xfs: XFS file system. Aug 02 16:43:38 localhost kernel: XFS (sda6): Mounting V5 Filesystem Aug 02 16:43:38 localhost kernel: XFS (sda6): Ending clean mount As far as I can tell, it works. CC:
(none) =>
brtians1 Been running this since it got build on an x86_64 server with ~14TB storage... CC:
(none) =>
tmb Thomas - was my test legit? Just need your input and then I'll give it an approval. Yeah, it is...
Brian Rockwell
2019-08-08 19:32:53 CEST
Whiteboard:
(none) =>
MGA7_64_OK
Brian Rockwell
2019-08-08 19:33:54 CEST
Whiteboard:
MGA7_64_OK =>
MGA7-64-OK Validating. Keywords:
(none) =>
validated_update
Thomas Backlund
2019-08-09 22:31:52 CEST
Keywords:
(none) =>
advisory An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2019-0078.html Resolution:
(none) =>
FIXED |