F33 Brtfs By Default Test Day

More information about the event can be found here: http://fedoraproject.org/wiki/Test_Day:2020-07-08_Btrfs_default
Go back to List of Events.

Results

Clicking on the testcase name will show you the appropriate "how to test" page.
Click on the Enter result button, to enter result.
Note: results are cached and realoaded from the database each 10 seconds.

Initial

Username Profile Install to Previous KVM Comments
Enter result
FlexibleToast KVM Proxmox and oVirt
Schykle
Schykle x86_64
alciregi KVM, x86_64, bios
alexfinkel [1] 1. The /boot partition is still using ext4.
archmunky KVM, UEFI
bcgates KVM
carlwgeorge KVM, x86_64, gnome-boxes
cmurf KVM
decathorpe KVM
devil24g KVM
gilbus KVM
ifel KVM [1] 1. Host: Ryzen 5 1600, 48G, 1 Gbit NIC, Ubuntu 18.04.4 LTS, qemu-kvm 1:2.12+dfsg-0~18.04~ppa0. Storage: Synology DS918+, 4x4T Seagate IronWolf in RAID5, 2Gbit bond connection, BTRFS. Guest: 2 Cores, 4GB, UEFI, iSCSI Thin provisioned volume from the storage. Installation took 13 minutes (from "Install to Hard Drive" to "Complete!")
ifel x86_64 [1] 1. Lenovo ThinkPad X1 Carbon 3rd, model 20BTS0Y500; Installation took 8 minutes (from "Install to Hard Drive" to "Complete!")
igaldino KVM
jskladan KVM
kanderson KVM [1] 1. Installed with Fedora-Everything-netinst-x86_64-Rawhide-20200707.n.0.iso and chose the Workstation package group. Use a custom partition, chose btrfs, and selected to create the default partitions and completed installation.
kartikay1506
kparal virt-manager [1] 1. After seeing lruzicka's comment, I measured installation times for 0707 Workstation (lvm+ext4) and testday 0708 Workstation btrfs images. The installation was long (almost 9 minutes) in both cases. So btrfs doesn't cause any slowdown here. The long times are probably caused by using a debug kernel.
lruzicka KVM, x86_64, bios based [1] 1. The installation took longer than I am normally used to.
mcatanzaro KVM
mhoungbo Virtual Machine Manager 2.2.1
mzumquadrat KVM
nasirhm KVM/QEMU x86_64 on Lenovo Thinkpad X1 Carbon
ondra05 VirtualBox [1] 1. Custom partitioning: 600 MiB EFI, 23.4 GiB BtrFS, / and /home subvols
salimma Btrfs, both without encryption and with encryption [1] 1. with encryption, two LUKS volumes end up being created (one for swap and one for btrfs). this is transparent as long as the passphrase matches but otherwise makes for an annoying UX -- but should be temporary as the swap-on-zram Change should be landing soon.
salimma Btrfs, no encryption
sumantrom KVM
yang Install to Previous KVM
yanqiyu A old HP laptop(HDD), and KVM on SSD [1] 1. To add: did a force Compress, all worked fine.

Release-blocking (x86_64)

