Hi, On Thu, Sep 25, 2008 at 06:03:18PM -0700, Robinson, Eric wrote: > Hi all, > > I have a pair of new servers, each with 6x300GB 15K SAS drives > configured as a 1.1TB (usable) RAID5 array. The servers will be a > heartbeat+DRBD active/active cluster, with one server primary for MySQL > and the other server primary for FTP. > > My old servers have about 60GB of MySQL data and 140GB of FTP files. On > the new servers, DRBD will ride on top of LVM. I want to allocate 200GB > for MySQL data as LV01 and 400GB for FTP data as LV02, leaving about > 500GB unallocated and available for future needs. > > Here are my questions:
You'd most probably get more informed public at the drbd forums. What follows are my layman answers. > 1. If I start LV01 at 200GB and LV02 at 400GB, and then later I grow > LV01 by another 200GB, would it be fair to expect performance issues due > to the separation of LV01's PVs on the disk platters? Would it be better > to allocate the maximum expected size up front? I don't think you should worry about these. As for performance, it's probably hard to give a straight answer since quite a few components are combined here. Perhaps the limiting factor is RAID5. It will also depend a lot on the use patterns. I'd also ask the MySQL people how are databases organized and what kind of storage is preferable. > 2. Does DRBD care if, when, or how its backing devices are grown? Can I > issue an lvextend command on an LVM that is being used by DRBD without > expecting any problems? lvextend works on a logical volume level. It shouldn't have anything to do with the drbd. Thanks, Dejan > > > --Eric > > > > My apologies for the following annoying disclaimer. It is added by our > e-mail server... > > > > > > > > Disclaimer - September 25, 2008 > This email and any files transmitted with it are confidential and intended > solely for [EMAIL PROTECTED] If you are not the named addressee you should > not disseminate, distribute, copy or alter this email. Any views or opinions > presented in this email are solely those of the author and might not > represent those of Physician Select Management (PSM) or Physician's Managed > Care (PMC). Warning: Although the message sender has taken reasonable > precautions to ensure no viruses are present in this email, neither PSM nor > PMC can accept responsibility for any loss or damage arising from the use of > this email or attachments. > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
