[OpenIndiana-discuss] Antwort: Transferring everything in one zpool to be a subtree in another larger zpool

2015-05-04 Thread Thorsten Heit
Hi,

 I have this old machine running oi151a7 with a zpool containing a set of
 filesystems used for media files of various types, and I want to 
transfer
 them all, in one go, safely but not unnecessarily slowly, to a new zpool 
on
 a different machine.
 
 The old zpool is on a 2tb two-disk mirror on the oi151a7,  while the new
 zpool is a freenas raidz2 of 12tb or so actual data space.
 
 I want your advice on what is the correct, safest and/or most practical 
way
 to do it.
 
 Both machines are on a GB network, and neither of them will be doing
 anything else while transferring the data.
 
 I'm guessing zfs send/recv over the network, using nc for buffering, but
 I've never done this before, so please advice me.


Quite easy with zfs and a little time for the sending/receiving process:

1) Create a snapshot of the pool you intend to move:

root@oldmachine:# zfs snapshot -r oldpool@snapshot_name


2) Send the pool to your new machine:

root@oldmachine:# zfs send -R oldpool@snapshot_name | \
ssh root@new_machine '/usr/sbin/zfs receive newpool/new_name'

-R creates a replication stream package that sends everything 
recursively up to the named snapshot, including properties, snapshots, 
descendent file systems and clones.

If you're not interested in older snapshots, use -rp instead of -R 
whereas -r creates a recursive stream package and -p tells zfs send 
to include properties.


3) Have a coffee or two and wait :-)


4) Optionally move the received zfs filesystems, volumes, ... one level up 
in your new pool:

root@newmachine:# zfs rename newpool/new_name/filesystem1 
newpool/filesystem1


I have done this several times in the past without problems. You could 
optionally compress the stream with gzip and uncompress it when receiving:

root@oldmachine:# zfs send -R oldpool@snapshot_name | gzip | \
ssh root@new_machine '/usr/bin/gunzip | /usr/sbin/zfs receive 
newpool/new_name'


In my experience with some 100GB of data this took far longer in our LAN 
than the same without compressing although the sending and receiving 
machines should have been fast enough...


If you don't want to send the whole pool, replace oldpool above with 
the file system / data set you're interested in; the commands stay the 
same.


Best regards

Thorsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


[OpenIndiana-discuss] OI updates

2015-05-04 Thread Jon Tibble

I've just pushed a collection of illumos-gate CVE fixes for a9.
This covers:
- 5378 CVE-2014-3158 ppp: integer overflow in option parsing
- 5480 CVE-2012-3165 mailx(1) buffer overflow vulnerability
- 5481 CVE-2012-1750 mailx(1) tilde expansion vulnerability
- 5853 pfexec_call() error handling could be improved
  5854 pfexecd should initialize pfexec response buffers
  (Not sure what CVE this actually was assigned.)

I've also pushed the NVIDIA driver update to 304.125 and the missing 
pieces of the Delphix vmxnet3s driver patchset.


The new packages are:
SUNWcs@0.5.11,5.11-0.151.1.9:20150504T114725Z
system/network/ppp@0.5.11,5.11-0.151.1.9:20150504T120317Z
consolidation/nvidia/nvidia-incorporation@0.5.11,5.11-0.151.1.9:20150504T113748Z
driver/graphics/nvidia@0.304.125,5.11-0.151.1.9:20150504T113958Z
driver/network/vmxnet3s@0.5.11,5.11-0.151.1.9:20150504T114139Z

For those interested in an up to date OI branded illumos-gate, I've 
finished getting the OI patches done so anyone wishing to work with that 
can grab it here: https://github.com/OpenIndiana/illumos-gate


