Great, thanks!
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
BJ Quinn wrote:
> Then what if I ever need to export the pool on the primary server
> and then import it on the replicated server. Will ZFS know which
> drives should be part of the stripe even though the device names
> across servers may not be the same?
Yes, "zpool import " will figur
Then what if I ever need to export the pool on the primary server and then
import it on the replicated server. Will ZFS know which drives should be part
of the stripe even though the device names across servers may not be the same?
--
This message posted from opensolaris.org
___
BJ,
>> The means to specify this is "sndradm -nE ...",
>> when 'E' is equal enabled.
>
> Got it. Nothing on the disk, nothing to replicate (yet).
:-)
>> The manner in which SNDR can guarantee that
>> two or more volumes are write-order consistent, as they are
>> replicated is place them in the
> The means to specify this is "sndradm -nE ...",
> when 'E' is equal enabled.
Got it. Nothing on the disk, nothing to replicate (yet).
>The manner in which SNDR can guarantee that
>two or more volumes are write-order consistent, as they are
>replicated is place them in the same I/O consistency
BJ Quinn wrote:
> I have two servers set up, with two drives each. The OS is stored
> on one drive, and the data on the second drive. I have SNDR
> replication set up between the two servers for the data drive only.
>
> I'm running out of space on my data drive, and I'd like to do a
> simp
I have two servers set up, with two drives each. The OS is stored on one
drive, and the data on the second drive. I have SNDR replication set up
between the two servers for the data drive only.
I'm running out of space on my data drive, and I'd like to do a simple "zpool
attach" command to ad
