From: Alexei_Roudnev (Alexei_Roudnev_at_exigengroup.com)
Date: Sat Nov 24 2007 - 00:03:38 CET
Message-ID: <071401c82e25$15bee9c0$6401a8c0@alexh> From: "Alexei_Roudnev" <Alexei_Roudnev@exigengroup.com> Date: Fri, 23 Nov 2007 15:03:38 -0800 Subject: [suse-sles-e] SuSe and a big disks (or big lun's)
(After > 2 TB thread)
SuSe require some improvements to deal with big storage volumes (or big ##
of small disks).
(1) Normally, if you use a few drives, you use LVM nd tyou assign the whole
disk to the LVM.
For some reason, yast2 don't allow to run LVM over the disk, but require to
create partition;
moreover, if you added disks into lvm using pv* commands, you still can't
use yast to configure VG groups and LV volumes on it.
(2) Big disks comes from multipath or _disk/by-id_ usually. Yast can't work
with them, and SuSe lvm don't see them by default as well.
(3) evms looks as a very promising lvm replacement, but it never have been
integrated properly (yast,
defaults, heartbeat module).
> On Thursday 22 November 2007 09:53, Joseph Marton wrote:
>> Any storage person will tell you that unless ABSOLUTELY necessary you
>> don't want to use large drives. You are always better off using
>> greater quantities of smaller drives rather than smaller quantities of
>> larger drives. The more spindles you have in your RAID solution, the
>> better.
---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com
This archive was generated by hypermail 2.1.7 : Fri Nov 23 2007 - 13:04:04 CET