I should have put this in the subject; the receiving zpool is on a
FreeNas 9.3 box.
When I did as described by you, i e "zfs send -R pool/name@snap | ..."
the resulting dataset on Freenas didn't really work.
When trying to set up a share for the dataset on Freenas, I got
"unsupported share prot
Hi,
> Thanks, that was exactly it.
>
> To add a few bits of info:
>
> You first must get a pair of private/public keys
>
> ssh-keyget -t rsa
>
> for the OI user to run the zfs send.
Um, yes, sorry, I assumed that you already did this ;-)
> I suppose you could use password login for root on
Hi,
> I should have put this in the subject; the receiving zpool is on a
> FreeNas 9.3 box.
>
> When I did as described by you, i e "zfs send -R pool/name@snap | ..."
> the resulting dataset on Freenas didn't really work.
> When trying to set up a share for the dataset on Freenas, I got
> "unsu
On 2015-05-05 11:56, Thorsten Heit wrote:
Hi,
I should have put this in the subject; the receiving zpool is on a
FreeNas 9.3 box.
When I did as described by you, i e "zfs send -R pool/name@snap | ..."
the resulting dataset on Freenas didn't really work.
When trying to set up a share for the da
Am 05.05.2015 um 14:00 schrieb openindiana-discuss-requ...@openindiana.org:
As a side note; just piping to ssh is excruciatingly slow, using netcat,
"nc", speeds things up at least 4fold.
The method that worked fine for me was using mbuffer. (I couldn't make
netcat work, shame on me, but I also
Running Hipster, I was using firefox 31.0.2 (package from the Firefox FTP
site) happily until today (first day I've booted since I recently upgraded)
previous update 2015-03-27, recent update 2015-04-30
Firefox works fine, except with any "alert" or popup box or sometimes
select lists, and dialog
mbuffer isn't included in FreeNAS.
It IS available for FreeBSD, but I don't know if that version will
behave responsibly in FreeNAS.
FreeNAS devs say "mbuffer won't be included in FreeNAS because we
already do proper buffering via dd."
Would dd work for buffering in Solaris/OI??
On 2015-05
you can also use ttcp or iperf just fine. I do that all the time and they are
pretty much available anywhere. (ttcp is so simple it's just a single .c source
file). The buffering isn't really the important part, using as close to raw tcp
transport gets you the biggest benefit (vs encryption/decr
ttcp?? ToolTalk CoPy?
On 2015-05-05 15:32, Doug Hughes wrote:
you can also use ttcp or iperf just fine. I do that all the time and they are
pretty much available anywhere. (ttcp is so simple it's just a single .c source
file). The buffering isn't really the important part, using as close t
On 1 May 2015 at 07:13, Nick Tan wrote:
> Has anyone tried using SMR disks with ZFS? I bought a Seagate 8TB SMR disk
> and put it in a esata enclosure for my backups. I found that zfs send
> would cause the disk to go offline. My guess is that zfs send is too fast
> and fills the drive write ca
In OI 151a7, the option -r is NOT available in zfs send.
See https://www.illumos.org/issues/2811
Has this been fixed in later OI versions???
On 2015-05-04 10:25, Thorsten Heit wrote:
2) Send the pool to your new machine:
root@oldmachine:# zfs send -R @ | \
ssh root@ '/usr/sbin/zfs receive
I couldn't think of any easy and automatic way to test read speed for
files mounted via NFS and CIFS from FreeNAS, in OI 151a7.
I used
time dd=/mountdir/file of=/dev/null bs=1024k
and arrived at 3-500 MB/s or so,
However this means I must read numbers off the screen and calculate, and
I'd ra
On 5/05/2015 5:42 PM, Hans J. Albertsson wrote:
I couldn't think of any easy and automatic way to test read speed for
files mounted via NFS and CIFS from FreeNAS, in OI 151a7.
I used
time dd=/mountdir/file of=/dev/null bs=1024k
and arrived at 3-500 MB/s or so,
However this means I must read
You could try to build it from source on your FreeNAS machine. If it
builds, I guess it will work.
Here is the project page: http://www.maier-komor.de/mbuffer.html
BR
Sebastian
Am 05.05.2015 um 19:38 schrieb openindiana-discuss-requ...@openindiana.org:
Message: 3
Date: Tue, 05 May 2015 15:30
If you transfer many snapshots, especially if some are small, there is a
benefit from buffering: the receive end, after each snapshot, stops
consuming data, possibly for several seconds. Without a buffer, this will
stall the sending side, so that nothing gets done during those pauses. I
have put
15 matches
Mail list logo
