Mailing List
Home
Forum Home
Linux - General Red Hat Linux discussion list
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Installation - Getting started with Red Hat Linux
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
application/x mplayer2 plugin
RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
Command stream end of file while reading
X Windows problem (xauth)
Upgrading openoffice 1 1 rpm
FTP: connection refused
FTP: connection refused
mount: /dev/cdrom: is not a valid block device
Dell Precision 650, RedHat 9, no sound
how to trace the cause resulting in the crash of bind server
Virus on the list
UNINSTALL RPM MYSQL
usb pen drives: mounting as a user
broadcom network interface
make mrproper
sendmail configuration on redhat
Couldn 't open PID file /var/run/named/named pid Permission denied
Promise 378 controller
kernel 2 6 and /dev/sound/mixer not found
Problem using up2date
mrtg step by step howto/configuration for a newbie?
Compiling and Installing Kernel 2 6
Can 't locate module ppp0, can 't locate module ppp compress 21
HOW I CAN MAKE BOOTABLE FLOPPY DISKET
Lotus Notes under Wine
/etc/security/limits conf question
Intel E/1000 driver
Command stream end of file while reading
rpm database corrupt
qla2300 modules
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
md Multipath problem with qla2300

md Multipath problem with qla2300

2005-04-28       - By Tyler Shaw

 Back
Reply:     1     2  

Hello all,

I am running RHEL AS 4.0 with dual qla2342's on a SunFire 40z using the
default qla2300 drivers that come with RHEL 4.  I set up an md multipath
array which works beautifully.  During testing, I have been removing a
single path to test the failover capabilities by shutting down the port on
the switch.  Mdadm detectst that the path is down and marks the device as
faulty.  I get a nice e-mail saying that mdadm detected it as down.

The problem is that right after mdadm has marked the device as faulty, I
re-enable the port and wait to see if it comes back.  I have been waiting
for 30 minutes now and it's still marked as down.  mdadm --monitor --scan -f
and mdmpd are both running and neither are picking up the fact that the
device is back.  Previously I have been able to run mdadm --examine <device>
and have it immediately add the device back in as active.  I'm not sure
where the failing is here.

Mdmpd is supposed to look at /proc/mdstat, but /proc/mdstat continually
shows the device as faulty.  I don't know if the mdadm --monitor has the
functionality of mdmpd to detect a device coming back.  This same
configuration was working under RHEL 3 (but with qlogic drivers), so I'm
wondering if that is where the problem lies, that the RedHat supplied
drivers are not reporting to the kernel that the device is back.

Does anybody have an idea what's going on and how I can get the default
programs to work without having to run my own custom scripts in the event of
a failure?

Thanks,

Tyler


--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@(protected)?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

Earn $52 per hosting referral at Lunarpages.