Username Profile Initial setup Startup Reboot Unmount System Logging Update CLI Package Install/Remove Service Start Selinux Service Manupluation Comments
Enter result Enter result Enter result Enter result Enter result Enter result Enter result Enter result Enter result
FlexibleToast KVM Proxmox and oVirt [1] [2] 1. Initial-setup on install with encryption enabled briefly hung after password was chosen. Before I could click the "wait" button it had already completed.
2. Both installations had a similar error. oVirt encryption install: kernel: raid6: using avx2x2 recovery algorithm Proxmox install: kernel: raid6: using intx1 recovery algorithm
Iolo x86_64 [1] [2] 1. Thinkpad X220, Workstation image, UEFI, LUKS2, Gnome Xorg, Kingston SV300S37A240G SSD; I customized partitioning slightly: 600 MiB /boot/efi (vfat), 1 GiB /boot (xfs), all available space to / (btrfs).
2. Grep does produce output, but it does not appear to be an error, but a simple notification: heinä 08 21:23:31 localhost.localdomain kernel: raid6: using ssse3x2 recovery algorithm
alciregi KVM, x86_64, bios
alexfinkel [1] 1. One line of output from the grep which appears to be informational: Jul 08 18:07:37 localhost.localdomain kernel: raid6: using ssse3x2 recovery algorithm
archmunky KVM, UEFI [1] [2] [3] 1. First reboot appeared to hang requiring hard reboot. Volume was marked as dirty but the journal was recovered successfully.
2. cli update succeed. should consider dnf addon to automatically create snapshots before dnf up
3. WARNING: possible circular locking dependency detected... *** DEADLOCK ***.... Jul 08 23:04:55 fed-btrfs kernel: 3 locks held by systemd-journal/492: Jul 08 23:04:55 fed-btrfs kernel: #0: ffffa0de7b1ec238 (&mm->mmap_lock#2){++++}-{3:3}, at: do_user_addr_fault+0x12e/0x4b0 Jul 08 23:04:55 fed-btrfs kernel: #1: ffffa0de70fbb598 (sb_pagefaults){.+.+}-{0:0}, at: btrfs_page_mkwrite+0x59/0x560 [btrfs] Jul 08 23:04:55 fed-btrfs kernel: #2: ffffa0de70fbb6a8 (sb_internal){.+.+}-{0:0}, at: start_transaction+0x3f8/0x500 [btrfs]
bcgates KVM [1] 1. I got this: "Jul 08 09:55:15 localhost.localdomain kernel: raid6: using ssse3x2 recovery algorithm" but I don't think this is an error.
bryanquigley HP Chromebook 11 G4 running Coreboot, 16 GB eMMC [1] 1. got raid6: using message like others - don't believe it's a bug
bryanquigley HP Chromebook 11 G4 running mrchromebox.tech coreboot - EUFI, 16 GB eMMC
chrimage Lenovo Ideapad Flex 5, AMD Ryzen 4500U
christian VirtualBox
cmurf mbp82,hpspectre
coremodule Raspberry Pi 3B+ Fedora-Workstation-Rawhide-20200706-btrfs.raw.xz [1] 1. #1855522,
dcavalca VMware x86_64 bios
decathorpe KVM [1] 1. mcelog.service failed, but I think this is normal in KVM
devil24g KVM
gamma VBox [1] 1. Default install with locale de, nothing else changed. on executing 'sudo journalctl -b | grep -E 'dirty bit|data may be corrupt|recovery|unmounted|recovering'' i get the message: localohst.localdomain kernel: raid6: using avx2x2 recovery algorithm
gilbus KVM
ifel KVM [1] [2] 1. Testcase_base_reboot_unmount: Jul 08 09:02:13 localhost.localdomain kernel: raid6: using avx2x2 recovery algorithm After reboot: Jul 08 09:24:53 localhost.localdomain kernel: raid6: using avx2x2 recovery algorithm
2. ● mcelog.service loaded failed failed Machine Check Exception Logging Daemon -- Logs begin at Wed 2020-07-08 09:02:13 PDT, end at Wed 2020-07-08 09:43:13 PDT. -- Jul 08 09:25:00 localhost.localdomain systemd[1]: Started Machine Check Exception Logging Daemon. Jul 08 09:25:00 localhost.localdomain mcelog[598]: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. Jul 08 09:25:00 localhost.localdomain mcelog[598]: CPU is unsupported Jul 08 09:25:00 localhost.localdomain systemd[1]: mcelog.service: Main process exited, code=exited, status=1/FAILURE Jul 08 09:25:00 localhost.localdomain systemd[1]: mcelog.service: Failed with result 'exit-code'.
ifel x86_64 [1] 1. Testcase_base_reboot_unmount: Jul 08 09:14:30 localhost.localdomain kernel: raid6: using avx2x2 recovery algorithm After reboot: Jul 08 09:20:30 localhost.localdomain kernel: raid6: using avx2x2 recovery algorithm
igaldino KVM [1] 1. $ sudo journalctl -b | grep -E 'dirty bit|data may be corrupt|recovery|unmounted|recovering' jul 09 12:17:00 localhost.localdomain kernel: raid6: using avx2x2 recovery algorithm
jskladan KVM
kanderson KVM
kartikay1506
kparal virt-manager [1] 1. kernel: raid6: using avx2x2 recovery algorithm
lruzicka KVM, x86_64, bios based
mcatanzaro KVM [1] 1. I only tested rebooting the installed system, didn't check for errors after rebooting the installer. The grep line is going to need to be adjusted because there is now a false-positive: Jul 08 14:05:26 localhost.localdomain kernel: raid6: using avx2x2 recovery algorithm
mzumquadrat KVM
nasirhm KVM/QEMU x86_64 on Lenovo Thinkpad X1 Carbon [1] [2] 1. Jul 09 23:22:38 localhost.localdomain kernel: raid6: using avx2x2 recovery algorithm
2. Tested with i3wm and sway
nielsenb Compaq 8510w Intel T9300 AMD RV630 BIOS [1] 1. Always shows "raid6: using ssse3x2 recovery algorithm"
pwhalen KVM, AArch64 [1] 1. Used this disk image - https://pwhalen.fedorapeople.org/Fedora-Workstation-Rawhide-Btrfs-AArch64/Fedora-Workstation-Rawhide-20200706-btrfs.raw.xz
salimma KVM, x86_64, LUKS [1] [2] 1. New user created with sudo access. The UX is weird (asking for online accounts before asking for the user name) but that's outside the scope of this test day.
2. Jul 08 15:05:14 localhost.localdomain kernel: raid6: using avx2x2 recovery algorithm but this is unrelated
steelcowboy HP EliteBook 735 G6, AMD Ryzen Pro 3700U
sumantrom Baremetal lenovo T580 with Test Day Iso [1] 1. [sumantro93@localhost ~]$ sudo journalctl -b | grep -E 'dirty bit|data may be corrupt|recovery|unmounted|recovering' [sudo] password for sumantro93: Jul 08 09:30:02 localhost.localdomain kernel: raid6: using avx2x2 recovery algorithm
sumantrom KVM
tflink x86_64 hardware
thynkon KVM, x86_64
thynkon KVM, x86_64, KDE Plasma
tiny6996 Lenovo E485
yang KVM
yanqiyu X86_64,KVM and baremetal [1] [2] 1. I am making /boot as a subvolume
2. Everything worked fine!
yozaam VirtualBox Ram:4GB installed Fedora-Workstation-Live-x86_64-20200708-btrfsdefault.iso dynamic Virtual Disk Image: 12GB Running & installed on a external hard drive [1] [2] 1. Very slow and took more than 30 minutes for the "installing software" stage while installing to hard drive, Have installed multiple workstation iso's in the past, they do not take so much time ( maybe because it is a external hdd (exFAT) / maybe because it is a dynamic .vdi drive
2. No mount error but recovery raid6 same as user:gamma above `Jul 08 17:04:35 localhost.localdomain kernel: raid6: using avx2x2 recovery algorithm` I wonder if this is vbox thing?
zbyszek AMD64 KVM UEFI sd-boot, continually upgraded since F31

