linux-ext4 - Conversion to ext4 renders a filesystem unbootable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <491ec8f2.h+/NctvgrQETYou26OH9qFQ1@Brain>
Date:	Sat, 15 Nov 2008 05:04:50 -0800
From:	bmj001@...imail.com (Bruce Jerrick)
To:	sandeen@...hat.com, linux-ext4@...r.kernel.org
Subject: Conversion to ext4 renders a filesystem unbootable

Despite ext4[dev] support in Fedora 9 and 10, conversion of an ext3 filesystem
to ext4 will render it permanently unbootable (read on; there's a "yes, I know"
down there).

I'm not looking for a rescue (this was all done to an expendable system), and
it appears to be a known "issue", but additional warnings in 'man tune2fs'
(or even in the executable) seem to be warranted.

The scenario was:

On a multi-boot machine with my main system being Fedora 8 (with
kernel-2.6.26.6-49.fc8 and e2fsprogs-1.41.3-2.fc9, so it has ext4dev support),
I "converted" an ext3 filesystem by setting 'test_fs' with tune2fs, then
mounting it (successfully) under the F8 system as type ext4dev.

The converted filesystem contained an F10 installation all on one filesystem,
i.e., no separate /boot .  (I had overlooked the fact that the anaconda
installer doesn't support ext4 on a bootable partition; the goal was just to
make sure I can access F10 ext4 filesystems from the F8 system.)  Later I
discovered that the F10 system wouldn't boot, with a message about
"unsupported features".

Presumably this was because it now uses extents instead of indirect blocks
(after it was ext4, I modified a file on it, so I assume it started
using extents).  The really bad news is that this conversion seems to
be irreversible.  So there should probably be warnings in 'man tune2fs'
similar to those in 'man mkfs.ext4' (and also a warning about rendering a
partition permanently unbootable).

BTW, there's a minor inconsistency in F10 'man mke2fs' (and its hardlink
clones).  In the OPTIONS section, "-O" has "extent" listed, but the example
after "-t fs-type" uses "-O extents" (granted, either form seems to be
accepted).

Similarly, 'tune2fs -l' reports "extent" (in Filesystem features), but
/etc/mke2fs.conf uses "extents" (as a features value).

-- Bruce Jerrick

PS.  If feasible, a two-way ext3 <-> ext4 converter would be nice.
PPS.  Are bootable ext4 partitions in the cards?  (I assume yes.)
PPPS.  Why am I still using F8?  <flame> Because gnome-session/gnome-terminal
 save/restore is (repairably) broken in F9 and gone entirely in F10. </flame>

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html