Re: [zfs-discuss] The format command crashes on 3TB disk but zpool create ok
On 2012-12-14 17:03, Edward Ned Harvey (opensolarisisdeadlongliveopensolaris) wrote: Suspicion and conjecture only: I think format uses a fdisk label, which has a 2T limit. Technically, "fdisk" is a program and labels (partitioning tables) are MBR and EFI/GPT :) And "fdisk" at least in OpenIndiana can explicitly label a disk as EFI, similarly to what ZFS does when given the whole disk to a pool. You might also have luck with GNU parted, though I've had older builds (i.e. in SXCE) crash on 3Tb disks too, including one that's labeled as EFI and used in a pool on the same SXCE. There were no such problems with newer build of parted as in OI, so that disk was in fact labeled for SXCE while the box was booted with OI LiveCD. HTH, //Jim Klimov ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] any more efficient way to transfer snapshot between two hosts than ssh tunnel?
> >Even with infinite wire speed, you're bound by the ability of the source server >to generate the snapshot stream and the ability of the destination server to >write the snapshots to the media. > >Our little servers in-house using ZFS don't read/write that fast when pulling >snapshot contents off the disks, since they're essentially random access on a >server that's been creating/deleting snapshots for a long time. > >--eric > That is true. This discussion is assumed under ideal condition. We want to minimize the overhead in transportation layer only. Thanks. Fred ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss