All of lore.kernel.org
 help / color / mirror / Atom feed
From: Animesh Singh <animeshs@gmail.com>
To: linux-poweredge@dell.com
Cc: linux-scsi@vger.kernel.org
Subject: SCSI controller issue.
Date: Wed, 20 Oct 2004 14:04:15 +0530	[thread overview]
Message-ID: <e8fef13b041020013424f5b018@mail.gmail.com> (raw)
In-Reply-To: <e8fef13b041020013136005fe5@mail.gmail.com>

Afternoon,

I am using PERC 4/D scsi controller card for out Power Vault + RHEL AS
2.1 fro cluster.

1. I got lots of I/O error on filesystem( ext3 ), while using Power
Vault 220s with PERC 3/D scsi controller card.
2. After chaning it to PERC 4/D card am facing following issuse:
    It does not allow me to make more then one LUN on the Power Vault.
    If I have 4 disk in R5 and one HS configured on PV 220s. ( in case
if any disk of R5 fails ) then second node gets different status about
the disk status. i.e on Primary node it shows HS getting in to rebuild
status & over node 2 it gives status of DISK FAIL.)
3. We changed the PERC 3/D to PERC 4/D 'cause of listed reasons:
    It supports 160mpbs, where as PERC 4/D supports 320 mpbs ( which
is the same speed provided by PV Controller.
    SCSI cables from nodes to PV were 10feets long, so we went for
shorter cable.

The issue is that if I take up server live then in case of R5 disk
failure + Primary node failure ( on which service at that time will
run ), then in this case will my secondary node takes up the service
and rebuild the R5 or not?

And the flexbility of having more then one LUN on PERC 3/D is not
support on PERC 4/D SCSI controller card.

Regards,
Animesh.

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

           reply	other threads:[~2004-10-20  8:34 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <e8fef13b041020013136005fe5@mail.gmail.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e8fef13b041020013424f5b018@mail.gmail.com \
    --to=animeshs@gmail.com \
    --cc=linux-poweredge@dell.com \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.