Discuss October 2005

discuss@lists.centos.org

266 participants
334 discussions

RE: [CentOS] mdadm quandary
by tagarsi, arun 03 Oct '05

03 Oct '05

Hello, Ok I managed to fix this myself using the mdadm options in /etc/mdadm.conf Many thanks Arun -----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org]On Behalf Of Arun Tagarsi Sent: Sunday, October 02, 2005 1:10 PM To: CentOS mailing list Subject: [CentOS] mdadm quandary Hello, I wonder if has seen a problem of the sorts I am describing as at the moment it is driving me nuts. We have an array of LSI disks (Hardware Raid 5) which are attached to a Linux node. The Node has a LSI929 dual fibre channel card that has a channel attached to controller A and B of the array. So we have a list of devices under /proc/partitions mapping what we are expecting to see , for example the devices /dev/sdd1 (A) and /dev/sdx1 (B ) would form a raid 0 device under linux to make a file system slightly under 1TB. This file system was created using the older mkraid utils at the time but has been in production for over a year. This node and the array unfortunately had a power outage and the resulting problem faced by us is the following. The raid start up fails with as it cannot find a device /dev/sdai1 . This device is not part of the /etc/raidtab but is a normal device defined in the /dev directory. There are no references to the /dev/sdai1 device in /proc/partitions at all . All devices expected as /dev/sdd1 and /dev/sdx1 are listed and show the expected sizes. so I presume these are the only devices that the Linux box would be able to work with. If I run a mdadm --examine of the /dev/sdd1 it shows me that indeed /dev/sdd1 and it is lun 0 of the MD device but it also has references to the /dev/sdai1 device. The mdadm --examine /dev/sdx1 shows up as /dev/sdai1 and is lun 1 of the MD device. This is where I am totally confused and I hope I was able to explain the problem . Is there a way to change the super block from referencing sdai1 to sdx1? without compromising the array . The data on the array we suspect is intact and would take a great deal of time to restore. Thanks for your time. Arun -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.9/116 - Release Date: 9/30/2005 _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

1 0

Yum update slow on CentOS 4.1 x86_64?
by Remco Barendse 03 Oct '05

03 Oct '05

Hi list I have several CentOS 4.1 boxes, but only one is running x86_64 CentOS. yum update on all boxes is really fast, on the x86_64 box it is horribly slow. Even startup and "Setting up Repos" takes minutes to complete. The box is just idling all the time (no load at all) and is connected to an 8 mbit DSL connection. Also the downloading of the headers seems to go very slow, about 1 kb per second or so? I tested the internet connection (did wget on an 700 mb ISO image) which downloaded at near max speed so I am sortof ruling out the connection. Top doesn't show any load when yum is running, nor is anything eating any cpu cycles. Ideas anyone?

2 2

question on firewire support and centosplus
by Joe Landman 02 Oct '05

02 Oct '05

Hi folks: Firewire was not supported in 4.0 due to the upstream provider not including it. Is it in 4.1? Or is it still out of the mainline upstream kernel provider? What about centosplus? Centosplus has been listed as unsupported. I presume this means that they are/were one-off builds with missing functionality (e.g. xfs, etc), and are not updated. Is this the case? I am looking at this for an important server, and I want to make sure that if we switch to the centosplus kernel that we haven't messed up the rest of the package support, or major kernel bugfixes. The reason I am curious about firewire is that I would like to use the firewire interface rather than the USB interface for our backup drives. Its not much faster, just fewer context switches (e.g. lower server load). Thanks. Joe -- Joe Landman landman(a)scalableinformatics.com http://www.scalableinformatics.com

2 2

scsi tape drive problems
by James B. Byrne 02 Oct '05

02 Oct '05

I am experimenting with a scsi2 HP SureStore DAT24 attached as an external device to an Intel P4 system. I am attempting to create a raw disk image of a dds2 tape made on a non linux system. My immediate problem is that I am trying to terminate a dd process and having no luck. dd was invoked thus: dd if=/dev/nst1 of=/tmp/disk.dds2.img bs=512 & pid=$! a ps reveals this: ps PID TTY TIME CMD 1936 pts/0 00:00:00 bash 2034 pts/0 00:00:15 dd 2093 pts/0 00:00:00 ps a call to kill has no apparent effect: kill -s SIGKILL 2034 ps PID TTY TIME CMD 1936 pts/0 00:00:00 bash 2034 pts/0 00:00:18 dd 2100 pts/0 00:00:00 ps and calls to mt show this: mt -f /dev/nst1 status /dev/nst1: Device or resource busy Short of a reboot, how do I get control of the tape drive back? (once I get the drive back I will have a lot of other questions regarding dd.) Regards, Jim -- . *** e-mail is not a secure channel *** mailto:byrnejb.<token>@harte-lyne.ca James B. Byrne Harte & Lyne Limited vox: +1 905 561 1241 9 Brockley Drive fax: +1 905 561 0757 Hamilton, Ontario <token> = hal Canada L8E 3C3

