I've been looking at the various sysctl changes for specific
applications (databases, network intensive apps, etc) that have been
made on the servers I manage. I'm wondering if there is any place that
has information about the performance impact or general effect of
changing any / all of the
On RHEL5 systems, you have to set the SAN-based filesystems with the
_netdev option in the fstab to get the system to boot properly.
Maarten Broekman
From: rhelv5-list-boun...@redhat.com
[mailto:rhelv5-list-boun...@redhat.com] On Behalf Of Arvind Navale
Sent: Wednesday, November 04,
This is in the filesystem metadata. You can see it with 'tune2fs -l
device' for those filesystems supported by tune2fs.
Maarten Broekman
Example:
# /sbin/tune2fs -l /dev/sda6
tune2fs 1.35 (28-Feb-2004)
Filesystem volume name: /
Last mounted on: not available
Filesystem UUID:
We have a Kerberos domain configured for user principals and one thing
we noticed between RHEL5.2 and RHEL5.3 is that the REQUIRES_PWCHANGE
attribute doesn't behave consistently between RHEL versions. On RHEL5.2
if we set the REQUIRES_PWCHANGE on the Kerberos principal, the user is
prompted to
-Original Message-
From: rhelv5-list-boun...@redhat.com
[mailto:rhelv5-list-boun...@redhat.com] On Behalf Of
greg_sw...@aotx.uscourts.gov
Sent: Wednesday, December 17, 2008 11:18 AM
To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list
Cc: Red Hat Enterprise
-Original Message-
From: rhelv5-list-boun...@redhat.com
[mailto:rhelv5-list-boun...@redhat.com] On Behalf Of
Collins, Kevin [BEELINE]
Sent: Wednesday, December 17, 2008 1:25 PM
To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list
Cc: nahant-l...@redhat.com
Another mechanism that allows you to dynamically ignore disks (so you
don't have to explicitly list them in each kickstart file) would be:
%pre
echo bootloader --location=mbr --driveorder=cciss/c0d0
/tmp/bootloader
IGNOREDISK=/tmp/ignoredisk
### Ignore qlogic disks for PHYSICAL
I've had cases where the nostorage option doesn't work properly and
still presents some storage devices to the OS if they don't match
defined drive sizes. Using the ignoredisks directive was the only
reliable way I had to completely ignore the SAN devices when we looked
into it around a year ago.
With LVM2 (RHEL5), if I have multiple systems that see the same LUNs,
how do I stop all the systems from importing / exporting the volume
groups when I issue a vgimport or vgexport on one of the systems?
Configuration:
hostA and hostB see the same SAN LUNs. I've created each LUN as a PV
(Tikanga) discussion mailing-list
Subject: RE: [rhelv5-list] Vgimport / vgexport question
See the man pages for vgcreate and vgchange, and particularly the
options: -c, --clustered.
Kevin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Broekman, Maarten
Of Broekman, Maarten
Sent: Tuesday, October 21, 2008 10:06 AM
To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list
Subject: RE: [rhelv5-list] Vgimport / vgexport question
Doesn't that work only if I'm using RedHat's clustering software?
Maarten Broekman
Email: [EMAIL PROTECTED
the general Best Practices for VCS
apply: use 100-FDX links for Heart-Beat links unless using CFS or Oracle
RAC in which case you'll want 1Gbps links for HB's, use VVR for
geo-clusters, etc...
Vincent
On Thu, 16 Oct 2008, Broekman, Maarten wrote:
Does anyone know of any OS tuning recommendations
Does anyone know of any OS tuning recommendations that should be made
when running VCS on RHEL5? Symantec claims to not have any but they
also suggest getting advice from the OS vendor. Does anyone on this
list use VCS on RHEL5 and, if so, have you found any OS parameters that
should be tuned in
If I understand what you're asking about, RedHat's z channels are what
you're looking for. I'd ask your RedHat tech reps about getting access
to those channels.
Maarten Broekman
Email: [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
I have a fresh build off the RHEL5.2 media (the timestamps on the media
are from April) that I'm trying to update via yum update. Everything
seems to work until it starts trying to resolve dependencies at which
point it starts looping:
-- Running transaction check
--- Package
-9756
Cell: (617) 590-8005
Email: [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Broekman, Maarten
Sent: Tuesday, September 09, 2008 10:16 AM
To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list
Subject: [rhelv5-list] Updating
causes yum to loop
infinitely...
Broekman, Maarten wrote:
Just a followup...
I interrupted the infinitely looping yum update and manually
tried to update:
[root ~]# yum clean all
Loading security plugin
Loading rhnplugin plugin
Cleaning up Everything
[root ~]# yum update glibc glibc
Wishlist -- Less Regressions, more QA
On 2008-08-01, Broekman, Maarten [EMAIL PROTECTED] wrote:
Correct. With the awk patch, both /dev/VG/LV and /dev/mapper/VG-LV
will
work. Without the awk patch, only /dev/VG/LV will work since
/dev/mapper/VG-LV are just links to /dev/VG/LV. Later in the init
]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jan Frode Myklebust
Sent: Friday, August 01, 2008 2:48 AM
To: rhelv5-list@redhat.com
Subject: [rhelv5-list] Re: RHEL6 Wishlist -- Less Regressions, more QA
On 2008-07-31, Broekman, Maarten [EMAIL PROTECTED] wrote:
I
I just checked my own RHEL5 systems (which haven't been able to dump
crashes for different reasons until 5.2), and crashlv works
fine...because it's the longest volume name so it's the one only 1 space
between the LV and VG names.
Just out of curiosity, what does your kdump.conf look like? Are
And you have GATEWAY= in each of the ifcfg-eth# files right? If you
do, then the problem is that when you bring up eth0, the system sets up
the default route to point at the GATEWAY= entry in ifcfg-eth0. Then,
when the system brings up eth2, it sets the default route to point at
the GATEWAY=
, which of course ends
up going out the default interface gateway.
Thanks
Daniel
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Broekman, Maarten
Sent: Thursday, July 24, 2008 12:09 PM
To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list
Subject
I'm looking for advice regarding the multipathing in RHEL5.
Specifically, we use EMC PowerPath currently and I'm looking to evaluate
the native multipathing for a number of reasons. Does anyone have
suggestions, advice, real-life experience where the native multipathing
didn't work properly or
] On Behalf Of Brian Long
Sent: Thursday, October 11, 2007 2:09 PM
To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list
Subject: Re: [rhelv5-list] Ignoring SAN disks during install
On Thu, 2007-10-11 at 12:38 -0400, Broekman, Maarten wrote:
Anyone have much success with the 'ignoredisk
device naming fix...
Broekman, Maarten wrote:
Anyone know what kernel / kexec release has the bugfix mentioned in bz
238124 / bz 228685? I'm trying kernel 2.6.18-36.el5 and kexec
1.101-192.el5 and I'm still seeing issues with cciss devices not
getting
mapped properly from /dev/cciss/c0d0p
Anyone know what kernel / kexec release has the bugfix mentioned in bz
238124 / bz 228685? I'm trying kernel 2.6.18-36.el5 and kexec
1.101-192.el5 and I'm still seeing issues with cciss devices not getting
mapped properly from /dev/cciss/c0d0p# in the real kernel to something
that the crash
) discussion mailing-list
Subject: Re: [rhelv5-list] Help needed with kdump on cciss devices
Broekman, Maarten wrote:
Thanks for the info. Does this also mean that kdump isn't able to
read
/proc/vmcore off of them (cciss partitions) when it's trying to dump?
Reading /proc/vmcore has nothing to do
I'm currently trying to get RHEL5 kdump to work with my cciss-based
internal drives. Every time I point kdump at my /var/crash partition
(ext3 /dev/cciss/c0d0p5), kdump complains that the filesystem isn't
ext2. Anyone had luck getting this to work?
Maarten Broekman
28 matches
Mail list logo
