Well if you have hardware raid you have to RAID first anyway, otherwise you can do it in either order...However, I'd probably do RAID first, then LVM, as software raiding a bunch of virtual partitions probably takes a ton of processing power than LVM over software RAID.

As for details...There are plenty of guides for software raid out there. Get that set up, you should have some /dev/md devices afterwards. Then just use the LVM tools to slice up the raid devices instead of the "actual" devices. IE give the LVM tools /dev/mdX instead of /dev/sdX.
Then make sure you are mounting things properly ;)

-Alec Warner

Nick Smith wrote:
how would you go about getting the best of both worlds? raid the disks
then put them in an LVM? do you have any details on that? it sounds
nice.

On 2/21/06, Gustavo Zacarias <[EMAIL PROTECTED]> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nick Smith wrote:


from everything ive read it doesnt look like LVM has any redundancy, i
mean it is nice to be able to hotadd drives to your LV, but i need
redundancy as well, so it looks like raid1 or 5 would be the way to
go, because the backups would get more intensive as the LV grew right?
what if one drive in your LV dies? do you lose everything on the LV?
sorry for my ignorance, but this LVM is all new to me, and im not
finding any clear answers googling on the net...

Well RAID and LVM are two completely different things, i don't know why
you people mix them up.
The best of both worlds is RAID1 or RAID5 + LVM.
RAID0 is basically the same that LVM does and is just concatenation - no
redundancy at all "a big bunch of disks".

- --
Gustavo Zacarias
Gentoo/SPARC monkey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1-ecc0.1.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD+2MBV3G/IBCn/JARAqWfAJ950ZB2Q2EgkVI+q7Z81fDKBqtiOwCfR1QH
u/RK6aywiCbthI+f1+5y7ig=
=MhPZ
-----END PGP SIGNATURE-----
--
[email protected] mailing list





--
Linux, because I'd rather own a free OS than steal one that's not
worth paying for.

--
[email protected] mailing list

Reply via email to