[EMAIL PROTECTED] said:
For direct-attached storage, you should quiesce the device by ensuring that
any filesystems accessing it are unmounted, and then I believe you can just
yank it.
I was thinking about our current practices for SVM- or ZFS-mirrored
filesystems on direct-attached drives
Hello Andy,
Tuesday, February 26, 2008, 6:12:35 PM, you wrote:
AL On Feb 26, 2008, at 11:00 AM, Cyril Plisko wrote:
On Tue, Feb 26, 2008 at 5:50 PM, Robert Milkowski
[EMAIL PROTECTED] wrote:
CP Robert,
CP fcinfo works for me :
What HBA have you got?
qus12:/root# fcinfo hba-port
HBA
Hello James,
Tuesday, February 26, 2008, 11:27:56 PM, you wrote:
JCM But that doesn't help Robert much, or anybody else who wants
JCM to be able to get the info without having to learn any mdb-fu.
prtconv/mdb is good enough workaround.
JCM It shouldn't be too hard to hack up a utility to
Marion Hakanson [EMAIL PROTECTED] wrote:
Also:
cfgadm -al -o show_SCSI_LUN
It should list the LUN's on all controllers (paths) available.
[EMAIL PROTECTED] said:
That option only works for FC-attached devices, as detailed in the
cfgadm_fp(1M) manpage.
Sorry, I misremembered. For
On Wed, 27 Feb 2008 14:09:49 -0800
Marion Hakanson [EMAIL PROTECTED] wrote:
Marion Hakanson [EMAIL PROTECTED] wrote:
Also:
cfgadm -al -o show_SCSI_LUN
It should list the LUN's on all controllers (paths) available.
[EMAIL PROTECTED] said:
That option only works for FC-attached
[EMAIL PROTECTED] said:
The other thing you need to remember is that when MPxIO is *enabled* for
mpt-attached devices, then none of those devices show up in cfgadm output.
Ah, that explains why the campers are unhappy. Add me to that list, then.
It must be tough to generalize MPxIO beyond
Robert Milkowski wrote:
Hello James,
Tuesday, February 26, 2008, 11:27:56 PM, you wrote:
JCM But that doesn't help Robert much, or anybody else who wants
JCM to be able to get the info without having to learn any mdb-fu.
prtconv/mdb is good enough workaround.
JCM It shouldn't be too
On Wed, 27 Feb 2008 19:14:49 -0800
Marion Hakanson [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] said:
The other thing you need to remember is that when MPxIO is
*enabled* for mpt-attached devices, then none of those devices show
up in cfgadm output.
Ah, that explains why the campers are
On Tue, Feb 26, 2008 at 4:22 PM, Robert Milkowski [EMAIL PROTECTED] wrote:
Hello storage-discuss,
Once one enabled MPxIO and did devfsadm -C so stmsboot -L won't work
- how can one get LUN number for a given MPxIO device?
fcinfo doesn't work, mpathadm doesn't provide LUN and/or TARGET
On Tue, Feb 26, 2008 at 5:50 PM, Robert Milkowski [EMAIL PROTECTED] wrote:
CP Robert,
CP fcinfo works for me :
What HBA have you got?
qus12:/root# fcinfo hba-port
HBA Port WWN: 21e08b873d15
OS Device Name: /dev/cfg/c2
Manufacturer: QLogic Corp.
Model: QLE2462
On Feb 26, 2008, at 11:00 AM, Cyril Plisko wrote:
On Tue, Feb 26, 2008 at 5:50 PM, Robert Milkowski
[EMAIL PROTECTED] wrote:
CP Robert,
CP fcinfo works for me :
What HBA have you got?
qus12:/root# fcinfo hba-port
HBA Port WWN: 21e08b873d15
OS Device Name: /dev/cfg/c2
With S10U4+patches, PCIe SAS card, I get:
SAS ?! Can this be a problem ? AFAIK, fcinfo looks
specifically for FC HBA. (In fact it uses
libHBAAPI,
which routes the actual call via /etc/hba.conf)
Odds are that your HBA does not provide a library
for libHBAAPI.
That is correct. I'm
David Hollister wrote:
With S10U4+patches, PCIe SAS card, I get:
SAS ?! Can this be a problem ? AFAIK, fcinfo looks
specifically for FC HBA. (In fact it uses
libHBAAPI,
which routes the actual call via /etc/hba.conf)
Odds are that your HBA does not provide a library
On Wed, 27 Feb 2008 09:27:56 +1000
James C. McPherson [EMAIL PROTECTED] wrote:
On Tue, 26 Feb 2008 15:16:35 -0800
Hyon Kim [EMAIL PROTECTED] wrote:
...
A different LUN number can be assigned through LUN mapping for the
same physical LU when mulitple target ports
exist. The mpathadm could
On Tue, 26 Feb 2008 15:16:35 -0800
Hyon Kim [EMAIL PROTECTED] wrote:
...
A different LUN number can be assigned through LUN mapping for the
same physical LU when mulitple target ports
exist. The mpathadm could show LUN number at path level but we had
left up to transport layer utilities like
[EMAIL PROTECTED] said:
exist. The mpathadm could show LUN number at path level but we had left up
to transport layer utilities like fcinfo for reporting it. There is no such
utility for mpt but as far as LUN number is concerned, you can check
'prtconf -v' output and find lun prop from
On Tue, 26 Feb 2008 16:19:09 -0800
Marion Hakanson [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] said:
exist. The mpathadm could show LUN number at path level but we had
left up to transport layer utilities like fcinfo for reporting it.
There is no such utility for mpt but as far as LUN
17 matches
Mail list logo
