Hi.
On 02.06.16 19:50, Slawa Olhovchenkov wrote:
> I am suggesting next setup:
>
> node0:
> own pool zroot0: mirror-0: local_disk0
>remote-iscsi_disk1/1
> local_disk1: exported by iscsi as remote-iscsi_disk0/1 to node1
>
> node1:
> own pool zroot1: mirror-
Hi,
On 02.06.16 19:50, Slawa Olhovchenkov wrote:
>
> I am suggesting next setup:
>
> node0:
> own pool zroot0: mirror-0: local_disk0
>remote-iscsi_disk1/1
> local_disk1: exported by iscsi as remote-iscsi_disk0/1 to node1
>
> node1:
> own pool zroot1: mirro
On Fri, Jun 03, 2016 at 01:40:54PM +0500, Eugene M. Zheganin wrote:
> Hi.
>
> On 02.06.16 19:50, Slawa Olhovchenkov wrote:
> > I am suggesting next setup:
> >
> > node0:
> > own pool zroot0: mirror-0: local_disk0
> > remote-iscsi_disk1/1
> > local_disk1: expor
On Fri, Jun 03, 2016 at 02:05:07PM +0500, Eugene M. Zheganin wrote:
> Hi,
>
> On 02.06.16 19:50, Slawa Olhovchenkov wrote:
> >
> > I am suggesting next setup:
> >
> > node0:
> > own pool zroot0: mirror-0: local_disk0
> > remote-iscsi_disk1/1
> > local_disk1: e
> You message lead me to a though that I could use iSCSI to replicate the
> zfs pool from node1 to both iSCSI-provided disk on a node2 in a 4-way
> mirror, right ? Are there any obvious obstacles to this, that I don't
> see, considering the bandwith will be enough ?
I have spent a long time doing
03.06.2016 2:48, Peter Jeremy пишет:
On 2016-Jun-02 12:12:35 +0500, "Eugene M. Zheganin" wrote:
differs a lot ? And why should I prefere this overcomplicated scheme
over the geom_mirror, which seems rather simple when comparing. Seems
like I can point HAST to /dev/mirror/whatever device, right
On Fri, Jun 3, 2016 at 1:40 AM, Eugene M. Zheganin
wrote:
> Hi.
>
> On 02.06.16 19:50, Slawa Olhovchenkov wrote:
> > I am suggesting next setup:
> >
> > node0:
> > own pool zroot0: mirror-0: local_disk0
> >remote-iscsi_disk1/1
> > local_disk1: exported by i
Slawa Olhovchenkov writes:
> Default install with local_unbound and ntpd can't be functional with
> incorrect date/time in BIOS:
>
> Unbound requred correct time for DNSSEC check and refuseing queries
> ("Jul 1 20:17:29 yellowrat unbound: [3444:0] info: failed to prime
> trust anchor -- DNSKEY rr
On Fri, Jun 03, 2016 at 02:34:18PM -0400, Lowell Gilbert wrote:
> Slawa Olhovchenkov writes:
>
> > Default install with local_unbound and ntpd can't be functional with
> > incorrect date/time in BIOS:
> >
> > Unbound requred correct time for DNSSEC check and refuseing queries
> > ("Jul 1 20:17:2
On 2016-Jun-03 22:12:55 +0700, Eugene Grosbein wrote:
>> all your media content is valid. I've also had bad experiences with
>> gmirror volumes silently getting out of sync on a crash.
>
>
>gmirror or (gmirror+gjournal) ones?
Plain gmirror.
--
Peter Jeremy
signature.asc
Description: PGP sign
10 matches
Mail list logo