3 2

Can CentOS 4 be installed from CD1 only?
by Morten 02 Oct '05

02 Oct '05

Hi. I'm installing CentOS far from home and forgot the CDs... I don't have time to download all 4, what are my best options? I can download CD 1 and perhaps 2 - is that enough? Is there a way to install directly over the internet from one of the mirrors? Thanks. Morten

3 2

Red Hat Directory Server SRPMs??
by Alberto 02 Oct '05

02 Oct '05

Hi, Red Hat has released RHDS ( Red Hat Director Server, also know as iplanet/netscape directory server before ) as open source project and is included in Fedora Core as Fedora Directory Server. Any one know where can I get SRPMs for RHEL 3/4?? will be them included on CentOS?? Thanks

2 1

Recommendation(s)
by Sam Drinkard 02 Oct '05

02 Oct '05

List, It looks like I may have to drop back to a 32-bit version of the OS due to some non-resolvable library issues for the software I'm attempting to compile, and want to ask, how far back can I go with CentOS where I'd not lose too much functionality of the 4.1 version. Essentially what I need is the equivalent of RHES 3. The other thing I'd thought about would be to install the needed gnu library, but in a non-standard place, like /home/sam or some other user directory. Since the software only needs this at runtime and not during linking, I don't see what It would bother. Given that idea, how would I use RPM to install that library ? I read the man page, but did not seen much option for installing to a non-std location, and not have the system actually "recognize" it as being there. suggestions? -- Snowman

5 19

mdadm quandary
by Arun Tagarsi 02 Oct '05

02 Oct '05

Hello, I wonder if has seen a problem of the sorts I am describing as at the moment it is driving me nuts. We have an array of LSI disks (Hardware Raid 5) which are attached to a Linux node. The Node has a LSI929 dual fibre channel card that has a channel attached to controller A and B of the array. So we have a list of devices under /proc/partitions mapping what we are expecting to see , for example the devices /dev/sdd1 (A) and /dev/sdx1 (B ) would form a raid 0 device under linux to make a file system slightly under 1TB. This file system was created using the older mkraid utils at the time but has been in production for over a year. This node and the array unfortunately had a power outage and the resulting problem faced by us is the following. The raid start up fails with as it cannot find a device /dev/sdai1 . This device is not part of the /etc/raidtab but is a normal device defined in the /dev directory. There are no references to the /dev/sdai1 device in /proc/partitions at all . All devices expected as /dev/sdd1 and /dev/sdx1 are listed and show the expected sizes. so I presume these are the only devices that the Linux box would be able to work with. If I run a mdadm --examine of the /dev/sdd1 it shows me that indeed /dev/sdd1 and it is lun 0 of the MD device but it also has references to the /dev/sdai1 device. The mdadm --examine /dev/sdx1 shows up as /dev/sdai1 and is lun 1 of the MD device. This is where I am totally confused and I hope I was able to explain the problem . Is there a way to change the super block from referencing sdai1 to sdx1? without compromising the array . The data on the array we suspect is intact and would take a great deal of time to restore. Thanks for your time. Arun -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.9/116 - Release Date: 9/30/2005

1 0

Need help on UFS driver
by ijez 02 Oct '05

02 Oct '05

Hi, Does anyone have ufs driver modules for centOS 4.1 kernel 2.6.9-11.EL? I need this modules but don't want to border for recompile my kernel to get just ufs support. Can anyone point me where could I download this modules? Thanks In Advances. Regards, ijez

2 3

RE: [CentOS] SATA RAID Block
by Bowie Bailey 01 Oct '05

01 Oct '05

From: Ed Morrison [mailto:edward.morrison@gmail.com] > > I'm looking to add a sata raid controller to my server, give it a > terabyte of HDs and make a myth backend. I'm having trouble > determining > if this raid block is compatible with linux. Does anyone have any > experience with this item? > > http://www.plinkusa.net/webBP-SATA3141B.htm This is just an SATA backplane and so it shouldn't have any compatibility issues. If you want to do raid, you will still need a raid card to connect to the disks in this enclosure. You will need to check the compatibility of the raid card. The best ones are made by 3ware. There was an extended conversation about them on this list a while back. Check the archives if you're interested. Bowie

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss October 2005