Bug 1829792
Summary: | kernel cannot mount XFS in read-only mode from a read-only backing device | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Zbigniew Jędrzejewski-Szmek <zbyszek> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 32 | CC: | airlied, bskeggs, davide, esandeen, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, masami256, mchehab, mjg59, steved |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-02-11 20:56:25 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: |
Description
Zbigniew Jędrzejewski-Szmek
2020-04-30 11:47:15 UTC
To clarify: ideally, it would be possible to simply mount the file system ro from ro image, especially if it has been cleanly unmounted (which I assume is true in this case, since this is an official Fedora image). If that is not possible, a reasonable error should be printed. FWIW you can do "mount -o ro,norecovery" for a readonly-snapshot device with xfs on it. xfs_freeze puts a dummy transaction in the log to force a log replay to clear out orphan inodes, but this makes a plain RO mount on a RO device fail due to the required recovery. I'd like to get this fixed upstream but for now that's the workaround. (FWIW the kernel message is not an OOPS, it's just a very verbose warning from the block layer) Also, ideally the images such as https://download.fedoraproject.org/pub/fedora/linux/releases/32/Server/aarch64/images/Fedora-Server-32-1.6.aarch64.raw.xz would not be frozen snapshots, but properly unmounted and fully quiesced - that would also avoid this behavior. Anyway, this isn't really a bug per se, xfs requires "mount -o ro,norecovery" on a read-only device with a dirty journal (which is somewhat surprisingly the case with a frozen image) I created https://pagure.io/pungi/issue/1495 against pungi. https://github.com/redhat-imaging/imagefactory/issues/444 against imagefactory. |