The reason for the behaviour observed below turned out to be that the
device entry in /etc/multipath.conf was inadvertently appended *after* the
devices
section , rather than inside it - so that we had
#devices {
#device {
#blah blah
#} (file has a bunch of
hi all
We have a rh linux server connected to two HP SAN controllers, one an HSV200
(on the way out),
the other an HSV400 (on the way in). (Via a Qlogic HBA).
/etc/multipath.conf contains this :
device
{
vendor (COMPAQ|HP)
product
multipath.conf
contents for some devices (?) - why ?
McCulloch, Alan wrote:
hi all
We have a rh linux server connected to two HP SAN controllers, one an HSV200
(on the way out),
the other an HSV400 (on the way in). (Via a Qlogic HBA).
/etc/multipath.conf contains this :
device
hi All,
thanks for the responses.
After being dropped into the
# Filesystem repair
prompt,
( on account of inode 27344909 has illegal blocks )
following warm reboot (via reboot) after finding (SAN ) filesystem in
read-only
mode yesterday morning (possibly because of HBA fault on SAN) , I
hi All,
A fault on our SAN dropped us down to a read-only filesystem and after reboot,
we have an Unexpected Inconsistency and I am being instructed by the boot to
run fsck manually
without -a or -p (this was after I think processing around 15% of the
filesystem)
The specific message is
hi All,
Re below - thanks for the replies to the fsck question.
I have run fsck -r /data and this eventually completed with several changes
made.
Now I am getting the following error from the qla2xxx driver on boot
.
.
.
qla2xxx :05:0d.0: Mailbox command timeout occured. Scheduling ISP
6 matches
Mail list logo
