[Bug 205668] [ext2fs] [patch] cannot mount EXT4 filesystems which weren't cleanly unmounted
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Dec 28 16:06:01 UTC 2015
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205668
Bug ID: 205668
Summary: [ext2fs] [patch] cannot mount EXT4 filesystems which
weren't cleanly unmounted
Product: Base System
Version: 11.0-CURRENT
Hardware: Any
OS: Any
Status: New
Keywords: patch
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: freebsd-bugs at FreeBSD.org
Reporter: damjan.jov at gmail.com
CC: freebsd-fs at FreeBSD.org
Created attachment 164769
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=164769&action=edit
Patch to add support for the EXT2F_INCOMPAT_RECOVER flag
If a disk with the EXT4 filesystem wasn't cleanly unmounted, it will have the
EXT2F_INCOMPAT_RECOVER flag set on its feature flags, visible as
"needs_recovery" in the "Filesystem features" of "tune2fs -l /dev/<disk>".
Our ext2fs module doesn't know about this flag, and ends up treating a disk in
this state as having unsupported features, logging the inappropriate and
confusing message:
WARNING: mount of <disk> denied due to unsupported optional features
to dmesg and unable to mount it until fsck.ext4 even if mounting read-only or
forced.
My attached patch adds support for this flag and treats it as supported,
warning if the filesystem wasn't cleanly unmounted like it already does with
the other 2 ways of marking it as such.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list