Discuss

discuss@lists.centos.org

34758 discussions

RAID support in kernel?
by Michael Klinosky 31 Jan '11

31 Jan '11

Hello. I'm setting up a computer that will run 'CentOS 6 server'. The MB is an Asus with a hw raid controller (Promise PDC-20276), which I want to use in RAID-1 mode. I noted (from a MB website) that it also needs a driver - which is probably why it's called a 'fakeraid'. So, I've been trying to determine if any recent kernels support this chip. Using google.com/linux, I found lots of hits dating about 2002 - 04, and referencing the 2.4 kernel (which had the driver compiled into it). But, nothing newer. I checked kernel.org and kernelnewbies.org - I see that raid-1 is supported. But, I can't find any reference to this chip. How can I find out what drivers are compiled into a given kernel? Or, basically what hardware a given kernel supports?

6 9

Re: [CentOS] Ext4 on CentOS 5.5 x64
by cpolish＠surewest.net 31 Jan '11

31 Jan '11

Sorin Srbu wrote: <snip> > Anyway, I get a bad block message when running fsck, and am not sure > whether this is a interface problem between the chair and the monitor or > something with the tech preview. <snip> Having just live through this issue, I recommend you run the extended (long) SMART test on all your drives and check the reports. The relevant package to install is smartmontools. It's worth investing a little time in setting up the package. I ended up with this incantation in /etc/smartd.conf : /dev/hda -T normal -p -a -o on -S on -s (S/../.././02|L/../../6/03) -m root@localhost To execute the extended tests (doesn't mess with your data): # smartctl --test=long /dev/hda To view the test results about 80 minutes later: # smartctl --log=selftest /dev/hda and so on. -- Charles Polisher

3 3

RHEL-6 vs. CentOS-5.5 (was: Static assignment of SCSI device names?)
by Chuck Munro 30 Jan '11

30 Jan '11

Hello list members, My adventure into udev rules has taken an interesting turn. I did discover a stupid error in the way I was attempting to assign static disk device names on CentOS-5.5, so that's out of the way. But in the process of exploring, I installed a trial copy of RHEL-6 on the new machine to see if anything had changed (since I intend this box to run CentOS-6 anyway). Lots of differences, and it's obvious that RedHat does things a bit differently here and there. My focus has been on figuring out how best to solve my udev challenge, and I found that tools like 'scsi_id' and udev admin/test commands have changed. The udev rules themselves seem to be the same. Regarding networking, all of my 'ifcfg-*' files from CentOS-5.5 worked well, including bridging for KVM. Of course, one of the first things I did was remove that atrocious NetworkManager package ... it needs to be rewritten to make it a *lot* more intuitive. RedHat uses it during installation to manually configure the NICs, which I think is a mistake. I much prefer the way CentOS anaconda has done it so far, as a separate install menu form. The performance of the machine seemed to be better with the newer kernel, which is encouraging. I suspect we can look forward to a number of improvements. I've just managed to scratch the surface. I do expect there may be a few challenges for those of us upgrading a system from 5.x to 6, where some user-written admin scripts could break depending on the system commands they use. I look forward to CentOS-6 and all the goodies we can expect, and I'm quite happy to wait until the CentOS crew does their thing before releasing it ... they deserve a lot of credit for doing a thorough job all these years. Chuck

4 3

py-yaml complaints from yum
by Tim Dunphy 30 Jan '11

30 Jan '11

hello list!! I'm having a curious issue.. if I type yum update -y the system complains of a PyYAML dependency: --> Finished Dependency Resolution PyYAML-3.08-4.el5.x86_64 from installed has depsolving problems --> Missing Dependency: libyaml-0.so.1()(64bit) is needed by package PyYAML-3.08-4.el5.x86_64 (installed) Error: Missing Dependency: libyaml-0.so.1()(64bit) is needed by package PyYAML-3.08-4.el5.x86_64 (installed) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest if I do yum whatprovides "*/libyaml-0.so.1" this is what I get back: [root@VIRTCENT14:~] #yum whatprovides "*/libyaml-0.so.1" Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * addons: mirror.cogentco.com * base: hpc.arc.georgetown.edu * centosplus: mirror.steadfast.net * contrib: hpc.arc.georgetown.edu * epel: mirror.seas.harvard.edu * extras: mirror.atlanticmetro.net * remi: rpms.famillecollet.com * rpmforge: fr2.rpmfind.net * updates: mirror.ash.fastserv.com libyaml-0.1.2-3.el5.i386 : YAML 1.1 parser and emitter written in C Repo : epel Matched from: Filename : /usr/lib/libyaml-0.so.1 libyaml-0.1.2-3.el5.x86_64 : YAML 1.1 parser and emitter written in C Repo : epel Matched from: Filename : /usr/lib64/libyaml-0.so.1 libyaml-0.1.2-3.el5.x86_64 : YAML 1.1 parser and emitter written in C Repo : installed Matched from: Filename : /usr/lib64/libyaml-0.so.1 but it looks like /usr/lib64/libyaml-0.so.1 is already installed on this system. [root@VIRTCENT14:~] #ls -l /usr/lib64/libyaml-0.so.1 lrwxrwxrwx 1 root root 18 Dec 19 22:46 /usr/lib64/libyaml-0.so.1 -> libyaml-0.so.1.1.0 So what's yum complaining about here, and may I have some advice on how to correct this error? thanks CentOS list! You have a history of awesomeness which I respect. -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

2 1

Amazon EC2 - building a minimal centOS ebs bootable image
by Sanjay Arora 29 Jan '11

29 Jan '11

