Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Derek Engelhaupt <derekengelhaupt@rocketmail.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Autoraid supported?
Date: Thu, 15 Aug 2002 00:18:03 -0600	[thread overview]
Message-ID: <20020815061803.7FFD54829@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Derek Engelhaupt <derekengelhaupt@rocketmail.com> of "Wed, 14 Aug 2002 17:11:33 PDT." <20020815001133.84971.qmail@web12507.mail.yahoo.com>

Derek Engelhaupt wrote:
> Being an HP-UX man I was wondering how Debian handles alternate (pv) links?

YMMV. The dual controller FC10 confused the shit out of the
Emulex lpfc driver. lpfc just doesn't know the FC10 might take
5-10 (or more)  seconds to reassign LUNs from one controller
to the other.  I don't expect much better from the SCSI stack
but it will depend on the interface driver.

...
> Normally on my HP-UX side I would hook up the AutoRAID, do an ioscan
> -f, insf -e, and proceed to pvcreate/vgcreate/lvcreate, etc.  Since
> there is no ioscan in Linux, how can you do a physical scan of the
> hardware?

At boot time, such a scan takes place.
You can look in /proc/scsi/scsi to see which SCSI devices have
been discovered.

> Any hardware diagnostics?  Or if anyone can point me to some
> other online resources that might be helpful, that would be great too. 
> Thanks....

See Debian scsitools and scsiadd packages.
Also learn about mounting file systems by label rather than
by device name

grant

      reply	other threads:[~2002-08-15  6:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-13 13:13 [parisc-linux] RE: question setting up consoles, x and stuff Grant Grundler
2002-08-15  0:11 ` [parisc-linux] Autoraid supported? Derek Engelhaupt
2002-08-15  6:18   ` Grant Grundler [this message]

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=20020815061803.7FFD54829@dsl2.external.hp.com \
    --to=grundler@dsl2.external.hp.com \
    --cc=derekengelhaupt@rocketmail.com \
    --cc=parisc-linux@lists.parisc-linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox