mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Patterson <andrew.patterson@hp.com>
To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	"scameron@beardog.cca.cpqcorp.net"
	<scameron@beardog.cca.cpqcorp.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: RE: HP (Compaq) Smart Array 5xxx controller SCSI driver
Date: Thu, 24 Jul 2008 13:47:48 -0400	[thread overview]
Message-ID: <1216921668.13842.6.camel@boris.fwe.com> (raw)
In-Reply-To: <0F5B06BAB751E047AB5C87D1F77A778826B3DD7474@GVW0547EXC.americas.hpqcorp.net>

On Thu, 2008-07-24 at 15:00 +0000, Miller, Mike (OS Dev) wrote:
> > > As for the patches I mentioned which were previously ignored for
> > > improving how the current cciss SCSI code handled hot plogging, if
> > > you're curious about that, check here:
> > >
> > > http://marc.info/?l=linux-scsi&m=120213565000426&w=4
> > >
> > > A change like that becomes more important if logical drives are
> > > exposed through the scsi layer.
> >
> > We need to think about the best way to map (expose) logical
> > and physical drivers to SCSI luns. As I wrote before, I'm
> > interested in how HP SCSI driver does.
> 
> We don't neccesarily want or need to expose the physical disks. The
> only exception is disks that are not part of a logical volume. If the
> disks are part of a logical volume but exposed the user may shoot
> themselves in the foot by destroying the firmware metadata.

Exposing the underlying disks can be useful for things such as:

      * Finding out what is in a logical drive.
      * Checking and updating disk firmware.
      * Running smartctrl tests on disks

> -- mikem
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
-- 
Andrew Patterson
Hewlett-Packard


  parent reply	other threads:[~2008-07-25 14:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 17:57 scameron
2008-07-24  1:32 ` FUJITA Tomonori
2008-07-24 13:30   ` scameron
2008-07-24 13:44     ` FUJITA Tomonori
2008-07-24 13:54       ` scameron
2008-07-24 15:00       ` Miller, Mike (OS Dev)
2008-07-24 15:06         ` FUJITA Tomonori
2008-08-07 19:04           ` Miller, Mike (OS Dev)
2008-08-08  1:07             ` FUJITA Tomonori
2008-08-08 15:32               ` Miller, Mike (OS Dev)
2008-07-24 17:47         ` Andrew Patterson [this message]
2008-07-24 16:02       ` scameron
     [not found] <20080722175537.GB8833@beardog.cca.cpqcorp.net>
2008-07-23 15:50 ` scameron
2008-07-24  1:32   ` FUJITA Tomonori

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=1216921668.13842.6.camel@boris.fwe.com \
    --to=andrew.patterson@hp.com \
    --cc=Mike.Miller@hp.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=scameron@beardog.cca.cpqcorp.net \
    /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

all inboxes | Powered by JetHome®