Just a quick ping to the general m/l.
Is there a SAN expert out there who could spare some time to have a look at this forum post, please?
URL -- http://www.centos.org/modules/newbb/viewtopic.php?topic_id=20273&forum=3...
Alan.
On May 14, 2009, at 6:48 AM, Alan Bartlett ajb.stxsl@googlemail.com wrote:
Just a quick ping to the general m/l.
Is there a SAN expert out there who could spare some time to have a look at this forum post, please?
URL -- http://www.centos.org/modules/newbb/viewtopic.php?topic_id=20273&forum=3...
Doing storage work is a pain, it means you are up in the middle of the night doing all sorts of scary stuff with the company's data.
You are going to have to reboot to see the new size because the partition is in use.
I highly recommend using LVM on the bare SAN volume next time.
-Ross
On Thu, May 14, 2009 at 6:48 AM, Alan Bartlett ajb.stxsl@googlemail.com wrote:
Just a quick ping to the general m/l.
Is there a SAN expert out there who could spare some time to have a look at this forum post, please?
URL -- http://www.centos.org/modules/newbb/viewtopic.php?topic_id=20273&forum=3...
If you unmount the partition, then rescan the scsi bus it'll work. Basically your system won't see the additional space while you're using the partition. if you stop using it (unmount) then you can operate on it and bring it back online.
This is where LVM shines, because you can simply add another lun, add it to your lvm setup, and expand the filesystem on the fly.
Jim Perrin wrote:
This is where LVM shines, because you can simply add another lun, add it to your lvm setup, and expand the filesystem on the fly.
Also the OP should look into thin provisioning software that may be available for his EMC array. In some situations this can eliminate the need for LVM. For me I still use LVM because it helps when detecting what paths to use with MPIO. I often create larger(1-2TB) volumes on the storage array and then create smaller logical volumes in LVM, then when I need to expand I just expand, no need for new LUNs. If your data access patterns don't involve large amounts of writes and then deletes(thin provisioning dedicates storage when it is written to), then you don't need volume management at all the array can do it for you.
Most workloads in my experience are friendly with thin provisioning, some are not. Some vendors have ways to reclaim deleted space as well to put it back into the storage pool(s) for use by other systems.
http://searchstorage.techtarget.com/news/column/0,294698,sid5_gci1134713,00....
nate
Dear all,
I have a mail server based on a CentOS 5.3 machine with postfix.
Most of our users are on LDAP (on localhost) but we also have some local users and we are using PAM for authentication.
Are you running nscd on the server? That should smooth out LDAP blips, though I would disable nscd's dns caching in /etc/nscd.conf
Is postfix configured to talk directly to LDAP ? What does the configuration look like?
nate
We are using nscd with the default configuration. This server also has a web server, will disabling nscd's dns cache have negative impact on the performance in this service (or others)?
Postfix does not talk with LDAP. Here's the configuration file: ---------------- queue_directory = /var/spool/postfix command_directory = /usr/sbin daemon_directory = /usr/libexec/postfix mail_owner = postfix myhostname = mail.astro.up.pt mydomain = astro.up.pt myorigin = $mydomain inet_interfaces = all mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain unknown_local_recipient_reject_code = 550 mynetworks_style = host virtual_alias_domains = vlti.org sp-astronomia.pt virtual_alias_maps = hash:/etc/postfix/virtual, hash:/etc/mailman/virtual-mailman smtp_generic_maps = hash:/etc/postfix/generic canonical_maps = hash:/etc/postfix/canonical alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases alias_database = hash:/etc/aliases recipient_delimiter = + home_mailbox = Maildir/ mailbox_command = /usr/bin/procmail -d ${USER} debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5 sendmail_path = /usr/sbin/sendmail.postfix newaliases_path = /usr/bin/newaliases.postfix mailq_path = /usr/bin/mailq.postfix setgid_group = postdrop
### AMAVIS content_filter = smtp-amavis:[localhost]:10024
### SASL #TLS - SMTP AUTH disable_vrfy_command = yes smtpd_use_tls = yes smtpd_tls_auth_only = yes tls_random_source = dev:/dev/urandom smtpd_tls_cert_file = /etc/pki/tls/certs/mail-chained.pem smtpd_tls_key_file = /etc/pki/tls/private/mail.astro.up.pt.key smtpd_sasl_auth_enable = yes smtpd_sasl_security_options = noanonymous broken_sasl_auth_clients = yes
# Security smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination
# Options message_size_limit = 30960000 smtpd_timeout = 600 -----------------------------
Thanks, Manuel
-
Alan Bartlett -
Jim Perrin -
Karanbir Singh -
Manuel Monteiro -
nate -
Ross Walker