On Sat, Jul 06, 2013 at 01:28:28AM +1000, Joel Sing wrote: > On Thu, 4 Jul 2013, Jiri B wrote: > > On Thu, Jul 04, 2013 at 02:33:51AM +1000, Joel Sing wrote: > > > [...snip...] FWIW one of my servers (handles mail, etc) is a Sun Fire > > > V210 (sparc64) machine with 2x1GHz CPU, 2GB RAM and a pair of SCSI drives > > > - it runs perfectly well in a similar CRYPTO on RAID 1 configuration. > > > That said, you'd be best to set it up and measure the performance to > > > ensure it will meet your needs. > > > > I'm confused. Is it possible to have RAID1 and CRYPTO on top of that as > > boot device? It did not work for me... > > No, that will not work since the boot loader will not know how to handle the > nested volumes - the OP said:
Thanks for clarifying. > > I'm planning to use 3 x 1TB drives in RAID 1. No FDE since > > "availability" involves the possibility of unattended booting; like > > after a power outage while being abroad/out of town, in which case I'd > > have to ssh in to the box and bioctl(8) the encrypted volume. > > And that will work, since you boot off RAID 1 and then bring up a CRYPTO > volume manually. Once we do stacked properly we should have RAID1C and you > would be able to boot from that... Perhaps a long shot, but would it be very wrong to assume that such a future boot loader would know how to handle *already existing* nested volumes? Like, if I prepare a RAID1C already partitioned for (or with room left for) the OS, but run the OS from a standalone disk while we wait for a boot loader that does stacking properly? (Given the amount of time to copy a terabyte or two of data, I would certainly be willing to give it a shot. No guarantees expected, of course..) Cheers, Erling
