On Sat, 29 Oct 2016 13:58:22 +0200 Saša Janiška <gour(a)atmarama.com&gt; wrote: May the force be with you. ;-) I don't know about the raid question, since I don't use raid. I think the installer automatically selects lvm if you let it, but I never do. I always use a custom install to pre-created partitions (and never install over the currently working version, to save lots of hassle and headache if problems occur). The upgrade becomes a much more relaxed process when there is a working alternative available. I don't use a /boot under root, and haven't with Fedora, so I'm not sure if that is a problem or not. Until you asked your question, I hadn't even thought about the fact that /boot could be in the / partition, though I knew it. I use a separate 1 G boot partition for each linux OS I have installed. Maybe someone else can speak to this. There must have been a reason lost in the mists of time. And probably inapplicable now, given how much change there has been. Using a custom layout, and not allocating a /boot partition should work for this in the installer, too. I can't see a reason it wouldn't, and if it does you don't have to worry about it.

On 10/29/16 07:58, Saša Janiška wrote: Questions specific to the test release (F25 has not been released yet), should be directed to the fedora-test list. Don't know where you heard that little tidbit. I can tell you that LVM across multiple disks is terrible. When you have a disk die suddenly, all LVs which have PVs on that disk are unrecoverable, UNLESS you are using a redundant raid partition. When using redundant raid, and you loose one disk, you can run in degraded mode until you replaced that failed disk, then you can rebuild the missing portion from the redundant part. Redundant raid is all raids EXCEPT raid-0 which is just striping of the data across multiple disks. All other forms of raid (1, 3, 5, 6, 10) are able to survive a single disk failure and can rebuild when the failed disk is replaced. raid 6 can even survive 2 disk failures!). Probably a more historical artifact these days, but it could come into play if you are using a filesystem that grub2 cannot boot from. -- Kevin J. Cummings kjchome(a)verizon.net cummings(a)kjchome.homeip.net cummings(a)kjc386.framingham.ma.us Registered Linux User #1232 (http://www.linuxcounter.net/)

On 10/29/2016 01:58 PM, Saša Janiška wrote: A separate /boot partition makes the boot process more powerful. For example, you can't encrypt the / filesytem if it has boot inside, as grub would not be able to read the kernel and the initrd. Regards. -- Roberto Ragusa mail at robertoragusa.it

Hi, I'm late to this, but i can't recommend Btrfs multiple device stuff for those unaware of the state. While stable, the problem is it doesn't have any of the notification capabilities as mdadm or lvm raid. Also, it's pretty unsuitable for rootfs because unattended degraded boot isn't possible. So while you're unlikely to lose data, and it will catch and fix even the most trivial, transient corruptions, you definitely need to make sure it fits your use case requirements. Chris Murphy