Re: [OpenIndiana-discuss] migrating zfs pools

[Jim Klimov]

On 2013-07-18 20:21, Gary Gendel wrote:

Jim,

Lots of great info here, thanks.

I was thinking about adding/removing the disks as mirrors.  My first
concern was the different disk capacities, geometries and 4k vs. 512
byte block sizes.  Then I realized that the end result reduces number of
mirrored disk sets by one.  Since there is no way to downsize the number
of mirror sets in a pool, it looks like that approach is not feasible.
Zfs send/receive it is. :)


Yes, for the sector size change - it is probably best to migrate so.
You might probably attach your old disks to the new (degraded, if
you follow my suggestion) tlvdevs, if they are same-sized, and they
should store properly sized ZFS block components (i.e. 4k per disk,
so what if that is 8 HW sectors and not one?)

Even if not, you'd probably find ways of using the old disks -
perhaps as a backup pool for occasional replication? ;)

//Jim


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

Re: [OpenIndiana-discuss] migrating zfs pools

[Gary Gendel]

Jim,

Lots of great info here, thanks.

I was thinking about adding/removing the disks as mirrors.  My first 
concern was the different disk capacities, geometries and 4k vs. 512 
byte block sizes.  Then I realized that the end result reduces number of 
mirrored disk sets by one.  Since there is no way to downsize the number 
of mirror sets in a pool, it looks like that approach is not feasible.  
Zfs send/receive it is. :)


Thanks for the super help.  The new disks arrive this weekend so I'll 
give it a go when I can.


Gary

On 07/18/2013 02:07 PM, Jim Klimov wrote:

On 2013-07-18 19:50, Gary Gendel wrote:

Hi,

I have a pool, archive, with zfs files:

/archive
/archive/gary
/archive/dani
/archive/ian


I want to replace this with a new set of disks along with the
appropriate properties set (smb sharing, etc.).

Basically, I want to copy the complete pool to a new pool and then
import that pool as the original.  The goal is to retire the original
pool configuration. Sounds like something that many have done before so
I wanted to tap on the experts who can provide direction and caveats.


This seems like a job for recursive ZFS send, which with replication
options should also transfer your datasets' attributes (such as share
definitions). One thing I'd suggest for the migration would be to
import the newly created pool with an "alternate mountpoint" (-R /a)
so that when your replicated filesystems begin mounting, they don't
conflict with originals (/archive -> /a/archive), but when you retire
your old pool and import the new without an altroot - paths to new
data would become the same as they were in the old setup.

While doing this, you might also want to use some different data
allocation policies (copies, compression, dedup if your huge RAM
permits, etc.) From my practice, this is best done by assigning the
policies to original datasets, then snapshotting and sending them.
You can also change attributes on destinations during the "zfs recv"
but this may be or not be convenient (i.e. different policies would
be applied to blocks written before you make the switch, though
this doesn't break anything from readers' perspective).

Possibly, it might make sense to send all historical data highly
compressed (i.e. gzip-9) and then re-set your new datasets to the
compression algos you'd need for performance, if applicable (i.e.
to lz4, lzjb, zle, off and so on). Note that I am still vague on
whether *reading* gzip-9 or lz4 yields any speed benefits to
either side (i.e. is decompression speed CPU-bound, and how much
for the two winning options).

Since you're speaking of retiring the pool configuration, I shouldn't
assume that you have something that can be simple expanded onto new
disks in the ways of mirroring (mirrors, raid10 - attach new disks
for increased redundancy, wait for resilver, detach old disks, expand
pool)? Eh, here, for completeness I've said it :)

Also, do you plan to retire old disks or reuse them later in the
new pool? At some risk to data integrity, you can create a pool
with missing devices (i.e. using a lofs device over a sparse file
for a component, then destroying it) - this would make your new
pool degraded, until you are done migrating data and place the old
disks into those "missing" positions. I wouldn't risk this with
single-redundancy setups, but for raidz2/raidz3 this trick might
make sense - NO WARRANTIES though :)

HTH,
//Jim Klimov


___
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] migrating zfs pools

[Jim Klimov]

On 2013-07-18 19:50, Gary Gendel wrote:

Hi,

I have a pool, archive, with zfs files:

/archive
/archive/gary
/archive/dani
/archive/ian


I want to replace this with a new set of disks along with the
appropriate properties set (smb sharing, etc.).

Basically, I want to copy the complete pool to a new pool and then
import that pool as the original.  The goal is to retire the original
pool configuration. Sounds like something that many have done before so
I wanted to tap on the experts who can provide direction and caveats.


This seems like a job for recursive ZFS send, which with replication
options should also transfer your datasets' attributes (such as share
definitions). One thing I'd suggest for the migration would be to
import the newly created pool with an "alternate mountpoint" (-R /a)
so that when your replicated filesystems begin mounting, they don't
conflict with originals (/archive -> /a/archive), but when you retire
your old pool and import the new without an altroot - paths to new
data would become the same as they were in the old setup.

While doing this, you might also want to use some different data
allocation policies (copies, compression, dedup if your huge RAM
permits, etc.) From my practice, this is best done by assigning the
policies to original datasets, then snapshotting and sending them.
You can also change attributes on destinations during the "zfs recv"
but this may be or not be convenient (i.e. different policies would
be applied to blocks written before you make the switch, though
this doesn't break anything from readers' perspective).

Possibly, it might make sense to send all historical data highly
compressed (i.e. gzip-9) and then re-set your new datasets to the
compression algos you'd need for performance, if applicable (i.e.
to lz4, lzjb, zle, off and so on). Note that I am still vague on
whether *reading* gzip-9 or lz4 yields any speed benefits to
either side (i.e. is decompression speed CPU-bound, and how much
for the two winning options).

Since you're speaking of retiring the pool configuration, I shouldn't
assume that you have something that can be simple expanded onto new
disks in the ways of mirroring (mirrors, raid10 - attach new disks
for increased redundancy, wait for resilver, detach old disks, expand
pool)? Eh, here, for completeness I've said it :)

Also, do you plan to retire old disks or reuse them later in the
new pool? At some risk to data integrity, you can create a pool
with missing devices (i.e. using a lofs device over a sparse file
for a component, then destroying it) - this would make your new
pool degraded, until you are done migrating data and place the old
disks into those "missing" positions. I wouldn't risk this with
single-redundancy setups, but for raidz2/raidz3 this trick might
make sense - NO WARRANTIES though :)

HTH,
//Jim Klimov


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

[OpenIndiana-discuss] migrating zfs pools

[Gary Gendel]

Hi,

I have a pool, archive, with zfs files:

/archive
/archive/gary
/archive/dani
/archive/ian


I want to replace this with a new set of disks along with the 
appropriate properties set (smb sharing, etc.).


Basically, I want to copy the complete pool to a new pool and then 
import that pool as the original.  The goal is to retire the original 
pool configuration. Sounds like something that many have done before so 
I wanted to tap on the experts who can provide direction and caveats.


Thanks,
Gary



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

Re: [OpenIndiana-discuss] smb server promblem

[Jim Klimov]

On 2013-07-18 17:40, Brogyányi József wrote:

Sorry little bit odd for me that few minutes finding time. Under the
booting time it has to find the smb server. I think this is another
annoying bug in win.
Anyway tank you the quick answer.


I think you can recreate an experiment by using a sniffer,
likely on all of the CIFS-related ports (IIRC tcp/udp
135 + 137-139 + 445 -- this is a bit of overkill, with
not all ports being used in all protocols, but it is
relatively easy to set up a catch-all sniffer rule).

Now that you say that after some time things become seen,
I can guess that the CIFS server sends out NMB announcements
as broadcasts every several seconds (30? 60? more?) and
that's what lets "Computer browser" client to detect the
server in its neighborhood. Likely, if your kCIFS server
started first and the Win7 client initialized later, there
is a gap between announcements when the client does not
know about the server. Restarting the server sends these
announcements, so the server would be seen in the network
neighborhood instantly.

Direct accesses to the named server and shares probably
causes the client to either solicit the server name (like
"plz send me your IP") or use your client's local naming
service which knows the name, or the explicit IP number
that you've provided, to access the server/share more
quickly.

This is my guess, you can verify with a sniffer to see
how far off I am... would be fun :)

//Jim


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

Re: [OpenIndiana-discuss] smb server promblem

[dormitionsk...@hotmail.com]

On Jul 18, 2013, at 7:32 AM, Jim Klimov wrote:

> That would be part of Samba, while I believe the OP is trying
> to get kCIFS working.



Ah, yes.  I have too many years with Linux.

svc:/network/samba:default == samba

svc:/network/smb/server:default ==  kCIFS

Sorry about that.  

Glad you got it working, though.

fp


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

Re: [OpenIndiana-discuss] smb server promblem

[Brogyányi József]

2013.07.18. 14:59 keltezéssel, dormitionsk...@hotmail.com írta:

On Jul 18, 2013, at 6:13 AM, Jozsef Brogyanyi wrote:


Hi

I have a little problem with smb server. When I issue the svcs -x command then 
I looked everything is all right but from win7 I could not see the shared 
folder's.
Just I can see the attached  folder's.


I'm not real sure what you mean.  Can you see the server in your Windows 
Explorer network neighborhood?

Try:  svcadm enable wins

This starts the nmbd service that makes the server visible in Windows, Linux, 
Mac, etc. file browsers.