That should build fine with GCC on hipster.  If you build it with Studio 
on a9 you'll get a warning about clog 
(https://www.illumos.org/issues/5353) and warnings about pointers that 
can be fixed with 
https://paste.ec/paste/sDXMLQXR#DnPbnxkm9tFNmX0WxH1rWdV6CjIpGRmcKwfP2HOCgFE


I've deliberately left out any broadcom patches that we had as there 
seems to be a mishmash of patches around from various sources and it's 
better for everyone if people look and work against upstream illumos-gate.


Regards,
Jon

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


Re: [OpenIndiana-discuss] Antwort: Transferring everything in one zpool to be a subtree in another larger zpool

2015-05-04 Thread Hans J. Albertsson

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.

Then copy the public key from ~/.ssh/id_rsa.pub  on OI to the user root 
(or other user with admin privs) on freenas.

In the web mgmt gui on freenas, click Account-view-users-root
and click edit at the bottom. Put the contents of your .pub key into 
the public key field of the edit form.


To test run

ssh root@freenas_address ls

When it works, run

pfexec zfs send -R Tank/dataset@snapshot | ssh root@freenas_address 
'/sbin/zfs recv Tank/Media/name'


on OI
zfs on freenas is in /sbin,

I suppose you could use password login for root on freenas, but freenas 
is set up to use rsa key controlled login for replication. So this way 
probably has been tested a lot more.



On 2015-05-04 10:25, Thorsten Heit wrote:

Hi,


I have this old machine running oi151a7 with a zpool containing a set of
filesystems used for media files of various types, and I want to

transfer

them all, in one go, safely but not unnecessarily slowly, to a new zpool

on

a different machine.

The old zpool is on a 2tb two-disk mirror on the oi151a7,  while the new
zpool is a freenas raidz2 of 12tb or so actual data space.

I want your advice on what is the correct, safest and/or most practical

way

to do it.

Both machines are on a GB network, and neither of them will be doing
anything else while transferring the data.

I'm guessing zfs send/recv over the network, using nc for buffering, but
I've never done this before, so please advice me.


Quite easy with zfs and a little time for the sending/receiving process:

1) Create a snapshot of the pool you intend to move:

root@oldmachine:# zfs snapshot -r oldpool@snapshot_name


2) Send the pool to your new machine:

root@oldmachine:# zfs send -R oldpool@snapshot_name | \
 ssh root@new_machine '/usr/sbin/zfs receive newpool/new_name'

-R creates a replication stream package that sends everything
recursively up to the named snapshot, including properties, snapshots,
descendent file systems and clones.

If you're not interested in older snapshots, use -rp instead of -R
whereas -r creates a recursive stream package and -p tells zfs send
to include properties.


3) Have a coffee or two and wait :-)


4) Optionally move the received zfs filesystems, volumes, ... one level up
in your new pool:

root@newmachine:# zfs rename newpool/new_name/filesystem1
newpool/filesystem1


I have done this several times in the past without problems. You could
optionally compress the stream with gzip and uncompress it when receiving:

root@oldmachine:# zfs send -R oldpool@snapshot_name | gzip | \
 ssh root@new_machine '/usr/bin/gunzip | /usr/sbin/zfs receive
newpool/new_name'


In my experience with some 100GB of data this took far longer in our LAN
than the same without compressing although the sending and receiving
machines should have been fast enough...


If you don't want to send the whole pool, replace oldpool above with
the file system / data set you're interested in; the commands stay the
same.


Best regards

Thorsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


Re: [OpenIndiana-discuss] Antwort: Transferring everything in one zpool to be a subtree in another larger zpool

2015-05-04 Thread Hans J. Albertsson

On 2015-05-04 10:25, Thorsten Heit wrote:
 Hi,
  ...
 3) Have a coffee or two and wait

More like leave overnight, for an HP N54L...


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


Re: [OpenIndiana-discuss] Java 8 plugin for Firefox

2015-05-04 Thread Apostolos Syropoulos via openindiana-discuss

Check IcedTea, it works smoothly on my Linux at work..


After compiling OpenJDK 8 32-bit I compiled icedtea-web-1.6
and yes it works (please see the attached screen-shot). I guess
OpenJKD and IcedTea should replace JDK in OpenIndiana etc.

A.S.


--
Apostolos Syropoulos
Xanthi, Greece
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


Re: [OpenIndiana-discuss] OI updates

2015-05-04 Thread Tim Mooney

In regard to: [OpenIndiana-discuss] OI updates, Jon Tibble said (at 2:55pm...:


I've just pushed a collection of illumos-gate CVE fixes for a9.
This covers:
- 5378 CVE-2014-3158 ppp: integer overflow in option parsing
- 5480 CVE-2012-3165 mailx(1) buffer overflow vulnerability
- 5481 CVE-2012-1750 mailx(1) tilde expansion vulnerability
- 5853 pfexec_call() error handling could be improved
 5854 pfexecd should initialize pfexec response buffers
 (Not sure what CVE this actually was assigned.)

I've also pushed the NVIDIA driver update to 304.125 and the missing
pieces of the Delphix vmxnet3s driver patchset.


Thanks Jon!  I've applied this to my OI a9 workstation and so far
everything looks good.

Tim
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing  Infrastructure  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss