Discuss

discuss@lists.centos.org

34758 discussions

new ssd to play with
by Jerry Geis 08 Sep '11

08 Sep '11

I grabbed a new SSD M4-CT064M4SSD2 from Crucial. I am disappointed. I stuck the unit in an Atom machine (zotac) with CentOS 6 on the disk. It really doesn't "feel" faster than the previous 5400 RPM drive that was in it. The SSD is giving me (in the zotac running centos 6): hdparm -t /dev/sda /dev/sda: Timing buffered disk reads: 298 MB in 3.00 seconds = 99.30 MB/sec The Samsung 5400 RPM disk (in the zotac running Centos 6): hdparm -t /dev/sda /dev/sda: Timing buffered disk reads: 196 MB in 3.01 seconds = 65.02 MB/sec I'm not supper impressed at all. Sure the numbers say its "slightly" better but I don't "feel" it. I was expecting like really noticeable change in application load time or something - but not really. Just wondering... Is there something that has to be done to take advantage of the SSD performance? Thanks, jerry

8 10

CentoOS 6 x86_64 Updates
by Timothy Kesten 08 Sep '11

08 Sep '11

Hi Folks, is it correct that there were for a long time no more updates for CentOS 6 x86_64? I think the last update was offered before more than one month Thx Timothy P.S. sorry for that terrible english :-)

2 1

rsync -x does not do the same on EL 5.6 and 5.7
by Simon Matter 08 Sep '11

08 Sep '11

Hi, We re doing backups of all filesystems to a dedicated server using "rsync -x". Now, the latest CentOS versions (5.7/6.x) come with rsync-3.0.6 instead of rsync-2.x. That's nice but unfortunately it doesn't do the same as 2.x in certain situations. The problem is with the -x option, which does not delete content under a mount point anymore. It was my impression that this is a bug, but I've been told it's a feature. The problem has shown up after I have added a new mount point on a server. I've added a BZ for RedHat and also posted to the rsync list as below: https://bugzilla.redhat.com/show_bug.cgi?id=735981 https://lists.samba.org/archive/rsync/2011-September/026766.html Am I really the only one having problems with the new behaviour? It affects all user running "rsync -x". The problem only shows up after new mount points have been added to a subdirectory which is processed by rsync -x. That may be the reason why not many people relize it. Still, I don't see the logic behind the change which is why I take this here to hear what others think. Thanks, Simon

3 2

new memory not getting regonized
by sylvan.dcunha＠gmail.com 08 Sep '11

08 Sep '11

dear All, I had a Centos 5.5 OS running for about 6 months used as a Xen VM server prfectly running 3 Virtual machines Its a Sun Blade server with 8 core Xeon Proceesor with 32 GB Ram couple of days back I added another 32 gb ram . The bios shows the added ram that is now it shows me 64 GB but the Centos OS just recognizes 32gb only the OS details are: Centos release 5.5 final Kernel 2.6.18-194.32.1.el5xen on an x86_64 now also running uname -a shows me Linux hypervisor2 2.6.18-194.32.1.el5xen #1 SMP Wed Jan 5 18:44:24 EST 2011 x86_64 x86_64 x86_64 GNU/Linux shows that PAE support is not there I do believe that installing kernel PAE with yum should solve the problem but since the server is a online production server just wanted to verify if I would run into some problems apprecite your kinf help and suggestions regards sylvan

7 12

boot problem after disk change on raid1
by Bünyamin İzzet 08 Sep '11

08 Sep '11