HTH


Oh, and then wait a few minutes.  Some of the client browsers take a few 
minutes to find the servers.

But once it finds the server, you should be able to open the different shares 
without them being explicitly attached.





___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
You're right. When I switched on my win7 it can see the OI share. While 
I read your e-mail the network is began to work. Just I checked Jim 
command's.

It shows the next:
brogyi@openindiana:~$ svcs -a | grep shares
online Jul_16   svc:/network/shares/group:default
online Jul_16   svc:/network/shares/group:zfs
online Jul_16   svc:/network/shares/group:smb

Sorry little bit odd for me that few minutes finding time. Under the 
booting time it has to find the smb server. I think this is another 
annoying bug in win.

Anyway tank you the quick answer.
Next time I'll try the svcadm enable wins command.


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

Re: [OpenIndiana-discuss] smb server promblem

[Jim Klimov]

On 2013-07-18 14:49, dormitionsk...@hotmail.com wrote:

On Jul 18, 2013, at 6:13 AM, Jozsef Brogyanyi wrote:


Hi

I have a little problem with smb server. When I issue the svcs -x command then 
I looked everything is all right but from win7 I could not see the shared 
folder's.
Just I can see the attached  folder's.



I'm not real sure what you mean.  Can you see the server in your Windows 
Explorer network neighborhood?


+1, I also did not get what you do see and what you don't -
namely, I am not familiar with the term "attached folders" :)

Does running \\servername\share or \\servername.domain\share
or \\1.2.3.4\share (with IP address) from Windows all work,
before or after restarting the smb services?


Try:  svcadm enable wins

This starts the nmbd service that makes the server visible in Windows, Linux, 
Mac, etc. file browsers.


That would be part of Samba, while I believe the OP is trying
to get kCIFS working.

By the way, which "shares" services do you have running?
For example:

# svcs -a | grep shares
disabled   Jan_29   svc:/network/shares/group:default
online Jan_29   svc:/network/shares/group:smb
online Jan_29   svc:/network/shares/group:zfs

I am not sure what they are for :) but believe they should
be maintaining the link between ZFS properties (or manual
shareadm definitions) and networked server shares... maybe.
Maybe I am wrong.

//Jim


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

Re: [OpenIndiana-discuss] smb server promblem

[dormitionsk...@hotmail.com]

> On Jul 18, 2013, at 6:13 AM, Jozsef Brogyanyi wrote:
> 
>> Hi
>> 
>> I have a little problem with smb server. When I issue the svcs -x command 
>> then I looked everything is all right but from win7 I could not see the 
>> shared folder's.
>> Just I can see the attached  folder's.
>> 
> 
> I'm not real sure what you mean.  Can you see the server in your Windows 
> Explorer network neighborhood?
> 
> Try:  svcadm enable wins
> 
> This starts the nmbd service that makes the server visible in Windows, Linux, 
> Mac, etc. file browsers.
> 
> HTH
> 

Oh, and then wait a few minutes.  Some of the client browsers take a few 
minutes to find the servers.

But once it finds the server, you should be able to open the different shares 
without them being explicitly attached.





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

Re: [OpenIndiana-discuss] smb server promblem

[dormitionsk...@hotmail.com]

On Jul 18, 2013, at 6:13 AM, Jozsef Brogyanyi wrote:

> Hi
> 
> I have a little problem with smb server. When I issue the svcs -x command 
> then I looked everything is all right but from win7 I could not see the 
> shared folder's.
> Just I can see the attached  folder's.
> 

I'm not real sure what you mean.  Can you see the server in your Windows 
Explorer network neighborhood?

Try:  svcadm enable wins

This starts the nmbd service that makes the server visible in Windows, Linux, 
Mac, etc. file browsers.

HTH



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

[OpenIndiana-discuss] smb server promblem

[Jozsef Brogyanyi]

Hi

I have a little problem with smb server. When I issue the svcs -x 
command then I looked everything is all right but from win7 I could not 
see the shared folder's.

Just I can see the attached  folder's.

brogyi@openindiana:~$ svcs | grep smb
online Jul_16   svc:/network/shares/group:smb
online Jul_17   svc:/network/smb/server:default
online Jul_17   svc:/network/smb/client:default

When I issued the next:
brogyi@openindiana:~$ sudo svcadm restart network/smb/server:default

Win7 can find the Openindiana.

brogyi@openindiana:~$ svcs | grep smb
online Jul_16   svc:/network/shares/group:smb
online Jul_17   svc:/network/smb/client:default
online 13:34:41 svc:/network/smb/server:default

Why have to restart the smb server? OI shows the smb server is run and 
running now too. Where I made the mistake? Thanks.

Brogyi


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

Re: [OpenIndiana-discuss] Workaround for Flash Plugin using older one

