Creating swap on (e)MMC devices (/dev/mmcblk*) is not a good idea, this is both very slow and will thrash/destroy the MMC disk quite quickly if the swap actually gets used.
So IMHO it would be better for anaconda to not create swap at all when doing automatic partitioning on a (e)MMC drive.
You should probably double check this with the ARM folks before implementing this.
I've added Peter Robinson to the Cc. Peter do you have any input on this?
> I've added Peter Robinson to the Cc. Peter do you have any input on this?
Not particularly although we can't currently do much about this from the disk image PoV as it's generated via virtual disks.
The issues are also quite device dependent too.
Device dependent? AFAIK there is no (e)MMC where it is a good idea to put swap on there. Sure some sdcards are worse then others, but AFAIK none are really suitable for swap.
As for the disk images, I guess we could disable creating swap there through kickstart or some such?
(In reply to Hans de Goede from comment #2)
> Device dependent? AFAIK there is no (e)MMC where it is a good idea to put
> swap on there. Sure some sdcards are worse then others, but AFAIK none are
> really suitable for swap.
> As for the disk images, I guess we could disable creating swap there through
> kickstart or some such?
We could but we've had some swap on the disk images now for 6+ years, with no reported issues I'm aware of, and the images are used in a lot of other storage devices as well other than just emmc
Ok, so lets keep the disk-images as is. Still it would be nice if anaconda could not create swap on eMMC disks.
Support for x86 based tablets / 2-in-1s like the Asus T100 Transformer series has improved a lot, so people can now run Fedora on them and creating swap on these devices with (cheap-ish) eMMC disks is a bad idea.
The same goes for a whole lot of ARM devices.