Bug 28168 - Updated btrfs-progs 5.10 for kernel 5.10
Summary: Updated btrfs-progs 5.10 for kernel 5.10
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: 2021-01-19 14:50 CET by David Walser
Modified: 2021-01-25 16:27 CET (History)
2 users (show)

See Also:
Source RPM: btrfs-progs-5.9-1.mga7.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description David Walser 2021-01-19 14:50:31 CET 
Advisory:
----------------------------------------

The btrfs-progs package has been updated to version 5.10, with full support
for the 5.10 series Linux kernels, bug fixes, and other enhancements.  See the
upstream Changelog for details.

References:
https://lore.kernel.org/linux-btrfs/20210118222021.11603-1-dsterba@suse.com/
----------------------------------------

Updated packages in core/updates_testing:
----------------------------------------
btrfs-progs-5.10-1.mga7
lib64btrfs0-5.10-1.mga7
lib64btrfsutil1-5.10-1.mga7
lib64btrfs-devel-5.10-1.mga7

from btrfs-progs-5.10-1.mga7.src.rpm
Comment 1 Aurelien Oudelet 2021-01-25 14:35:20 CET 
btrfs volume as /
Applying update to a M7 x86_64.
Subsequent reboot is OK.

Testing to make a btrfs to an USB drive is OK.
fsck this volume is OK.
fsck / is OK too.

Writing a file, copy a directory is OK.

No regression, overall speed I/O notably improved since kernel 5.10.10 in M7/updates_testing.
Validating.

Advisory pushed to SVN.

CC: (none) => ouaurelien, sysadmin-bugs
Whiteboard: (none) => MGA7-64-OK
Keywords: (none) => advisory, validated_update

Comment 2 Mageia Robot 2021-01-25 16:27:01 CET 
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2021-0015.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.