[Udo Grabowski (IMK)]

On 18/07/2013 11:25, Jon Tibble wrote:




I found a version that works with FF19 and FF22 (22 had other issues



like non-collapsing right-click menus) but it's at work so will post
tomorrow.  Did work for youtube and last.fm though.



The version that works for me currently is 10.1.85.3 from 
fp_10.1.85.3_and_9.0.283_archive.zip available from Adobe's archive.

Firefox reports it as "Shockwave Flash 10.1 r85"

md5sum... 7672ff843863fb00d8618d7245879472  libflashplayer.so



Does not work with FF 17.0.6esr, see the black screen (after the
advertising):



--
Dr.Udo GrabowskiInst.f.Meteorology a.Climate Research IMK-ASF-SAT
www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technologyhttp://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany  T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] Workaround for Flash Plugin using older one

[Jon Tibble]

>> I found a version that works with FF19 and FF22 (22 had other issues

>> like non-collapsing right-click menus) but it's at work so will post
>> tomorrow.  Did work for youtube and last.fm though.
>>

The version that works for me currently is 10.1.85.3 from 
fp_10.1.85.3_and_9.0.283_archive.zip available from Adobe's archive.

Firefox reports it as "Shockwave Flash 10.1 r85"

md5sum... 7672ff843863fb00d8618d7245879472  libflashplayer.so

JT


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

Re: [OpenIndiana-discuss] Workaround for Flash Plugin using older one

[Udo Grabowski (IMK)]

On 15/07/2013 22:18, Udo Grabowski (IMK) wrote:

On 15/07/2013 21:11, Jon Tibble wrote:

On 14/07/2013 19:20, Udo Grabowski (IMK) wrote:

On 09/07/2013 16:51, Udo Grabowski (IMK) wrote:

On 09/07/2013 16:12, Paolo Marcheschi wrote:

Hi

I found a workaround for flash plugin in order to see youtube and
other flash sites,
I used the archived flashplayer10_1r53_64_solaris_x86.tar.bz2 from
http://fpdownload.macromedia.com/get/flashplayer/installers/archive/fp10.1_archive.zip


remove the newest plugin, and  copy the old one in .mozilla/plugins
folder.

use the r53 instead of the r82, because the r82 does not work on
other sites (i.e. grooveshark)
to avoid activate the plugin every time follow this guide:
http://mzl.la/R7DD9y

I Hope this helps.



It does, thanks for the research. Actually, the 10.1r53 was the most
"stable" working horse of crashplayer before we switched to 11.1.
Of course, that version is also "vulnerable", as far as this has
any practical relevance on non-Windows systems...
...


No it does not, the r53 is actually a r82 (they don't archive severely
vulnerable versions, but overwrite them silently). Instead of youtube,
most videos on Dailymotion are now broken, and in general this version
is very unstable. Did a check on later versions, but none of them
work with hipster.
So this problem is not fixed with that workaround, just shifted around.



I found a version that works with FF19 and FF22 (22 had other issues
like non-collapsing right-click menus) but it's at work so will post
tomorrow.  Did work for youtube and last.fm though.



Just a tip: When you test on Dailymotion, let it run a while,
what I found it that it starts stuttering and then stops after
a while with the r82 version, so problems are not seen immediately.




This is stranger than I thought: Sometimes, the 11.1 plugin works
even on youtube, then at one instance decides to crash, and crashes
on every video (even those which worked shortly before!) afterwards.

This looks like it depends on some libraries loaded in different
versions or order sometimes (or on some libraries loaded for some
codecs), and then stay in memory.
--
Dr.Udo GrabowskiInst.f.Meteorology a.Climate Research IMK-ASF-SAT
www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technologyhttp://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany  T:(+49)721 608-26026 F:-926026

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

Re: [OpenIndiana-discuss] php 5.5.0 with Studio 12.3

[Uwe Reh]

Hi David,

thanx, you are right. I had a stupid mistake in the httpd.conf. Now I 
can access mod_php. But I'm still concerned about the 80 failed tests, 
especially the one for 'flock'.


I tried to use GCC also but the result seems to be equal, because we 
don't have the glibc.


Uwe


Am 12.07.2013 01:33, schrieb David Brodbeck:

I would try to get it going first with command-line PHP running via CGI.
  That eliminates some of the tricky library dependency issues that mod_php
has.


On Tue, Jul 9, 2013 at 7:06 AM, Uwe Reh  wrote:


Hi,

has anyone made a successful build of php5.5

After some minor changes in the source (https://bugs.php.net/bug.php?**
id=65207 ) it was possible to
'make'. But php isn't really functional. More than 80 tests didn't pass and
mod_php produces nothing than empty pages.

Are there other hint's than using GCC?

Uwe

__**_
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