Hello Looking to build CentOS based micro EC2 instance bootable from Amazon EBS. Want that the image be minimal, so that I can add only the rpms I want. Despite looking could not find a way to import a CentOS image from scratch or an existing minimal CentOS image that is bootable from EBS. My server must must persist, as I cannot handle issues with a dynamic server, so I want to use a server that can boot from EBS. Am a EC2 newbie and a follow the instructions kind of a Sys Admin ;-) Please guide me to links, howtos and give experienced advice, in general. With best regards. Sanjay.

6 11

httpd LDAP auth module
by Carlos S 29 Jan '11

29 Jan '11

Hi, I am looking at LDAP module for Apache httpd for authentication. The 'yum install' gives me 'mod_authz_ldap.i386 0:0.26-9.el5_5.1', whereas on Apache documentation site I find mod_authNz_ldap module. Both modules appear to be different looking at available directives. Any clues or suggestions on which module should be used? Where can I find documentation for mod_authz_ldap? -- CS.

4 7

offsite encrypted backups?
by Eero Volotinen 29 Jan '11

29 Jan '11

Hi List, Any idea for remote encrypted backup system? files must be encrypted on local side ? duplicity? any better ideas? -- Eero

6 6

centos 5.5: iptables: module recent
by Helmut Drodofsky 29 Jan '11

29 Jan '11

Hello, I have well performing iptables in centos 5.2 and 5.3 : -A INPUT -m state --state NEW -m recent --update --seconds 60 --hitcount 1000 -p tcp --dport 25 -j LOG --log-prefix "FW DROP IP Flood: " Centos 5.5, updated today: Without -hitcount : iptables accept the line Including -hitcount : iptables brings an error message: Applying iptables firewall rules: iptables-restore: line 47 failed [FAILED] The Line Number is always the number of the COMMIT statement. Not the line number of the statement with the recent module. So I think, iptables is missing something, What? When I add the line interactive, the result is [root@host sysconfig]# iptables -A INPUT -m state --state NEW -m recent --update --seconds 60 --hitcount 1000 -p tcp --dport 25 -j LOG --log-prefix "FW DROP IP Flood: " iptables: Unknown error 18446744073709551615 The man page describes the parameter: [!] --seconds seconds This option must be used in conjunction with one of --rcheck or --update. When used, this will narrow the match to only happen when the address is in the list and was seen within the last given number of seconds. [!] --hitcount hits This option must be used in conjunction with one of --rcheck or --update. When used, this will narrow the match to only happen when the address is in the list and packets had been received greater than or equal to the given value. This option may be used along with --seconds to create an even nar- rower match requiring a certain number of hits within a specific time frame. Without -hitcount the rule is worthless. Suggestions? Many Thanks Helmut

3 4

Cold install kernel .config file
by Tom G Murphy 29 Jan '11

29 Jan '11

Convey uses a highly modified CentOS kernel to work with our attach coprocessor. Currently to setup a system for delivery we do a cold install using a "stock" CentOS cold install using kickstart. During that cold install we lay down our modified kernel and reboot the system with that kernel. After the reboot we are able to access the coprocessor management processor and down load updated firmware then reboot the system to have a completed install. My goal is to be able to boot a "modified" kernel on the cold install step so we can download the firmware updates and eliminate the second boot. I have tried using using the bzImage generated from the modified kernel build but that kernel fails to be able to load the kickstart file :-( I have done searches trying to find the .config file used to build the kernel booted during cold install but have had no luck. I am guessing I have either have too much or too little included in the kernel. I tried to make sure everything I thought was needed were not modules but included in the kernel. Does anyone have any suggestions? --- Tom Murphy Platform Support Convey Computer 1-866-338-1768 tmurphy(a)conveycomputer.com Support Site: http://conveysupport.com/ Support Ticket : http://rt.conveysupport.com/

5 6

Re: [CentOS] Static assignment of SCSI device names?
by Chuck Munro 29 Jan '11

29 Jan '11

> Les Mikesell kindly wrote: >> > >> > Identifying drives by their ID string (which includes the drive's serial >> > number) and assigning names in the rules works ok. BUT, what happens >> > when I have to swap out a failed drive? The serial number (and possibly >> > model number) changes, and the udev assignment should fail, probably >> > assigning an unexpected /dev/sd? name. RAID rebuild would choke until I >> > change the MD device assignment. > If you can figure things out for the initial md device creation, > subsequent assembly uses the uuid to match up the members and doesn't > care if the disks have been moved around either physically or by > detection order. And if you are hot-swapping drives and rebuilding > manually, you should be able to find the just-assigned name with 'dmesg'. > That's how I've been doing it with the two RAID-6 servers I have now, but in my advanced age I'm getting lazy. I did figure out how to tag the drive by path using the '-i' option to scsi_id and filtering by a "RESULT==<path> *" expression. However, something has gone very much astray, because now the rules don't do anything ... the system assigns names in the order scanned despite having added the udev rules before the default '50-udev.rules' is executed. I'm a bit mystified by this. Before I started messing around, filtering by drive id string did work, now it doesn't. Is there a small database somewhere I need to trash? Mike's suggestion is intriguing and makes me wonder if I can manually label a replacement drive with the same UUID as the failed one (assuming I keep records, of course). Since all drives in the array are partitioned exactly the same way, I can have one or two spares on the shelf pre-partitioned, ready to be given a UUID. I don't plan to hot swap. Still, I'd love to be able to use udev rules to assign names, if only to make life easier ... inquiring minds need to know why I suddenly can't get any rules to work. Maybe I need to re-install. I have just downloaded a trial version of RHEL-6 which I should try, to see if it handles this stuff more gracefully. It'll do for experimentation until CentOS-6 arrives. Chuck

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss