Comment 10 for bug 1462632

Well basically I had an existing Fedora installation, which is now gone..

I would assume ext4 doesn't trigger it because the installer knows what it is. It might have failed to revert my luks/lvm/whateveritwas maybe because it didn't recognize it?

I would have to guess what Fedora set up in detail, so I can't tell you for sure.

Anyway, if you do actually write to disk but revert, I think that's utterly broken too. What if the pc is carelessly shutdown because the user assumes no changes were finalized yet? Give at least some sort of warning popup before you actually touch the disk like the debian text-based installer does before writing and activating the dm-crypt stuff - currently it's really out of the blue.