Desktop

Username Profile Desktop Browser Desktop Login Audio Basic Desktop Panel Basic Desktop Automount Workstation core Apps Update graphical Virtual Printer Update notif Error Checks Comments
Enter result Enter result Enter result Enter result Enter result Enter result Enter result Enter result Enter result Enter result
FlexibleToast KVM Proxmox and oVirt
Schykle x86_64 (XPS 9370, Inspiron 15 7579)
alciregi KVM, x86_64, bios
bcgates KVM
chrimage Lenovo Ideapad Flex 5, AMD Ryzen 4500U
christian VirtualBox
cmurf mbp82,hpspectre
dcavalca VMware x86_64 bios
decathorpe KVM
devil24g KVM
gamma VBox
ifel KVM
ifel x86_64
kanderson KVM
kparal virt-manager
lruzicka KVM, x86_64, bios based
mberry [1] [2] 1. Works as expected.
2. Sound is working as expected.
mberry x86_64 [1] 1. Automount of drives works as expected.
mzumquadrat KVM [1] [2] 1. Only tested with USB since my Notebook does not have a CD drive
2. Not able to test since i updated the system via CLI in an earlier step
nasirhm KVM/QEMU x86_64 on Lenovo Thinkpad X1 Carbon
nielsenb Compaq 8510w Intel T9300 AMD RV630 BIOS
steelcowboy HP EliteBook 735 G6, AMD Ryzen Pro 3700U [1] 1. I think Gutenprint should support my Epson Stylus NX625, but it couldn't find the driver in the software center and failed to add
sumantrom KVM
tflink x86_64 hardware
thynkon KVM, x86_64
thynkon KVM, x86_64, KDE Plasma
yang KVM
yanqiyu X86_64,KVM and baremetal

