Re: [OmniOS-discuss] issue importing zpool on S11.1 from omniOS LUNs

Am 31.01.17 um 00:15 schrieb Richard Elling: On Jan 29, 2017, at 3:10 AM, Stephan Budach wrote: Hi, just to wrap this up… I decided to go with 15 additional LUNs on each storage zpool, to avoid zfs complainign about replication mismatches. I know, I cluld have done

Re: [OmniOS-discuss] issue importing zpool on S11.1 from omniOS LUNs

> On Jan 29, 2017, at 3:10 AM, Stephan Budach wrote: > > Hi, > > just to wrap this up… I decided to go with 15 additional LUNs on each storage > zpool, to avoid zfs complainign about replication mismatches. I know, I cluld > have done otherwise, but it somehow felt

Re: [OmniOS-discuss] issue importing zpool on S11.1 from omniOS LUNs

Hi, just to wrap this up… I decided to go with 15 additional LUNs on each storage zpool, to avoid zfs complainign about replication mismatches. I know, I cluld have done otherwise, but it somehow felt better this way. After all three underlying zpools were "pimped", I was able to mount the

Re: [OmniOS-discuss] issue importing zpool on S11.1 from omniOS LUNs

Hi Richard, Am 26.01.17 um 20:18 schrieb Richard Elling: On Jan 26, 2017, at 12:20 AM, Stephan Budach > wrote: Hi Richard, gotcha… read on, below… "thin provisioning" bit you. For "thick provisioning" you’ll have a refreservation

Re: [OmniOS-discuss] issue importing zpool on S11.1 from omniOS LUNs

> On Jan 26, 2017, at 12:20 AM, Stephan Budach wrote: > > Hi Richard, > > gotcha… read on, below… "thin provisioning" bit you. For "thick provisioning" you’ll have a refreservation and/or reservation. — richard > > Am 26.01.17 um 00:43 schrieb Richard Elling: >>

Re: [OmniOS-discuss] issue importing zpool on S11.1 from omniOS LUNs

Just for sanity… these are a couple of errors fmdump outputs using -eV root@solaris11atest2:~# fmdump -eV TIME CLASS Jan 25 2017 10:10:45.011761190 ereport.io.pciex.rc.tmp nvlist version: 0 class = ereport.io.pciex.rc.tmp ena = 0xff37bc9a861

Re: [OmniOS-discuss] issue importing zpool on S11.1 from omniOS LUNs

Hi Richard, gotcha… read on, below… Am 26.01.17 um 00:43 schrieb Richard Elling: more below… On Jan 25, 2017, at 3:01 PM, Stephan Budach > wrote: Ooops… should have waited with sending that message after I rebootet the S11.1 host… Am

Re: [OmniOS-discuss] issue importing zpool on S11.1 from omniOS LUNs

more below… > On Jan 25, 2017, at 3:01 PM, Stephan Budach wrote: > > Ooops… should have waited with sending that message after I rebootet the > S11.1 host… > > > Am 25.01.17 um 23:41 schrieb Stephan Budach: >> Hi Richard, >> >> Am 25.01.17 um 20:27 schrieb Richard

Re: [OmniOS-discuss] issue importing zpool on S11.1 from omniOS LUNs

Ooops… should have waited with sending that message after I rebootet the S11.1 host… Am 25.01.17 um 23:41 schrieb Stephan Budach: Hi Richard, Am 25.01.17 um 20:27 schrieb Richard Elling: Hi Stephan, On Jan 25, 2017, at 5:54 AM, Stephan Budach

Re: [OmniOS-discuss] issue importing zpool on S11.1 from omniOS LUNs

Hi Richard, Am 25.01.17 um 20:27 schrieb Richard Elling: Hi Stephan, On Jan 25, 2017, at 5:54 AM, Stephan Budach > wrote: Hi guys, I have been trying to import a zpool, based on a 3way-mirror provided by three omniOS boxes via iSCSI.

Re: [OmniOS-discuss] issue importing zpool on S11.1 from omniOS LUNs

Hi Stephan, > On Jan 25, 2017, at 5:54 AM, Stephan Budach wrote: > > Hi guys, > > I have been trying to import a zpool, based on a 3way-mirror provided by > three omniOS boxes via iSCSI. This zpool had been working flawlessly until > some random reboot of the S11.1

Re: [OmniOS-discuss] issue importing zpool on S11.1 from omniOS LUNs

Hi Dale, this is exactly, what I am currently trying and the iostat errors are from that import run. Stephan Von meinem iPhone gesendet > Am 25.01.2017 um 18:38 schrieb Dale Ghent : > > > Oh, ok, I misunderstood you as trying to import illumos vdevs directly onto a >

Re: [OmniOS-discuss] issue importing zpool on S11.1 from omniOS LUNs

ZFS as implemented in Oracle Solaris is *not* OpenZFS, which is what illumos (and all illumos distros), FreeBSD, and the ZFS on Linux/macOS projects use. Up to a level of features, the two are compatible - but then they diverge in features. If one pool has features the zfs driver does not