From: Dale Gallagher <foobar@mighty.co.za>
To: linux-lvm@sistina.com
Subject: [linux-lvm] advice sought on setting up new system
Date: Fri Feb 6 07:52:01 2004 [thread overview]
Message-ID: <20040206124830.GA2127@samadhi.local> (raw)
Hi there
I'm new to LVM2 and am considering using it on a production system,
but would welcome advice from experienced users out there, before
I set things up. Your advice and comments would be appreciated.
Details follow.
Summary:
Primary function: mail system (pop3,smtp,http)
Scalable to 10's of thousands (and hopefully millions) of users ;-)
Applications: qmail, PostgreSQL, djbdns
Current system:
1GB RAM
4x U320 15k SCSI 72GB disks in hardware RAID1+0
All functions running on same host.
Future system to include external drive cage(s) and splitting of
functions onto separate hosts (DB/mail/DNS). The external drive
cage(s) to be used for mail storage. qmail uses maildir, as opposed
to mbox delivery, so each message is a separate file... this means
I require performance for a vastly greater number of smaller files
as opposed to a single mbox file per user. Another consideration is
a popular belief that mounting /var/qmail/queue with the sync option
set, or manually invoking sync() improves the queue's robustness
(that's another story).
At the moment the box has:
/ 520MB ext3
/boot 32MB ext3
free +/-130GB LVM
There's a swap partition, but otherwise the rest is available. I'm
considering something approximating the following.
/ 520MB ext3
/boot 32MB ext3
/usr 512MB LVM/ext3
/var 1GB LVM/ext3
/var/lib/pgsql 512MB LVM/ext3
/var/qmail/queue 512MB LVM/ext3 sync
/home 1GB LVM/ext3
/home/mail 127GB+ LVM/ext3
All the file systems on LVs may require expansion/contraction as the
system grows, so I'd like as flexible a setup as possible. The qmail
queue should probably be larger, rather than smaller, so that expansion
doesn't adversely affect performance. What about adding swap space?
What size should the various PEs be, linear/striped?... what other
configurable LVM settings would suit this setup etc. I'm a complete
newbie as far as LVM is concerned, so need valuable pointers.
The primary goal here is for flexibility and I/O performance - the
hardware RAID takes care of availability/redundancy, together with
backup media.
Thanks in advance
Dale
next reply other threads:[~2004-02-06 7:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 7:52 Dale Gallagher [this message]
2004-02-06 15:14 ` [linux-lvm] advice sought on setting up new system Ken Fuchs
2004-02-11 18:57 ` Dale Gallagher
2004-02-12 15:41 ` Ken Fuchs
2004-02-13 8:30 ` Joe Thornber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040206124830.GA2127@samadhi.local \
--to=foobar@mighty.co.za \
--cc=linux-lvm@sistina.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.