Hello, I have two disks sda and sdb. One of the was broken so I have changed the broken disk with a working one. I started the server in rescue mode, and created the partional table, and added all the partitions to the software raid. *I have added the partitions to the RAID, and reboot.* # mdadm /dev/md0 --add /dev/sdb1 # mdadm /dev/md1 --add /dev/sdb2 # mdadm /dev/md2 --add /dev/sdb3 # mdadm /dev/md3 --add /dev/sdb4 *After reboot, server did not boot. So I do the followings:* # mount /dev/md1 /mnt/rescue # mount /dev/md0 /mnt/rescue/boot # mount -o bind /dev /mnt/rescue/dev # mount -o bind /proc /mnt/rescue/proc # mount -o bind /dev/shm /mnt/rescue/dev/shm # mount -o bind /sys /mnt/rescue/sys # chroot /mnt/rescue *I checked the device.map* # cat /boot/grub/device.map (hd0) /dev/sda (hd1) /dev/sdb *And, install the grub.* # grub Probing devices to guess BIOS drives. This may take a long time. GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> root (hd0,0) root (hd0,0) Filesystem type is ext2fs, partition type 0xfd grub> setup (hd0) setup (hd0) Checking if "/boot/grub/stage1" exists... yes Checking if "/boot/grub/stage2" exists... yes Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 15 sectors are embedded. succeeded Running "install /boot/grub/stage1 (hd0) (hd0)1+15 p (hd0,0)/boot/grub/stage2 /boot/grub/grub.conf"... succeeded Done. grub> root (hd1,0) root (hd1,0) Filesystem type is ext2fs, partition type 0xfd grub> setup (hd1) setup (hd1) Checking if "/boot/grub/stage1" exists... yes Checking if "/boot/grub/stage2" exists... yes Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd1)"... 15 sectors are embedded. succeeded Running "install /boot/grub/stage1 (hd1) (hd1)1+15 p (hd1,0)/boot/grub/stage2 /boot/grub/grub.conf"... succeeded Done. grub> quit quit *But it still does not boot. What should I do at this point? What do you suggest?* *Disk informations* # fdisk -l /dev/sd[ab] Disk /dev/sda: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00090dd1 Device Boot Start End Blocks Id System /dev/sda1 * 1 131 1052226 fd Linux raid autodetect /dev/sda2 132 5353 41945715 fd Linux raid autodetect /dev/sda3 5354 96733 734009850 fd Linux raid autodetect /dev/sda4 96734 182401 688128210 fd Linux raid autodetect Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xf5c3aa6a Device Boot Start End Blocks Id System /dev/sdb1 * 1 131 1052226 fd Linux raid autodetect /dev/sdb2 132 5353 41945715 fd Linux raid autodetect /dev/sdb3 5354 96733 734009850 fd Linux raid autodetect /dev/sdb4 96734 182401 688128210 fd Linux raid autodetect *Raid info* # cat /proc/mdstat Personalities : [raid1] md3 : active raid1 sda4[0] sdb4[2] 688128128 blocks [2/1] [U_] resync=DELAYED md2 : active raid1 sda3[0] sdb3[2] 734009728 blocks [2/1] [U_] [>....................] recovery = 1.8% (13651648/734009728) finish=133.5min speed=89915K/sec md1 : active raid1 sdb2[2] sda2[0] 41945600 blocks [2/1] [U_] resync=DELAYED md0 : active raid1 sda1[0] sdb1[1] 1052160 blocks [2/2] [UU] unused devices: <none> *Mount informations* */dev/md0 is mounted /boot /dev/md1 is mounted / **/dev/md2 and /dev/md3 is for backup and some personal data* *Here is the grub.conf* # cat /mnt/rescue/boot/grub/grub.conf timeout 5 default 0 fallback 1 title CentOS (2.6.18-238.19.1.el5) root (hd1,0) kernel /vmlinuz-2.6.18-238.19.1.el5 ro root=/dev/md1 vga=0x317 initrd /initrd-2.6.18-238.19.1.el5.img title CentOS (2.6.18-238.9.1.el5) root (hd0,0) kernel /vmlinuz-2.6.18-238.9.1.el5 ro root=/dev/md1 vga=0x317 initrd /initrd-2.6.18-238.9.1.el5.img title CentOS (2.6.18-194.26.1.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.26.1.el5 ro root=/dev/md1 vga=0x317 initrd /initrd-2.6.18-194.26.1.el5.img title CentOS (2.6.18-194.3.1.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.3.1.el5 ro root=/dev/md1 vga=0x317 initrd /initrd-2.6.18-194.3.1.el5.img title CentOS (2.6.18-164.15.1.el5) root (hd0,0) kernel /vmlinuz-2.6.18-164.15.1.el5 ro root=/dev/md1 vga=0x317 initrd /initrd-2.6.18-164.15.1.el5.img title CentOS Linux (2.6.18-164.11.1.el5) root (hd0,0) kernel /boot/vmlinuz-2.6.18-164.11.1.el5 ro root=/dev/md1 vga=0x317 initrd /boot/initrd-2.6.18-164.11.1.el5.img

2 6

big problem at boot
by Michel Donais 08 Sep '11

08 Sep '11

I restarted the a Centos 5.6 server tonight and I ran in this issue: I was able to boot. Then instead of a normal boot with graphical interface the system requested : 'Enter run level' 'INIT' I typed 5 then I got 'INIT: no more process left in this run level How can I recover from the situation? This is a production system back-up are made but left on the disk and transfer at the end of the day into an other system --- Michel Donais

4 7

CentOS-announce Digest, Vol 79, Issue 3
by centos-announce-request＠centos.org 07 Sep '11