Modularity

Username Profile Module List Enable/disable module Install Module Update without repos Update Module Comments
Enter result Enter result Enter result Enter result Enter result
FlexibleToast KVM Proxmox and oVirt
bcgates KVM [1] 1. I had to install ruby using "sudo dnf module install ruby/default"
christian VirtualBox [1] 1. tested with `sudo dnf module install ruby:master/default`
lruzicka KVM, x86_64, bios based [1] 1. The dnf works ok, but some modules have broken dependencies and cannot be installed (avocado).
mzumquadrat KVM [1] [2] 1. Tested with cri-o
2. Used cri-o with default profile
sumantrom KVM + testdayiso without luks,guided automatic partioning [1] [2] 1. Enabled and disabled nodejs:14
2. Works fine tested with mariadb:10.4
sumantrom baremetal t580
yang KVM

Guided storage configuration

Username Profile Guided Empty Guided Delete All Guided Multi Select Guided Delete Partial Guided free space Guided encrypted Guided Multi Empty All Guided Shrink Comments
Enter result Enter result Enter result Enter result Enter result Enter result Enter result Enter result
FlexibleToast KVM Proxmox and oVirt
FlexibleToast KVM oVirt
bryanquigley HP Chromebook 11 G4 running mrchromebox.tech coreboot - EUFI, 16 GB eMMC
christian VirtualBox
kartikay1506
kartikay1506 Virtualbox
kparal virt-manager [1] [2] 1. #1855174, Crash in certain situations. Also, do we want to set up btrfs raid automatically, do we trust it enough?
2. #1855292,
lruzicka KVM, x86_64, bios based
mzumquadrat KVM
nielsenb Compaq 8510w Intel T9300 AMD RV630 BIOS
steelcowboy HP EliteBook 735 G6, AMD Ryzen Pro 3700U

Exploratory

Username Profile Experimental Comments
Enter result
Schykle x86_64 (XPS 9370, Inspiron 15 7579) [1] 1. Successfully ran scrubs, defragments (including enabling/disabling compression on the filesystem as well as changing compression types), and balance
decathorpe KVM [1] 1. btrfs balance, scrub, defragment, and subvolume/snapshot create, list, and delete worked out of the box.
devil24g KVM [1] 1. [Wed Jul 8 15:04:19 2020] ====================================================== [Wed Jul 8 15:04:19 2020] WARNING: possible circular locking dependency detected [Wed Jul 8 15:04:19 2020] 5.8.0-0.rc3.20200701git7c30b859a947.1.fc33.x86_64 #1 Not tainted [Wed Jul 8 15:04:19 2020] ------------------------------------------------------ [Wed Jul 8 15:04:19 2020] systemd-journal/525 is trying to acquire lock: [Wed Jul 8 15:04:19 2020] ffffa051f4a14db0 (&fs_info->reloc_mutex){+.+.}-{3:3}, at: btrfs_record_root_in_trans+0x44/0x70 [btrfs] [Wed Jul 8 15:04:19 2020] but task is already holding lock: [Wed Jul 8 15:04:19 2020] ffffa051f2c6f598 (sb_pagefaults){.+.+}-{0:0}, at: btrfs_page_mkwrite+0x59/0x560 [btrfs]
psimonyi KVM/QEMU [1] 1. #1856048, blivet-gui can create subvolumes, but can't display existing ones
pwhalen KVM, AArch64 Host [1] 1. Used an AArch64 disk image for testing - https://pwhalen.fedorapeople.org/Fedora-Workstation-Rawhide-Btrfs-AArch64/Fedora-Workstation-Rawhide-20200706-btrfs.raw.xz
sumantrom baremetal t580 [1] 1. Tried dual booting, first installing the Btrfs test day iso and then installed a regular F32 and grub stopped showing the btrfs F33 after install of regular F32. Both the images were written to a flash drive by FMW
Wiki Metadata