[OmniOS-discuss] OmniOS-discuss Digest, Vol 21, Issue 3
Hafiz Rafibeyli
rafibeyli at gmail.com
Mon Dec 2 15:07:14 UTC 2013
after my fist post I added 4 x HP SAS 300 GB DP disks to system,actual HP disks quantity 8 now.
AVAILABLE DISK SELECTIONS:
0. c1t5000C50041E9D9A7d0 <SEAGATE-ST33000650SS-0004-2.73TB>
/scsi_vhci/disk at g5000c50041e9d9a7
1. c1t5000C50041F1A5EFd0 <SEAGATE-ST33000650SS-0004-2.73TB>
/scsi_vhci/disk at g5000c50041f1a5ef
2. c1t5000C50055A62F57d0 <SEAGATE-ST33000650SS-0004-2.73TB>
/scsi_vhci/disk at g5000c50055a62f57
3. c1t5000C50055A607E3d0 <SEAGATE-ST33000650SS-0004-2.73TB>
/scsi_vhci/disk at g5000c50055a607e3
4. c1t5000C50055A628EFd0 <SEAGATE-ST33000650SS-0004-2.73TB>
/scsi_vhci/disk at g5000c50055a628ef
5. c1t5000C5004253FF87d0 <SEAGATE-ST33000650SS-0004-2.73TB>
/scsi_vhci/disk at g5000c5004253ff87
6. c1t5000C5005600A6B3d0 <SEAGATE-ST33000650SS-0004-2.73TB>
/scsi_vhci/disk at g5000c5005600a6b3
7. c1t5000C5005600B43Bd0 <SEAGATE-ST33000650SS-0004-2.73TB>
/scsi_vhci/disk at g5000c5005600b43b
8. c1t5001517BB2AFB592d0 <ATA-INTEL SSDSC2CW12-400i-111.79GB>
/scsi_vhci/disk at g5001517bb2afb592
9. c1t5001517BB2747BE7d0 <ATA-SSDSA2SH032G1GN-8860-29.80GB>
/scsi_vhci/disk at g5001517bb2747be7
10. c1t5001517803D007D8d0 <ATA-INTEL SSDSC2CW12-400i-111.79GB>
/scsi_vhci/disk at g5001517803d007d8
11. c1t5001517959627219d0 <ATA-SSDSA2SH032G1GN-8860-29.80GB>
/scsi_vhci/disk at g5001517959627219
12. c3t1d0 <ATA-STECMACH16M-0299 cyl 7785 alt 2 hd 224 sec 56>
/pci at 0,0/pci15d9,100 at 1f,2/disk at 1,0
13. c3t2d0 <ATA-STECMACH16M-0299 cyl 7785 alt 2 hd 224 sec 56>
/pci at 0,0/pci15d9,100 at 1f,2/disk at 2,0
14. c4t5000C5002BD75C05d0 <HP-EG0300FAWHV-HPDE-279.40GB>
/pci at 0,0/pci8086,340e at 7/pci15d9,400 at 0/iport at f/disk at w5000c5002bd75c05,0
15. c4t5000CCA01505A321d0 <HP-DG0300FARVV-HPD8-279.40GB>
/pci at 0,0/pci8086,340e at 7/pci15d9,400 at 0/iport at f/disk at w5000cca01505a321,0
16. c4t5000CCA0150597A5d0 <HP-DG0300FARVV-HPD8-279.40GB>
/pci at 0,0/pci8086,340e at 7/pci15d9,400 at 0/iport at f/disk at w5000cca0150597a5,0
17. c4t500000E1168BB382d0 <HP-EG0300FARTT-HPDA-279.40GB>
/pci at 0,0/pci8086,340e at 7/pci15d9,400 at 0/iport at f/disk at w500000e1168bb382,0
18. c4t500000E11693F232d0 <HP-EG0300FARTT-HPDA-279.40GB>
/pci at 0,0/pci8086,340e at 7/pci15d9,400 at 0/iport at f/disk at w500000e11693f232,0
19. c4t500000E11696D5A2d0 <HP-EG0300FARTT-HPDA-279.40GB>
/pci at 0,0/pci8086,340e at 7/pci15d9,400 at 0/iport at f/disk at w500000e11696d5a2,0
20. c4t500000E116974FB2d0 <HP-EG0300FARTT-HPDA-279.40GB>
/pci at 0,0/pci8086,340e at 7/pci15d9,400 at 0/iport at f/disk at w500000e116974fb2,0
21. c4t50000392C8008B7Ed0 <HP-EG0300FBDSP-HPD1-279.40GB>
/pci at 0,0/pci8086,340e at 7/pci15d9,400 at 0/iport at f/disk at w50000392c8008b7e,0
22. c6t5000C5002BD75C06d0 <HP-EG0300FAWHV-HPDE-279.40GB>
/pci at 0,0/pci8086,3410 at 9/pci15d9,400 at 0/iport at f/disk at w5000c5002bd75c06,0
23. c6t5000CCA01505A322d0 <HP-DG0300FARVV-HPD8-279.40GB>
/pci at 0,0/pci8086,3410 at 9/pci15d9,400 at 0/iport at f/disk at w5000cca01505a322,0
24. c6t5000CCA0150597A6d0 <HP-DG0300FARVV-HPD8-279.40GB>
/pci at 0,0/pci8086,3410 at 9/pci15d9,400 at 0/iport at f/disk at w5000cca0150597a6,0
25. c6t500000E1168BB383d0 <HP-EG0300FARTT-HPDA-279.40GB>
/pci at 0,0/pci8086,3410 at 9/pci15d9,400 at 0/iport at f/disk at w500000e1168bb383,0
26. c6t500000E11693F233d0 <HP-EG0300FARTT-HPDA-279.40GB>
/pci at 0,0/pci8086,3410 at 9/pci15d9,400 at 0/iport at f/disk at w500000e11693f233,0
27. c6t500000E11696D5A3d0 <HP-EG0300FARTT-HPDA-279.40GB>
/pci at 0,0/pci8086,3410 at 9/pci15d9,400 at 0/iport at f/disk at w500000e11696d5a3,0
28. c6t500000E116974FB3d0 <HP-EG0300FARTT-HPDA-279.40GB>
/pci at 0,0/pci8086,3410 at 9/pci15d9,400 at 0/iport at f/disk at w500000e116974fb3,0
29. c6t50000392C8008B7Fd0 <HP-EG0300FBDSP-HPD1-279.40GB>
/pci at 0,0/pci8086,3410 at 9/pci15d9,400 at 0/iport at f/disk at w50000392c8008b7f,0
----- Orijinal Mesaj -----
Kimden: omnios-discuss-request at lists.omniti.com
Kime: omnios-discuss at lists.omniti.com
Gönderilenler: 2 Aralık Pazartesi 2013 16:59:33
Konu: OmniOS-discuss Digest, Vol 21, Issue 3
Send OmniOS-discuss mailing list submissions to
omnios-discuss at lists.omniti.com
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.omniti.com/mailman/listinfo/omnios-discuss
or, via email, send a message with subject or body 'help' to
omnios-discuss-request at lists.omniti.com
You can reach the person managing the list at
omnios-discuss-owner at lists.omniti.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of OmniOS-discuss digest..."
Today's Topics:
1. Re: Re-installing OmniOS after Crash (Eric Sproul)
2. Re: 2x acctual disk quantity (Hafiz Rafibeyli)
3. Re: 2x acctual disk quantity (Saso Kiselkov)
----------------------------------------------------------------------
Message: 1
Date: Mon, 2 Dec 2013 09:53:09 -0500
From: Eric Sproul <esproul at omniti.com>
To: Piers Dawson-Damer <piers at mm.st>
Cc: omnios-discuss <omnios-discuss at lists.omniti.com>
Subject: Re: [OmniOS-discuss] Re-installing OmniOS after Crash
Message-ID:
<CA+QY2RSFCZ=Tu=-6+kFyqxPNvW6Gw=o=L2tc0RBpybBnOgZ7SQ at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Mon, Dec 2, 2013 at 4:26 AM, Piers Dawson-Damer <piers at mm.st> wrote:
> Any update on this error?
This is because we are now signing packages in bloody, in preparation
for the next stable release. If you're reasonably up to date with
r151007 you should already have the OmniTI CA certificate, which is
delivered by pkg:/web/ca-bundle into /etc/ssl/pkg. If you have this,
you should be able to get going by setting your local image's
trust-anchor-directory property so that the OmniTI cert can be
located:
# pkg set-property trust-anchor-directory etc/ssl/pkg
Note that the value is a *relative* path (relative to the root of the
image), so it does not have a leading '/'.
If you do not have the OmniTI CA file, you can update to the version
of ca-bundle that is not signed but *does* have the CA cert:
# pkg update web/ca-bundle at 5.11,5.11-0.151007:20130823T212116Z
This only works if you're already on some version of r151007.
We are in the home stretch for the next release, so those wishing for
the latest bits will have media containing signed packages and any new
pkg images created will have the correct trust-anchor-directory by
default.
Eric
------------------------------
Message: 2
Date: Mon, 2 Dec 2013 16:55:57 +0200 (EET)
From: Hafiz Rafibeyli <rafibeyli at gmail.com>
To: omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] 2x acctual disk quantity
Message-ID:
<1576695750.67960.1385996157208.JavaMail.zimbra at cantekstil.com.tr>
Content-Type: text/plain; charset=windows-1254
Saso is this you are asking for?
id part identify stat diskcap partcap error vendor product sn
c1t5000C50041E9D9A7d0 (!parted) via dd ok 3 TB S:0 H:4 T:0 SEAGATE ST33000650SS Z2934YB40000923
c1t5000C50041F1A5EFd0 (!parted) via dd ok 3 TB S:0 H:4 T:0 SEAGATE ST33000650SS Z2937JC90000924
c1t5000C5004253FF87d0 (!parted) via dd ok 3 TB S:0 H:4 T:0 SEAGATE ST33000650SS Z294403Y0000C25
c1t5000C50055A607E3d0 (!parted) via dd ok 3 TB S:0 H:4 T:0 SEAGATE ST33000650SS Z2955HY80000931
c1t5000C50055A628EFd0 (!parted) via dd ok 3 TB S:0 H:4 T:0 SEAGATE ST33000650SS Z295857E0000931
c1t5000C50055A62F57d0 (!parted) via dd ok 3 TB S:0 H:4 T:0 SEAGATE ST33000650SS Z2957MGA0000931
c1t5000C5005600A6B3d0 (!parted) via dd ok 3 TB S:0 H:4 T:0 SEAGATE ST33000650SS Z2967CNZ0000C32
c1t5000C5005600B43Bd0 (!parted) via dd ok 3 TB S:0 H:4 T:0 SEAGATE ST33000650SS Z2967CF50000C32
c1t5001517803D007D8d0 (!parted) via dd ok 120 GB S:2 H:0 T:0 ATA INTEL SSDSC2CW12 CVCV249102HG120
c1t5001517959627219d0 (!parted) via dd ok 32 GB S:2 H:0 T:0 ATA SSDSA2SH032G1GN CVEM130600KP032
c1t5001517BB2747BE7d0 (!parted) via dd ok 32 GB S:2 H:0 T:0 ATA SSDSA2SH032G1GN CVEM1404005G032
c1t5001517BB2AFB592d0 (!parted) via dd ok 120 GB S:2 H:0 T:0 ATA INTEL SSDSC2CW12 CVCV245100J1120
c3t1d0 (!parted) via dd ok 50 GB S:2 H:0 T:0 ATA STEC MACH16 M STM0001681F1
c3t2d0 (!parted) via dd ok 50 GB S:2 H:0 T:0 ATA STEC MACH16 M STM0001681EE
c4t500000E1168BB382d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0EUJ7104
c4t500000E11693F232d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0EY64104
c4t500000E11696D5A2d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0F12G104
c4t500000E116974FB2d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0F1P5104
c4t50000392C8008B7Ed0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FBDSP EB01PA9013TD103
c4t5000C5002BD75C05d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FAWHV 6SE134XX0000B10
c4t5000CCA0150597A5d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP DG0300FARVV PFV32ANE
c4t5000CCA01505A321d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP DG0300FARVV PFV333BE
c6t500000E1168BB383d0 (!parted) via dd ok 300 GB S:0 H:1 T:0 HP EG0300FARTT D001PAB0EUJ7104
c6t500000E11693F233d0 (!parted) via dd ok 300 GB S:0 H:1 T:0 HP EG0300FARTT D001PAB0EY64104
c6t500000E11696D5A3d0 (!parted) via dd ok 300 GB S:0 H:1 T:0 HP EG0300FARTT D001PAB0F12G104
c6t500000E116974FB3d0 (!parted) via dd ok 300 GB S:0 H:1 T:0 HP EG0300FARTT D001PAB0F1P5104
c6t50000392C8008B7Fd0 (!parted) via dd ok 300 GB S:0 H:1 T:0 HP EG0300FBDSP EB01PA9013TD103
c6t5000C5002BD75C06d0 (!parted) via dd ok 300 GB S:0 H:1 T:0 HP EG0300FAWHV 6SE134XX0000B10
c6t5000CCA0150597A6d0 (!parted) via dd ok 300 GB S:0 H:1 T:0 HP DG0300FARVV PFV32ANE
c6t5000CCA01505A322d0 (!parted) via dd ok 300 GB S:0 H:1 T:0 HP DG0300FARVV PFV333BE
----- Orijinal Mesaj -----
Kimden: omnios-discuss-request at lists.omniti.com
Kime: omnios-discuss at lists.omniti.com
G?nderilenler: 2 Aral?k Pazartesi 2013 16:39:43
Konu: OmniOS-discuss Digest, Vol 21, Issue 2
Send OmniOS-discuss mailing list submissions to
omnios-discuss at lists.omniti.com
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.omniti.com/mailman/listinfo/omnios-discuss
or, via email, send a message with subject or body 'help' to
omnios-discuss-request at lists.omniti.com
You can reach the person managing the list at
omnios-discuss-owner at lists.omniti.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of OmniOS-discuss digest..."
Today's Topics:
1. Re: Re-installing OmniOS after Crash (Piers Dawson-Damer)
2. 2x acctual disk quantity (Hafiz Rafibeyli)
3. Re: 2x acctual disk quantity (Saso Kiselkov)
4. 2x acctual disk quantity (Hafiz Rafibeyli)
5. Re: 2x acctual disk quantity (Saso Kiselkov)
----------------------------------------------------------------------
Message: 1
Date: Mon, 2 Dec 2013 20:26:34 +1100
From: Piers Dawson-Damer <piers at mm.st>
To: omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] Re-installing OmniOS after Crash
Message-ID: <B3452613-0C4C-4CD2-9B32-3358ADB0849F at mm.st>
Content-Type: text/plain; charset="us-ascii"
Any update on this error?
I also cannot update my system. Have tried removing the OmniTi repositories
Piers
SunOS prod 5.11 omnios-ef9657e i86pc i386 i86pc
piers at prod:~$ pfexec pkg update -v
Creating Plan /
pkg update: The certificate which issued this certificate:/C=US/ST=Maryland/O=OmniTI/OU=OmniOS/CN=OmniOS r151007 Release Signing Certificate/emailAddress=omnios-support at omniti.com could not be found. The issuer is:/C=US/ST=Maryland/L=Fulton/O=OmniTI/CN=OmniTI Certificate Authority
The package involved is:pkg://omnios/runtime/python-26@2.6.8,5.11-0.151007:20130926T213513Z
On 27 Oct 2013, at 11:04 pm, Sam M <emunch at utmi.in> wrote:
> Hello all.
>
> After installing napp-it, OmniOS got hosed. Not sure what caused it, probably not napp-it, because I couldn't boot up my system with any of the boot images, including the original.
>
> Now, on a brand new installation, I'm getting the following error -
>
> # pkg update web/ca-bundle pkg
> Creating Plan -
> pkg update: The certificate which issued this certificate:/C=US/ST=Maryland/O=OmniTI/OU=OmniOS/CN=OmniOS r151007 Release Signing Certificate/emailAddress=omnios-support at omniti.com could not be found. The issuer is:/C=US/ST=Maryland/L=Fulton/O=OmniTI/CN=OmniTI Certificate Authority
> The package involved is:pkg://omnios/library/python-2/pybonjour@1.1.1,5.11-0.151007:20130516T114553Z
>
> # uname -a
> SunOS sequoia 5.11 omnios-df542ea i86pc i386 i86pc Solaris
>
> There were no errors earlier after the installation when updating packages.
>
> How can I fix this? Where can I find OmniTI's CA certificate?
>
> TIA.
>
> Sam
>
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omniosce.org/ml-archive/attachments/20131202/8a7686b8/attachment-0001.html>
------------------------------
Message: 2
Date: Mon, 2 Dec 2013 14:08:04 +0200 (EET)
From: Hafiz Rafibeyli <rafibeyli at gmail.com>
To: omnios-discuss <omnios-discuss at lists.omniti.com>
Subject: [OmniOS-discuss] 2x acctual disk quantity
Message-ID:
<147167035.58244.1385986084129.JavaMail.zimbra at cantekstil.com.tr>
Content-Type: text/plain; charset=windows-1254
Saso thank you for your fast reply,
its ok about two ports(sas dp)I know it,
but my question is about ,which disk adresses to use in my zfs mirror or zfs raid config?
in my case:
c4t500000E1168BB382d0
c4t500000E11693F232d0
c4t500000E11696D5A2d0
c4t500000E116974FB2d0
OR
c6t500000E1168BB383d0
c6t500000E11693F233d0
c6t500000E11696D5A3d0
c6t500000E116974FB3d0
If I understand right,when use first adresses I will use 1st controller only,and when use second addresses 2nd controller only?
regards
Hafiz
Message: 6
Date: Sat, 30 Nov 2013 11:26:57 +0000
From: Saso Kiselkov <skiselkov.ml at gmail.com>
To: omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] 2x acctual disk quantity
Message-ID: <5299CB81.7090101 at gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 11/30/13, 9:43 AM, Hafiz Rafibeyli wrote:
> Hello,
>
> After adding 4 SAS dual port disks to my omnios system(omnios-b281e50+napp-it) ,I see number of disks 2x acctual quantity.
>
> I have dual controller backplane(supermicro) and 2 LSI 9211-8i,
>
> There is no any quantity problem with another disks,only with new added HP 300GB SAS DP.
>
>
> c4t500000E1168BB382d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0EUJ7104
> c4t500000E11693F232d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0EY64104
> c4t500000E11696D5A2d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0F12G104
> c4t500000E116974FB2d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0F1P5104
> c6t500000E1168BB383d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0EUJ7104
> c6t500000E11693F233d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0EY64104
> c6t500000E11696D5A3d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0F12G104
> c6t500000E116974FB3d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0F1P5104
Hey Hafiz,
What you're seeing are the two ports of the disks. Using "mpathadm list
lu" you should be able to determine which SAS addresses correspond to
which disks. You can also use something like diskmap.py from
https://github.com/swacquie/DiskMap (it requires the sas2ircu utility
from LSI).
Cheers,
--
Saso
------------------------------
Message: 3
Date: Mon, 02 Dec 2013 12:17:04 +0000
From: Saso Kiselkov <skiselkov.ml at gmail.com>
To: omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] 2x acctual disk quantity
Message-ID: <529C7A40.2090300 at gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 12/2/13, 12:08 PM, Hafiz Rafibeyli wrote:
>
> Saso thank you for your fast reply,
>
> its ok about two ports(sas dp)I know it,
>
> but my question is about ,which disk adresses to use in my zfs mirror or zfs raid config?
>
> in my case:
>
> c4t500000E1168BB382d0
> c4t500000E11693F232d0
> c4t500000E11696D5A2d0
> c4t500000E116974FB2d0
>
> OR
>
> c6t500000E1168BB383d0
> c6t500000E11693F233d0
> c6t500000E11696D5A3d0
> c6t500000E116974FB3d0
>
>
> If I understand right,when use first adresses I will use 1st controller only,and when use second addresses 2nd controller only?
You should use neither. The underlying disk paths are automatically
managed by the scsi_vhci driver. You need to consult "mpathadm list lu"
and use the device names printed there as your ZFS device nodes, for
example (using the example from
http://docs.oracle.com/cd/E19253-01/820-1931/agkax/index.html):
# mpathadm list lu
/dev/rdsk/c4t60020F20000035AF4267CCCB0002CEE2d0s2
Total Path Count: 2
Operational Path Count: 2
...
Here, c4t60020F20000035AF4267CCCB0002CEE2d0 is the correct disk node, so
you should use that. If you are getting "Total Path Count: 1" and twice
the number of nodes in "mpathadm list lu", then scsi_vhci is not
detecting your disks as multi-pathed and you need to tell it to do that.
See http://docs.oracle.com/cd/E19253-01/820-1931/gfpva/index.html on how
to do that. My guess is, however, that this should not be needed, since
you're saying you've got two LSI 9211-8i HBAs, which use the mpt_sas
driver, which is automatically multipath-enabled.
Cheers,
--
Saso
------------------------------
Message: 4
Date: Mon, 2 Dec 2013 16:19:50 +0200 (EET)
From: Hafiz Rafibeyli <rafibeyli at gmail.com>
To: omnios-discuss <omnios-discuss at lists.omniti.com>
Subject: [OmniOS-discuss] 2x acctual disk quantity
Message-ID:
<310264256.65409.1385993990627.JavaMail.zimbra at cantekstil.com.tr>
Content-Type: text/plain; charset=windows-1254
Saso ,I do not see my new added 4 disks in mpathadm list lu query.
Here is my output,
~# mpathadm list lu
/dev/rdsk/c1t5000C5005600A6B3d0s2
Total Path Count: 2
Operational Path Count: 2
/dev/rdsk/c1t5001517BB2747BE7d0s2
Total Path Count: 2
Operational Path Count: 2
/dev/rdsk/c1t5001517959627219d0s2
Total Path Count: 2
Operational Path Count: 2
/dev/rdsk/c1t5000C50055A607E3d0s2
Total Path Count: 2
Operational Path Count: 2
/dev/rdsk/c1t5001517BB2AFB592d0s2
Total Path Count: 1
Operational Path Count: 1
/dev/rdsk/c1t5000C50041E9D9A7d0s2
Total Path Count: 2
Operational Path Count: 2
/dev/rdsk/c1t5000C5004253FF87d0s2
Total Path Count: 2
Operational Path Count: 2
/dev/rdsk/c1t5000C50055A62F57d0s2
Total Path Count: 2
Operational Path Count: 2
/dev/rdsk/c1t5001517803D007D8d0s2
Total Path Count: 1
Operational Path Count: 1
/dev/rdsk/c1t5000C5005600B43Bd0s2
Total Path Count: 2
Operational Path Count: 2
/dev/rdsk/c1t5000C50041F1A5EFd0s2
Total Path Count: 2
Operational Path Count: 2
/dev/rdsk/c1t5000C50055A628EFd0s2
Total Path Count: 2
Operational Path Count: 2
These disks are from my 1st zfs pool which is now in production:
NAME STATE READ WRITE CKSUM CAP Product
zpool1 ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
c1t5000C50041E9D9A7d0 ONLINE 0 0 0 3 TB ST33000650SS
c1t5000C50041F1A5EFd0 ONLINE 0 0 0 3 TB ST33000650SS
c1t5000C5004253FF87d0 ONLINE 0 0 0 3 TB ST33000650SS
c1t5000C50055A607E3d0 ONLINE 0 0 0 3 TB ST33000650SS
c1t5000C50055A628EFd0 ONLINE 0 0 0 3 TB ST33000650SS
c1t5000C50055A62F57d0 ONLINE 0 0 0 3 TB ST33000650SS
logs
mirror-1 ONLINE 0 0 0
c1t5001517959627219d0 ONLINE 0 0 0 32 GB SSDSA2SH032G1GN
c1t5001517BB2747BE7d0 ONLINE 0 0 0 32 GB SSDSA2SH032G1GN
cache
c1t5001517803D007D8d0 ONLINE 0 0 0 120 GB INTEL SSDSC2CW12
c1t5001517BB2AFB592d0 ONLINE 0 0 0 120 GB INTEL SSDSC2CW12
spares
c1t5000C5005600A6B3d0 AVAIL 3 TB ST33000650SS
c1t5000C5005600B43Bd0 AVAIL 3 TB ST33000650SS
Is multipath'ing disabled on my system?and after enable multipath'ing will I lose my pool?because disk naming will change?
Will zfs import work with new disk naming to get back my zfs pool and data?
regards
Hafiz.
You should use neither. The underlying disk paths are automatically
managed by the scsi_vhci driver. You need to consult "mpathadm list lu"
and use the device names printed there as your ZFS device nodes, for
example (using the example from
http://docs.oracle.com/cd/E19253-01/820-1931/agkax/index.html):
# mpathadm list lu
/dev/rdsk/c4t60020F20000035AF4267CCCB0002CEE2d0s2
Total Path Count: 2
Operational Path Count: 2
...
Here, c4t60020F20000035AF4267CCCB0002CEE2d0 is the correct disk node, so
you should use that. If you are getting "Total Path Count: 1" and twice
the number of nodes in "mpathadm list lu", then scsi_vhci is not
detecting your disks as multi-pathed and you need to tell it to do that.
See http://docs.oracle.com/cd/E19253-01/820-1931/gfpva/index.html on how
to do that. My guess is, however, that this should not be needed, since
you're saying you've got two LSI 9211-8i HBAs, which use the mpt_sas
driver, which is automatically multipath-enabled.
Cheers,
--
Saso
------------------------------
Message: 5
Date: Mon, 02 Dec 2013 14:39:39 +0000
From: Saso Kiselkov <skiselkov.ml at gmail.com>
To: omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] 2x acctual disk quantity
Message-ID: <529C9BAB.9050002 at gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Can you please send me the output of format(1) when it lists the
available disks?
Cheers,
--
Saso
On 12/2/13, 2:19 PM, Hafiz Rafibeyli wrote:
> Saso ,I do not see my new added 4 disks in mpathadm list lu query.
>
> Here is my output,
>
> ~# mpathadm list lu
> /dev/rdsk/c1t5000C5005600A6B3d0s2
> Total Path Count: 2
> Operational Path Count: 2
> /dev/rdsk/c1t5001517BB2747BE7d0s2
> Total Path Count: 2
> Operational Path Count: 2
> /dev/rdsk/c1t5001517959627219d0s2
> Total Path Count: 2
> Operational Path Count: 2
> /dev/rdsk/c1t5000C50055A607E3d0s2
> Total Path Count: 2
> Operational Path Count: 2
> /dev/rdsk/c1t5001517BB2AFB592d0s2
> Total Path Count: 1
> Operational Path Count: 1
> /dev/rdsk/c1t5000C50041E9D9A7d0s2
> Total Path Count: 2
> Operational Path Count: 2
> /dev/rdsk/c1t5000C5004253FF87d0s2
> Total Path Count: 2
> Operational Path Count: 2
> /dev/rdsk/c1t5000C50055A62F57d0s2
> Total Path Count: 2
> Operational Path Count: 2
> /dev/rdsk/c1t5001517803D007D8d0s2
> Total Path Count: 1
> Operational Path Count: 1
> /dev/rdsk/c1t5000C5005600B43Bd0s2
> Total Path Count: 2
> Operational Path Count: 2
> /dev/rdsk/c1t5000C50041F1A5EFd0s2
> Total Path Count: 2
> Operational Path Count: 2
> /dev/rdsk/c1t5000C50055A628EFd0s2
> Total Path Count: 2
> Operational Path Count: 2
>
> These disks are from my 1st zfs pool which is now in production:
>
>
> NAME STATE READ WRITE CKSUM CAP Product
> zpool1 ONLINE 0 0 0
> raidz1-0 ONLINE 0 0 0
> c1t5000C50041E9D9A7d0 ONLINE 0 0 0 3 TB ST33000650SS
> c1t5000C50041F1A5EFd0 ONLINE 0 0 0 3 TB ST33000650SS
> c1t5000C5004253FF87d0 ONLINE 0 0 0 3 TB ST33000650SS
> c1t5000C50055A607E3d0 ONLINE 0 0 0 3 TB ST33000650SS
> c1t5000C50055A628EFd0 ONLINE 0 0 0 3 TB ST33000650SS
> c1t5000C50055A62F57d0 ONLINE 0 0 0 3 TB ST33000650SS
> logs
> mirror-1 ONLINE 0 0 0
> c1t5001517959627219d0 ONLINE 0 0 0 32 GB SSDSA2SH032G1GN
> c1t5001517BB2747BE7d0 ONLINE 0 0 0 32 GB SSDSA2SH032G1GN
> cache
> c1t5001517803D007D8d0 ONLINE 0 0 0 120 GB INTEL SSDSC2CW12
> c1t5001517BB2AFB592d0 ONLINE 0 0 0 120 GB INTEL SSDSC2CW12
> spares
> c1t5000C5005600A6B3d0 AVAIL 3 TB ST33000650SS
> c1t5000C5005600B43Bd0 AVAIL 3 TB ST33000650SS
>
> Is multipath'ing disabled on my system?and after enable multipath'ing will I lose my pool?because disk naming will change?
> Will zfs import work with new disk naming to get back my zfs pool and data?
>
> regards
>
> Hafiz.
>
>
> You should use neither. The underlying disk paths are automatically
> managed by the scsi_vhci driver. You need to consult "mpathadm list lu"
> and use the device names printed there as your ZFS device nodes, for
> example (using the example from
> http://docs.oracle.com/cd/E19253-01/820-1931/agkax/index.html):
>
> # mpathadm list lu
> /dev/rdsk/c4t60020F20000035AF4267CCCB0002CEE2d0s2
> Total Path Count: 2
> Operational Path Count: 2
> ...
>
> Here, c4t60020F20000035AF4267CCCB0002CEE2d0 is the correct disk node, so
> you should use that. If you are getting "Total Path Count: 1" and twice
> the number of nodes in "mpathadm list lu", then scsi_vhci is not
> detecting your disks as multi-pathed and you need to tell it to do that.
> See http://docs.oracle.com/cd/E19253-01/820-1931/gfpva/index.html on how
> to do that. My guess is, however, that this should not be needed, since
> you're saying you've got two LSI 9211-8i HBAs, which use the mpt_sas
> driver, which is automatically multipath-enabled.
>
> Cheers,
>
------------------------------
Subject: Digest Footer
_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss at lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
------------------------------
End of OmniOS-discuss Digest, Vol 21, Issue 2
*********************************************
------------------------------
Message: 3
Date: Mon, 02 Dec 2013 14:59:28 +0000
From: Saso Kiselkov <skiselkov.ml at gmail.com>
To: omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] 2x acctual disk quantity
Message-ID: <529CA050.8080303 at gmail.com>
Content-Type: text/plain; charset=windows-1254
No, I need you to run "format" and hit Control-C to exit it. it will
print a disk list up front, like so:
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c3t0d0 <DEFAULT cyl 8872 alt 2 hd 255 sec 63>
/pci at 7b,0/pci1022,7458 at 11/pci1000,3060 at 2/sd at 0,0
1. c6t600D0230006B66680C50AB7821F0E900d0 <ADVUNI-OXYGENRAID
416F4-347B-3.41TB>
/scsi_vhci/disk at g600d0230006b66680c50ab7821f0e900
2. c6t600D0230006C1C4C0C50BE5BC9D49100d0 <ADVUNI-OXYGENRAID
416F4-347B-3.41TB>
/scsi_vhci/disk at g600d0230006c1c4c0c50be5bc9d49100
(..etc..)
--
Saso
On 12/2/13, 2:55 PM, Hafiz Rafibeyli wrote:
> Saso is this you are asking for?
>
> id part identify stat diskcap partcap error vendor product sn
> c1t5000C50041E9D9A7d0 (!parted) via dd ok 3 TB S:0 H:4 T:0 SEAGATE ST33000650SS Z2934YB40000923
> c1t5000C50041F1A5EFd0 (!parted) via dd ok 3 TB S:0 H:4 T:0 SEAGATE ST33000650SS Z2937JC90000924
> c1t5000C5004253FF87d0 (!parted) via dd ok 3 TB S:0 H:4 T:0 SEAGATE ST33000650SS Z294403Y0000C25
> c1t5000C50055A607E3d0 (!parted) via dd ok 3 TB S:0 H:4 T:0 SEAGATE ST33000650SS Z2955HY80000931
> c1t5000C50055A628EFd0 (!parted) via dd ok 3 TB S:0 H:4 T:0 SEAGATE ST33000650SS Z295857E0000931
> c1t5000C50055A62F57d0 (!parted) via dd ok 3 TB S:0 H:4 T:0 SEAGATE ST33000650SS Z2957MGA0000931
> c1t5000C5005600A6B3d0 (!parted) via dd ok 3 TB S:0 H:4 T:0 SEAGATE ST33000650SS Z2967CNZ0000C32
> c1t5000C5005600B43Bd0 (!parted) via dd ok 3 TB S:0 H:4 T:0 SEAGATE ST33000650SS Z2967CF50000C32
> c1t5001517803D007D8d0 (!parted) via dd ok 120 GB S:2 H:0 T:0 ATA INTEL SSDSC2CW12 CVCV249102HG120
> c1t5001517959627219d0 (!parted) via dd ok 32 GB S:2 H:0 T:0 ATA SSDSA2SH032G1GN CVEM130600KP032
> c1t5001517BB2747BE7d0 (!parted) via dd ok 32 GB S:2 H:0 T:0 ATA SSDSA2SH032G1GN CVEM1404005G032
> c1t5001517BB2AFB592d0 (!parted) via dd ok 120 GB S:2 H:0 T:0 ATA INTEL SSDSC2CW12 CVCV245100J1120
> c3t1d0 (!parted) via dd ok 50 GB S:2 H:0 T:0 ATA STEC MACH16 M STM0001681F1
> c3t2d0 (!parted) via dd ok 50 GB S:2 H:0 T:0 ATA STEC MACH16 M STM0001681EE
> c4t500000E1168BB382d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0EUJ7104
> c4t500000E11693F232d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0EY64104
> c4t500000E11696D5A2d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0F12G104
> c4t500000E116974FB2d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0F1P5104
> c4t50000392C8008B7Ed0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FBDSP EB01PA9013TD103
> c4t5000C5002BD75C05d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FAWHV 6SE134XX0000B10
> c4t5000CCA0150597A5d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP DG0300FARVV PFV32ANE
> c4t5000CCA01505A321d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP DG0300FARVV PFV333BE
> c6t500000E1168BB383d0 (!parted) via dd ok 300 GB S:0 H:1 T:0 HP EG0300FARTT D001PAB0EUJ7104
> c6t500000E11693F233d0 (!parted) via dd ok 300 GB S:0 H:1 T:0 HP EG0300FARTT D001PAB0EY64104
> c6t500000E11696D5A3d0 (!parted) via dd ok 300 GB S:0 H:1 T:0 HP EG0300FARTT D001PAB0F12G104
> c6t500000E116974FB3d0 (!parted) via dd ok 300 GB S:0 H:1 T:0 HP EG0300FARTT D001PAB0F1P5104
> c6t50000392C8008B7Fd0 (!parted) via dd ok 300 GB S:0 H:1 T:0 HP EG0300FBDSP EB01PA9013TD103
> c6t5000C5002BD75C06d0 (!parted) via dd ok 300 GB S:0 H:1 T:0 HP EG0300FAWHV 6SE134XX0000B10
> c6t5000CCA0150597A6d0 (!parted) via dd ok 300 GB S:0 H:1 T:0 HP DG0300FARVV PFV32ANE
> c6t5000CCA01505A322d0 (!parted) via dd ok 300 GB S:0 H:1 T:0 HP DG0300FARVV PFV333BE
>
> ----- Orijinal Mesaj -----
> Kimden: omnios-discuss-request at lists.omniti.com
> Kime: omnios-discuss at lists.omniti.com
> G?nderilenler: 2 Aral?k Pazartesi 2013 16:39:43
> Konu: OmniOS-discuss Digest, Vol 21, Issue 2
>
> Send OmniOS-discuss mailing list submissions to
> omnios-discuss at lists.omniti.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> or, via email, send a message with subject or body 'help' to
> omnios-discuss-request at lists.omniti.com
>
> You can reach the person managing the list at
> omnios-discuss-owner at lists.omniti.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OmniOS-discuss digest..."
>
>
> Today's Topics:
>
> 1. Re: Re-installing OmniOS after Crash (Piers Dawson-Damer)
> 2. 2x acctual disk quantity (Hafiz Rafibeyli)
> 3. Re: 2x acctual disk quantity (Saso Kiselkov)
> 4. 2x acctual disk quantity (Hafiz Rafibeyli)
> 5. Re: 2x acctual disk quantity (Saso Kiselkov)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 2 Dec 2013 20:26:34 +1100
> From: Piers Dawson-Damer <piers at mm.st>
> To: omnios-discuss at lists.omniti.com
> Subject: Re: [OmniOS-discuss] Re-installing OmniOS after Crash
> Message-ID: <B3452613-0C4C-4CD2-9B32-3358ADB0849F at mm.st>
> Content-Type: text/plain; charset="us-ascii"
>
> Any update on this error?
>
> I also cannot update my system. Have tried removing the OmniTi repositories
>
> Piers
>
> SunOS prod 5.11 omnios-ef9657e i86pc i386 i86pc
>
> piers at prod:~$ pfexec pkg update -v
> Creating Plan /
> pkg update: The certificate which issued this certificate:/C=US/ST=Maryland/O=OmniTI/OU=OmniOS/CN=OmniOS r151007 Release Signing Certificate/emailAddress=omnios-support at omniti.com could not be found. The issuer is:/C=US/ST=Maryland/L=Fulton/O=OmniTI/CN=OmniTI Certificate Authority
> The package involved is:pkg://omnios/runtime/python-26@2.6.8,5.11-0.151007:20130926T213513Z
>
>
>
> On 27 Oct 2013, at 11:04 pm, Sam M <emunch at utmi.in> wrote:
>
>> Hello all.
>>
>> After installing napp-it, OmniOS got hosed. Not sure what caused it, probably not napp-it, because I couldn't boot up my system with any of the boot images, including the original.
>>
>> Now, on a brand new installation, I'm getting the following error -
>>
>> # pkg update web/ca-bundle pkg
>> Creating Plan -
>> pkg update: The certificate which issued this certificate:/C=US/ST=Maryland/O=OmniTI/OU=OmniOS/CN=OmniOS r151007 Release Signing Certificate/emailAddress=omnios-support at omniti.com could not be found. The issuer is:/C=US/ST=Maryland/L=Fulton/O=OmniTI/CN=OmniTI Certificate Authority
>> The package involved is:pkg://omnios/library/python-2/pybonjour@1.1.1,5.11-0.151007:20130516T114553Z
>>
>> # uname -a
>> SunOS sequoia 5.11 omnios-df542ea i86pc i386 i86pc Solaris
>>
>> There were no errors earlier after the installation when updating packages.
>>
>> How can I fix this? Where can I find OmniTI's CA certificate?
>>
>> TIA.
>>
>> Sam
>>
>>
>>
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://omniosce.org/ml-archive/attachments/20131202/8a7686b8/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 2 Dec 2013 14:08:04 +0200 (EET)
> From: Hafiz Rafibeyli <rafibeyli at gmail.com>
> To: omnios-discuss <omnios-discuss at lists.omniti.com>
> Subject: [OmniOS-discuss] 2x acctual disk quantity
> Message-ID:
> <147167035.58244.1385986084129.JavaMail.zimbra at cantekstil.com.tr>
> Content-Type: text/plain; charset=windows-1254
>
>
> Saso thank you for your fast reply,
>
> its ok about two ports(sas dp)I know it,
>
> but my question is about ,which disk adresses to use in my zfs mirror or zfs raid config?
>
> in my case:
>
> c4t500000E1168BB382d0
> c4t500000E11693F232d0
> c4t500000E11696D5A2d0
> c4t500000E116974FB2d0
>
> OR
>
> c6t500000E1168BB383d0
> c6t500000E11693F233d0
> c6t500000E11696D5A3d0
> c6t500000E116974FB3d0
>
>
> If I understand right,when use first adresses I will use 1st controller only,and when use second addresses 2nd controller only?
>
> regards
>
> Hafiz
>
>
> Message: 6
> Date: Sat, 30 Nov 2013 11:26:57 +0000
> From: Saso Kiselkov <skiselkov.ml at gmail.com>
> To: omnios-discuss at lists.omniti.com
> Subject: Re: [OmniOS-discuss] 2x acctual disk quantity
> Message-ID: <5299CB81.7090101 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 11/30/13, 9:43 AM, Hafiz Rafibeyli wrote:
>> Hello,
>>
>> After adding 4 SAS dual port disks to my omnios system(omnios-b281e50+napp-it) ,I see number of disks 2x acctual quantity.
>>
>> I have dual controller backplane(supermicro) and 2 LSI 9211-8i,
>>
>> There is no any quantity problem with another disks,only with new added HP 300GB SAS DP.
>>
>>
>> c4t500000E1168BB382d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0EUJ7104
>> c4t500000E11693F232d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0EY64104
>> c4t500000E11696D5A2d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0F12G104
>> c4t500000E116974FB2d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0F1P5104
>> c6t500000E1168BB383d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0EUJ7104
>> c6t500000E11693F233d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0EY64104
>> c6t500000E11696D5A3d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0F12G104
>> c6t500000E116974FB3d0 (!parted) via dd ok 300 GB S:0 H:0 T:0 HP EG0300FARTT D001PAB0F1P5104
>
> Hey Hafiz,
>
> What you're seeing are the two ports of the disks. Using "mpathadm list
> lu" you should be able to determine which SAS addresses correspond to
> which disks. You can also use something like diskmap.py from
> https://github.com/swacquie/DiskMap (it requires the sas2ircu utility
> from LSI).
>
> Cheers,
>
------------------------------
Subject: Digest Footer
_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss at lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
------------------------------
End of OmniOS-discuss Digest, Vol 21, Issue 3
*********************************************
More information about the OmniOS-discuss
mailing list