Hi,
I have recently been handed a couple storage systems and an HPC that was built by some guys who took off for "greener" pastures. I am new to ZFS and gmultipath and have a few questions if anyone is willing to help.

For starters, I have a couple failed disks so I am trying to wrap my head around the entire system before I go ripping disks out.

I have a single pool called array that contains 8 raidz sets.
When i run "zpool status" i get output about the pool and the raid sets. They are labelled raidz3-0, raidz3-1, raidz3-2..., and I assume that those are labels and not definitive proof that the set is raidz3. When I run "zpool list -v array", each set has the same title of "raidz3"

Question: Is the output of "zpool list -v array" the definitive proof that it is raidz3 or is that just another label?


A snippet of "zpool status" shows for example:

array                                           DEGRADED     0 0     0
      raidz3-0                                      ONLINE 0     0     0
multipath/disk1p1 ONLINE 0 0 0 block size: 512B configured, 4096B native gptid/8d0cf578-69d2-11e3-bc82-00259061c2b0 ONLINE 0 0 0 block size: 512B configured, 4096B native gptid/8d627ea9-69d2-11e3-bc82-00259061c2b0 ONLINE 0 0 0 block size: 512B configured, 4096B native gptid/8db741ce-69d2-11e3-bc82-00259061c2b0 ONLINE 0 0 0 block size: 512B configured, 4096B native gptid/8e0cedc1-69d2-11e3-bc82-00259061c2b0 ONLINE 0 0 0 block size: 512B configured, 4096B native multipath/disk21p1 ONLINE 0 0 0 block size: 512B configured, 4096B native gptid/8ebbb3b1-69d2-11e3-bc82-00259061c2b0 ONLINE 0 0 0 block size: 512B configured, 4096B native gptid/8f163d91-69d2-11e3-bc82-00259061c2b0 ONLINE 0 0 0 block size: 512B configured, 4096B native gptid/8f6caf80-69d2-11e3-bc82-00259061c2b0 ONLINE 0 0 0 block size: 512B configured, 4096B native
      raidz3-1                                      DEGRADED 0     0     0
gptid/8fcffb3b-69d2-11e3-bc82-00259061c2b0 ONLINE 0 0 0 block size: 512B configured, 4096B native gptid/90288230-69d2-11e3-bc82-00259061c2b0 ONLINE 0 0 0 block size: 512B configured, 4096B native gptid/907f3719-69d2-11e3-bc82-00259061c2b0 ONLINE 0 0 0 block size: 512B configured, 4096B native multipath/disk44p1 ONLINE 0 0 0 block size: 512B configured, 4096B native gptid/912d1e9d-69d2-11e3-bc82-00259061c2b0 ONLINE 0 0 0 block size: 512B configured, 4096B native gptid/91841263-69d2-11e3-bc82-00259061c2b0 ONLINE 0 0 0 block size: 512B configured, 4096B native gptid/91db5c27-69d2-11e3-bc82-00259061c2b0 ONLINE 0 0 0 block size: 512B configured, 4096B native gptid/92324909-69d2-11e3-bc82-00259061c2b0 ONLINE 0 0 0 block size: 512B configured, 4096B native 1261723115475920584 UNAVAIL 2 81 0 was /dev/gptid/9287be65-69d2-11e3-bc82-00259061c2b0


Question 2: One of the failed disks showing at the bottom there, but should I be alarmed by some of the disks being displayed as multipath/diskXXp1 instead of a gptid address?

I have a few more questions but we can start with these,
-Gary

<<attachment: gpitman.vcf>>

_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to