07 Sep '11

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2011:1240: Low CentOS 4 i386 and x86_64 EOL Notice (Tru Huynh) ---------------------------------------------------------------------- Message: 1 Date: Mon, 5 Sep 2011 17:56:00 +0200 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2011:1240: Low CentOS 4 i386 and x86_64 EOL Notice To: centos-announce(a)centos.org Message-ID: <20110905155600.GA19859(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2011:1240: This is the 6-month notification for the End of Life for the CentOS 4 distribution. The upstream provider will discontinue public updates of their EL4 product on February 29th, 2012. The CentOS Project will end support for CentOS 4 on the same date. CentOS 4, as well as all previously released versions of CentOS, will continue to be available in the Centos Vault: http://vault.centos.org/ This CESA includes a new centos-release file that reminds you of the February 29th, 2012 end of life date. Users still running production workloads on CentOS 4 are advised to begin planning the upgrade to CentOS 5 or CentOS 6 before the EOL date. For users who are unable to migrate off the EL 4 code base before its end-of-life date, the upstream provider intends to offer a limited, optional extension program. The CentOS Project recommends that you contact their sales team for a price quote for their extended service if you can not move to a newer code base before February 29th, 2012. -- Tru Huynh (mirrors, CentOS i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

Help with kickstart install
by Jerry Geis 07 Sep '11

07 Sep '11

I am doing a kickstart install for CentOS 6.0 (x86_64 install) The error on screen is "fatal error occurred when install glibc package. Could indicate error with install media" When I looked at the /mnt/sysimage/root/install.log file I see Installing glibc-2.12.-1.7.el6.i686 error unpacking of archive failed on file /lib/ld-2.12.so;4e66d2ec cpio read failed bad file descriptor. (Note I am installing x86-64 but the error is on i686 file) This happens (same error) on 2 machines. AMD box with two 2T hard disks in each box for software RAID. I am using a PXE boot environment. Same environment I use for 5.6 (works fine). My kickstart file has the "repo" line commented out, so my local repo is not interfering. These CentOS 6 files were copied direct from DVD back on Jul 3. How do I find out what is wrong with the file and correct it? These are my files: ls -l /home/silentm/pxe-install/CentOS-6-x86_64/Packages/glibc-* -rw-r--r-- 1 silentm silentm 4466416 Jul 3 00:10 /home/silentm/pxe-install/CentOS-6-x86_64/Packages/glibc-2.12-1.7.el6.i686.rpm -rw-r--r-- 1 silentm silentm 3920028 Jul 3 00:17 /home/silentm/pxe-install/CentOS-6-x86_64/Packages/glibc-2.12-1.7.el6.x86_64.rpm -rw-r--r-- 1 silentm silentm 14815992 Jul 3 00:17 /home/silentm/pxe-install/CentOS-6-x86_64/Packages/glibc-common-2.12-1.7.el6.x86_64.rpm -rw-r--r-- 1 silentm silentm 983372 Jul 3 00:10 /home/silentm/pxe-install/CentOS-6-x86_64/Packages/glibc-devel-2.12-1.7.el6.i686.rpm -rw-r--r-- 1 silentm silentm 982972 Jul 3 00:17 /home/silentm/pxe-install/CentOS-6-x86_64/Packages/glibc-devel-2.12-1.7.el6.x86_64.rpm -rw-r--r-- 1 silentm silentm 605080 Jul 3 00:17 /home/silentm/pxe-install/CentOS-6-x86_64/Packages/glibc-headers-2.12-1.7.el6.x86_64.rpm -rw-r--r-- 1 silentm silentm 1416456 Jul 3 00:17 /home/silentm/pxe-install/CentOS-6-x86_64/Packages/glibc-static-2.12-1.7.el6.x86_64.rpm -rw-r--r-- 1 silentm silentm 157512 Jul 3 00:17 /home/silentm/pxe-install/CentOS-6-x86_64/Packages/glibc-utils-2.12-1.7.el6.x86_64.rpm Thanks, Jerry

3 4

Selinux extra packages and compiled apps
by John Doe 07 Sep '11

07 Sep '11

Hey, I am in the process of trying (and convincing my colleagues) to learn/setup selinux as we switch to 6.0... Quick question: do I really "need" to install the setools/setroubleshoot packages or can I live without them? They want to install 80 packages (gnome stuff, gstreamer, gtk, tcl/tk...) and I would like to avoid installing all sort of graphical tools/libs on my lean servers. Can I just install setools-console by example? Is there a console only equivalent for setroubleshoot? If you know a must-have "selinux for dummies" like howto, apart from Redhat/Fedora doc or CentOS wiki, I am interested!Especially if it covers the case of many non-standard applications (the policy here is to use compiled apaches/php/mencoder/ffmpeg/..., all installed (with their data/logs) in a "/OURDIR" directory (but still use /var/run for the pids and a few others depending on the app), init.d scripts, logrotates, etc... Thx, JD

3 3

pan reader and gmime
by Michael D. Berger 07 Sep '11

07 Sep '11

Running: yum list available | grep -i gmime shows results for CentOS 5, but not for CentOS 6. It seems to be needed by my pan. What should I do? Thanks, Mike.

2 1

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