Bug 1713485

Summary: ext3 partitions get remounted as read-only due to journal error ("journal block not found"..."Detected aborted journal")
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: rawhideCC: airlied, bskeggs, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, robatino, steved, yaneti
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: openqa
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-15 17:50:18 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: 1644939    

Description Adam Williamson 2019-05-23 20:16:43 UTC
Since Fedora-Rawhide-20190517.n.0, when kernel-5.2.0-0.rc0.git6.1.fc31 appeared, openQA ext3 install tests are all failing. Every time, it seems to fail because the ext3 root partition is remounted read-only shortly after it is initially mounted; this obviously breaks the install process. These are the relevant messages from the system journal:

22:05:56,542 INFO kernel:EXT4-fs (vda3): mounting ext3 file system using the ext4 subsystem
22:05:56,549 INFO kernel:EXT4-fs (vda3): mounted filesystem with ordered data mode. Opts: (null)

...

22:06:37,040 CRIT kernel:EXT4-fs error (device vda3): ext4_get_branch:171: inode #8: block 7165: comm jbd2/vda3-8: invalid block
22:06:37,041 ALERT kernel:jbd2_journal_bmap: journal block not found at offset 6156 on vda3-8
22:06:37,041 ERR kernel:Aborting journal on device vda3-8.
22:06:37,046 CRIT kernel:EXT4-fs error (device vda3): ext4_journal_check_start:61: Detected aborted journal
22:06:37,046 CRIT kernel:EXT4-fs (vda3): Remounting filesystem read-only

Proposing as a Final blocker per criterion "The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration" - https://fedoraproject.org/wiki/Fedora_30_Final_Release_Criteria#Disk_layouts

jforbes says this is known upstream, but I want to have a Fedora bug for blocker and tracking purposes.

Comment 1 Adam Williamson 2019-07-15 17:50:18 UTC
Looks like this got fixed in the 20190524.n.1 compose; the test hasn't failed since then. There was a new kernel in that compose, so that checks out, looks like we just got a fix from upstream.