Bug#418519: Reason for having raw disk as physical volume

2015-01-03 Thread Vincas Dargis
2015.01.03 17:24, Lennart Sorensen wrote: Also there has to be somewhere to install the bootloader, and blockmapping into the filesystem is a very bad idea Uhm, yes, of course. Bootloader is just before /dev/sda1 partition, which may be /boot or a dummy/unused. Everything in /dev/sda raid v

Bug#418519: Reason for having raw disk as physical volume

2015-01-03 Thread Lennart Sorensen
On Sat, Jan 03, 2015 at 09:48:14AM +0200, Vincas Dargis wrote: > With HW Raid, it's exactly what we intended to do: create very small > volume (for Linux point of view it's just /dev/sda) to be as "boot > disk", containing only boot loader (and maybe /boot), which should > not be ever resized or sn

Bug#418519: Reason for having raw disk as physical volume

2015-01-02 Thread Vincas Dargis
2015.01.02 22:13, Geert Stappers wrote: "workaround": use an additional dedicated boot disk[1] With HW Raid, it's exactly what we intended to do: create very small volume (for Linux point of view it's just /dev/sda) to be as "boot disk", containing only boot loader (and maybe /boot), which sh

Bug#418519: Reason for having raw disk as physical volume

2015-01-02 Thread Geert Stappers
When the only disk is "completely LVM", then boot loaders should also have support for it. When the computer is "Only LVM" also. "workaround": use an additional dedicated boot disk[1] Groeten Geert Stappers Note [1] something that bootROM ( "BIOS" ) supports signature.asc Description: Di

Bug#418519: Reason for having raw disk as physical volume

2015-01-02 Thread Vincas Dargis
Hello, I can tell example where having raw disk as PV is handy: using hardware RAID controllers, such as Areca ones. Raid controllers allows you to add new disks to existing raid array. For example, if you have Raid 10 using four 1TB disks, you can add two more disks and increase capacity from 2T