Bug 26694 - Updated xfsprogs to 5.6.0 to match kernel
Summary: Updated xfsprogs to 5.6.0 to match kernel
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2020-05-27 21:15 CEST by David Walser
Modified: 2020-06-11 00:58 CEST (History)
4 users (show)

See Also:
Source RPM: xfsprogs-5.4.0-1.mga7.src.rpm
CVE:
Status comment:


Attachments

Description David Walser 2020-05-27 21:15:49 CEST
Advisory:
----------------------------------------

This update adds full support for kernel 5.6 series

----------------------------------------

Updated packages in core/updates_testing:
----------------------------------------
xfsprogs-5.6.0-1.mga7
libxfs1-5.6.0-1.mga7
libxfs-devel-5.6.0-1.mga7
libxfs-static-devel-5.6.0-1.mga7

from xfsprogs-5.6.0-1.mga7.src.rpm
Comment 1 Herman Viaene 2020-05-30 14:52:04 CEST
MGA7-64 Plasma on Lenovo B50
No installation issues.
Ref bug 24805 for some tests.
I don't have an XFS partition on this laptop, so using a 16Gb USB stick to fiddle with.
# mkfs.xfs  /dev/sdb 
mkfs.xfs: /dev/sdb appears to contain an existing filesystem (vfat).
mkfs.xfs: Use the -f option to force overwrite.
[root@mach5 ~]# mkfs.xfs  -f /dev/sdb 
meta-data=/dev/sdb               isize=512    agcount=4, agsize=976832 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=1
data     =                       bsize=4096   blocks=3907328, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
That made the stick only accessible to root, so opened it to the world. Created as normal user a text file, inserted the stick in my desktop PC, there  could read the file.
Some more at the CLI:
# mount | grep sdb
/dev/sdb on /run/media/tester7/ce1ee9ca-e170-438d-b271-3919eb563986 type xfs (rw,nosuid,nodev,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota,uhelper=udisks2)

# xfs_bmap /run/media/tester7/ce1ee9ca-e170-438d-b271-3919eb563986
/run/media/tester7/ce1ee9ca-e170-438d-b271-3919eb563986: no extents


# xfs_info /run/media/tester7/ce1ee9ca-e170-438d-b271-3919eb563986
meta-data=/dev/sdb               isize=512    agcount=4, agsize=976832 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=1
data     =                       bsize=4096   blocks=3907328, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

# xfs_estimate /run/media/tester7/ce1ee9ca-e170-438d-b271-3919eb563986
/run/media/tester7/ce1ee9ca-e170-438d-b271-3919eb563986 will take about 4.4 megabytes
I'm not sure what that last command estimates, but it doesn't seem nonsens, so for me OK.

CC: (none) => herman.viaene
Whiteboard: (none) => MGA7-64-OK

Comment 2 Thomas Andrews 2020-05-30 15:42:18 CEST
Validating. Advisory in Comment 0.

CC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => validated_update

Nicolas Lécureuil 2020-06-11 00:18:43 CEST

Keywords: (none) => advisory
CC: (none) => mageia

Comment 3 Mageia Robot 2020-06-11 00:58:19 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0143.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.